From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: evan@glug.org, guile-devel@gnu.org, guile-user@gnu.org
Subject: Re: The 1.6.1 release.
Date: Wed, 03 Apr 2002 02:37:02 -0800 [thread overview]
Message-ID: <a8embc$1be$2@main.gmane.org> (raw)
In-Reply-To: <87lmc8fp24.fsf@raven.i.defaultvalue.org> (message from Rob Browning on Sun, 31 Mar 2002 14:41:07 -0600)
From: Rob Browning <rlb@defaultvalue.org>
Date: Sun, 31 Mar 2002 14:41:07 -0600
As a practical definition, I'd love to see it move to the point where
being ready for release was more just a matter of making sure all the
release-critical TODO items had been done (which would include
references into the bug tree), and that "make check" would complete
without error on the "primary platforms". In particular, I'd like to
see items added to "make check" whenever we have important problems
that need fixing -- *before* we fix them. This wouldn't be
appropriate for all problems, but for many I suspect it would.
why don't you add this to build/release.text and fill it out w/ related
process? i think it's safe to say that whoever writes release.text has
the most say in the release process. since you're doing the release it
makes more sense for you to do it than for me. (i'm a lazy bastard,
too. ;-)
thi
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2002-04-03 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ofi5qm4a.fsf@raven.i.defaultvalue.org>
[not found] ` <87r8mxs5t8.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us>
2002-03-31 0:21 ` The 1.6.1 release Thien-Thi Nguyen
[not found] ` <E16rT62-0003Dh-00@giblet>
2002-03-31 13:00 ` Mr. Peter Ivanyi
2002-04-03 10:32 ` Thien-Thi Nguyen
2002-03-31 20:41 ` Rob Browning
[not found] ` <87lmc8fp24.fsf@raven.i.defaultvalue.org>
2002-04-01 14:26 ` Neil Jerram
2002-04-03 10:37 ` Thien-Thi Nguyen [this message]
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='a8embc$1be$2@main.gmane.org' \
--to=ttn@giblet.glug.org \
--cc=evan@glug.org \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--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).