From: Rob Browning <rlb@defaultvalue.org>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: Stable releases
Date: Sun, 19 Nov 2006 17:46:35 -0800 [thread overview]
Message-ID: <87k61qopok.fsf@raven.defaultvalue.org> (raw)
In-Reply-To: <87bqn5n48n.fsf@ossau.uklinux.net> (Neil Jerram's message of "Fri, 17 Nov 2006 21:38:16 +0000")
Neil Jerram <neil@ossau.uklinux.net> writes:
> If we followed this, I'm pretty sure the result would be more
> frequent stable releases than in the past. I don't see any problem
> with that, in fact I think it would be a good thing... but then I've
> never prepared a release myself. Is the release process
> sufficiently easy and automated that it would allow us to do this?
> And what does everyone else think about whether it's a good idea?
I think more frequent stable releases are a good idea, though at least
right now, there is enough by-hand work involved that I wouldn't want
to do it *too* often. Of course I could probably automate things a
bit more. [1]
Note though, that one thing that is key to making more frequent stable
releases easy is careful discipline on the part of anyone committing
to the stable branch. If everyone remembers to include the
appropriate ChangeLog, NEWS, etc. entries, then there's much less to
do at release time. Otherwise, the diff against the last stable
release has to be examined more carefully, developers have to be
prodded, etc.
[1] It might be nice if there were a more automated way to generate
the html and text NEWS summaries for the web pages and the list
announcements. I suppose I could just have the list announcement
point to the web page, but I don't know how much people like
having the summary in the message itself.
--
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-20 1:46 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 [this message]
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
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=87k61qopok.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).