From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-devel@gnu.org, guile-user@gnu.org
Subject: Re: The 1.6.1 release.
Date: Sat, 30 Mar 2002 16:21:22 -0800 [thread overview]
Message-ID: <a85lq4$udd$2@main.gmane.org> (raw)
In-Reply-To: 87r8mxs5t8.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us
From: Evan Prodromou <evan@glug.org>
Date: Wed, 06 Mar 2002 16:13:39 -0600
So, for my own clarification, once 1.5.x becomes "blessed" into 1.6.x,
what happens in CVS? Will there still be 2 branches, one stable and
one unstable? Or will a third branch, 1.9.x, start happening at that
point? Or later, when 1.7.x is starting to look like 1.8.x?
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).
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. [cc guile-user]
thi
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next parent reply other threads:[~2002-03-31 0:21 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 ` Thien-Thi Nguyen [this message]
[not found] ` <E16rT62-0003Dh-00@giblet>
2002-03-31 13:00 ` The 1.6.1 release 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
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='a85lq4$udd$2@main.gmane.org' \
--to=ttn@giblet.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).