From: Neil Jerram <neil@ossau.uklinux.net>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: Stable releases
Date: Tue, 21 Nov 2006 21:39:06 +0000 [thread overview]
Message-ID: <87r6vweayt.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87k61qopok.fsf@raven.defaultvalue.org> (Rob Browning's message of "Sun, 19 Nov 2006 17:46:35 -0800")
Rob Browning <rlb@defaultvalue.org> writes:
> 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]
I'd like to help if I can with automating things. Is the release
process documented somewhere so I can begin to get an idea of what's
involved?
> 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.
Yes, absolutely. I think a large part of the problem for 1.8.1,
however, was that we weren't sure what the organization and format of
NEWS should be. Once we're decided on that, I think it would be
easier to put in entries for the diffs.
> [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.
I'm sure we should be able to automate format stuff. NEWS is in text
anyway, so doesn't this just mean that we need text -> html for the
webpage?
Regards,
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-11-21 21:39 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 [this message]
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=87r6vweayt.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).