From: Neil Jerram <neil@ossau.uklinux.net>
Subject: Re: Stable releases
Date: Tue, 21 Nov 2006 21:33:56 +0000 [thread overview]
Message-ID: <87vel8eb7f.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <8764dai81b.fsf@laas.fr> ( Ludovic Courtès's message of "Mon, 20 Nov 2006 14:04:16 +0100")
ludovic.courtes@laas.fr (Ludovic Courtès) writes:
> Hi,
>
> Neil Jerram <neil@ossau.uklinux.net> writes:
>
>> I've been wondering whether we could make stable releases on a more
>> predictable basis than we have done in the past.
>
> I'm all in favor of what you propose, but...
>
>> (a) leaving a short while - say 2-3 days - after committing a fix,
>> just in case of a glaring mistake that would be picked up by
>> another developer building
>
> I believe 2-3 days is a bit too short, given the current average
> response time on this mailing list. :-) So I'd rather say one week.
Agreed, one week is better.
> And also it'd be nice if the release maker could send a reminder one
> week before making the release so that people have an incentive to
> update their trees and test.
Yes, good idea.
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:33 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 [this message]
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=87vel8eb7f.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
/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).