From: Neil Jerram <neil@ossau.uklinux.net>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: Stable releases
Date: Tue, 21 Nov 2006 22:01:41 +0000 [thread overview]
Message-ID: <87irh8e9x6.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <rmiodr1rokt.fsf@fnord.ir.bbn.com> (Greg Troxel's message of "Tue, 21 Nov 2006 07:06:42 -0500")
Greg Troxel <gdt@ir.bbn.com> writes:
> Right now we have stable releases at intervals best measured in years
> (0 in 2005, 3 in 2006). While having them more often would be good,
> 2-3 days is way too ambitious. I'd suggest as something that is
> achievable and would be useful:
>
> release 2 months after last release if anything significant has
> changed (where significant means new feature or bug fix)
>
> release 6 months after last release if anything has changed at all
>
> release after a 1 week cooling off period if a serious bug is fixed
That's fine, but 99% of the time I expect it to collapse in practice
to just the last point, because
- by definition, nothing should usually change in a stable series
apart from bug fixes
- bug fixes usually happen in response to someone reporting a problem,
and I find it difficult to imaging saying to that person "we've
fixed your bug, but don't regard it as important and so will not be
making a release until a couple of months' time".
> In my view, the main path to guile usage by other than the people on
> this list is via stale releases and then packaging systems. This
> enables other people to choose to depend on guile. Currently, that's
> a scary choice to make.
Not sure I understand. What do you think it is that makes the choice
scary?
Regards,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2006-11-21 22:01 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
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 [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=87irh8e9x6.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--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).