From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: GNU Guile 2.0.4 released
Date: Tue, 31 Jan 2012 14:46:58 +0100 [thread overview]
Message-ID: <87lioougq5.fsf@pobox.com> (raw)
In-Reply-To: <87hazcknzr.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 31 Jan 2012 14:20:08 +0100")
On Tue 31 Jan 2012 14:20, ludo@gnu.org (Ludovic Courtès) writes:
> Regarding bug fixing, there’s probably room for improvement. For
> instance, when a bug is filed, we could assign a target release for the
> fix, and stick to it. Perhaps we could have a more formal freeze window
> also, during which we would only fix new bugs and be extremely
> conservative about anything else.
I don't know. Releases are also energetic times, when people become
more active -- and it's not always activity that can be redirected to
fixing bugs, unfortunately :/ So if we're too strict, we might lose
some of that without it going in other productive directions.
The local-eval thing was not satisfying for many reasons, and it did
delay the release. Still, it's good to have it in and settled.
> What do you think?
I guess in summary: I don't know :)
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2012-01-31 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 20:56 GNU Guile 2.0.4 released Ludovic Courtès
2012-01-30 21:13 ` Ludovic Courtès
2012-01-30 21:27 ` Neil Jerram
2012-01-30 21:43 ` Hans Aberg
2012-01-30 22:15 ` Ludovic Courtès
2012-01-31 9:41 ` Andy Wingo
2012-01-31 13:20 ` Ludovic Courtès
2012-01-31 13:46 ` Andy Wingo [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=87lioougq5.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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).