From: Rob Browning <rlb@defaultvalue.org>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: Stable releases
Date: Tue, 21 Nov 2006 23:16:12 -0800 [thread overview]
Message-ID: <87k61ovtmr.fsf@raven.defaultvalue.org> (raw)
In-Reply-To: <87mz6kea8c.fsf@ossau.uklinux.net> (Neil Jerram's message of "Tue, 21 Nov 2006 21:54:59 +0000")
Neil Jerram <neil@ossau.uklinux.net> writes:
> I think we probably have taken a wrong turn, because I don't think
> the 1.8.x that we are on the verge of producing can be described any
> more as a "stable" series. Surely the common connotations of
> "stable" are that the API is as unchanging as possible, and that the
> code is only changed in order to fix non-trivial bugs?
I think I'd be in favor of fixing trivial bugs too, as long as the
fixes are extremely unlikely to cause any other trouble, but other
than that I agree.
> Therefore, my feeling now is that we should revert to traditional
> "stable" handling for 1.8.x. This would mean not merging
> enhancements from HEAD such as my debugging stuff and Ludovic's text
> collation work. It would also mean that Rob's comments about
> limited testing requirement hold.
>
> As far as releasing exciting new stuff is concerned, I suggest we
> just make unstable 1.9.x releases every now and then. We should
> flag these very clearly as unstable, and not really worry at all
> about testing them.
You have fairly accurately summarized the way I would prefer to handle
things, but it hasn't been completely clear to me that that's what
everyone else wants.
In general I would prefer to be very conservative with the stable
series, and just plan to create a new stable series as often as
needed.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-11-22 7:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 21:38 Stable releases Neil Jerram
2006-11-20 1:46 ` Rob Browning
2006-11-21 21:39 ` Neil Jerram
2006-11-22 6:47 ` Rob Browning
2006-11-27 22:44 ` Neil Jerram
2006-11-30 5:57 ` Rob Browning
2006-12-02 14:06 ` Neil Jerram
2006-11-20 13:04 ` Ludovic Courtès
2006-11-20 17:39 ` Rob Browning
2006-11-21 21:54 ` Neil Jerram
2006-11-22 7:16 ` Rob Browning [this message]
2006-11-22 13:37 ` Ludovic Courtès
2006-11-23 18:05 ` Rob Browning
2006-11-27 22:40 ` Neil Jerram
2006-11-28 9:01 ` Ludovic Courtès
2006-12-02 14:21 ` Neil Jerram
2006-12-04 8:55 ` Ludovic Courtès
2006-11-27 8:39 ` Ludovic Courtès
2006-11-21 21:33 ` Neil Jerram
2006-11-21 12:06 ` Greg Troxel
2006-11-21 22:01 ` Neil Jerram
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=87k61ovtmr.fsf@raven.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@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).