From: Rob Browning <rlb@defaultvalue.org>
Cc: evan@glug.org, guile-devel@gnu.org, guile-user@gnu.org
Subject: Re: The 1.6.1 release.
Date: Sun, 31 Mar 2002 14:41:07 -0600 [thread overview]
Message-ID: <87lmc8fp24.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <E16rT62-0003Dh-00@giblet> (Thien-Thi Nguyen's message of "Sat, 30 Mar 2002 16:21:22 -0800")
Thien-Thi Nguyen <ttn@giblet.glug.org> writes:
> good question.
>
> IMO, the more branches there are the more PITA it is to maintain them.
> this suggests that to cut ourselves slack we should delay branching
> until things are *determined* to be stable (as opposed being *declared*
> to be stable).
I have no problem with this. This is what I'd intended for the next
release.
> to do a good determination means we need to define what are the
> criteria for stability so that we can measure the living tree
> against it. there is now workbook/build/stability.text (currently
> empty) -- everyone please feel free to suggest items to add to that
> file.
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.
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-03-31 20:41 UTC|newest]
Thread overview: 4+ 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
2002-03-31 20:41 ` Rob Browning [this message]
2002-04-01 14:26 ` Neil Jerram
2002-04-03 10:37 ` Thien-Thi Nguyen
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=87lmc8fp24.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=evan@glug.org \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.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).