From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: mvo@zagadka.ping.de, guile-devel@gnu.org
Subject: Re: Stable branch will freeze.
Date: Fri, 15 Mar 2002 03:47:38 -0800 [thread overview]
Message-ID: <E16lqBO-00005F-00@giblet> (raw)
In-Reply-To: <m3g0324215.fsf@laruns.ossau.uklinux.net> (message from Neil Jerram on 15 Mar 2002 09:24:06 +0000)
From: Neil Jerram <neil@ossau.uklinux.net>
Date: 15 Mar 2002 09:24:06 +0000
I think that's rather harsh, thi. A small amount of focus and control
to get a release out is hardly dictatorship.
true, but focus and control were not demonstrated, only intimated. the
reality is no one here controls anyone but themselves (and obviously in
my case i can't even do that very well ;-). why make noise otherwise?
wrt focus, this looks promising:
The real problem here is that we don't have a shared view of what is
release critical. We used to, but I think that sense was blown off
course by the volume of bugs that have been reported recently.
so how do we go about (re-)nailing down this shared view? more
precisely, what is the path under devel/ where you propose to check in
the release-critical shared view?
thi
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-03-15 11:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 23:29 Stable branch will freeze Marius Vollmer
2002-03-14 23:47 ` Neil Jerram
2002-03-15 0:02 ` Rob Browning
2002-03-15 19:38 ` Marius Vollmer
2002-03-15 0:02 ` Rob Browning
2002-03-15 0:05 ` Thien-Thi Nguyen
2002-03-15 9:24 ` Neil Jerram
2002-03-15 11:47 ` Thien-Thi Nguyen [this message]
2002-03-15 11:59 ` Thien-Thi Nguyen
[not found] ` <87adt9eq8e.fsf@raven.i.defaultvalue.org>
2002-04-03 3:20 ` Thien-Thi Nguyen
2002-04-03 4:22 ` Rob Browning
2002-03-15 19:54 ` Marius Vollmer
2002-03-15 23:19 ` Thien-Thi Nguyen
2002-03-16 0:08 ` Marius Vollmer
2002-03-16 0:39 ` Thien-Thi Nguyen
2002-03-16 18:12 ` Evan Prodromou
2002-03-18 20:19 ` Rob Browning
2002-03-20 21:53 ` Marius Vollmer
2002-04-03 3:33 ` Thien-Thi Nguyen
2002-04-03 4:25 ` Rob Browning
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E16lqBO-00005F-00@giblet \
--to=ttn@giblet.glug.org \
--cc=guile-devel@gnu.org \
--cc=mvo@zagadka.ping.de \
--cc=ttn@glug.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).