From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: Evan Prodromou <evan@glug.org>, guile-devel@gnu.org
Subject: Re: Stable branch will freeze.
Date: 20 Mar 2002 22:53:30 +0100 [thread overview]
Message-ID: <874rja29et.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87pu216345.fsf@raven.i.defaultvalue.org>
Rob Browning <rlb@defaultvalue.org> writes:
> Evan Prodromou <evan@glug.org> writes:
>
> > However, I kind of agree with Thi that there's some process that needs
> > some work here. I'd recommend that you maybe ask one of the people
> > who've been concentrating on this release to mark the BUGS file -- or
> > another file, or a daturbase or whatever -- with a criticality level.
>
> Ok, as I mentioned before, would anyone be opposed to placing
> references to the relevant release critical bugs in the TODO from now
> on? i.e.
>
> === Before releasing 1.6.0:
>
> - Resolve Bug#751: make sure the frob whizzes.
>
> etc.
That sounds good to me.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-03-20 21:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-14 23:29 Stable branch will freeze Marius Vollmer
2002-03-14 23:47 ` Neil Jerram
2002-03-15 0:02 ` Rob Browning
2002-03-15 19:38 ` Marius Vollmer
2002-03-15 0:02 ` Rob Browning
2002-03-15 0:05 ` Thien-Thi Nguyen
2002-03-15 9:24 ` Neil Jerram
2002-03-15 11:47 ` Thien-Thi Nguyen
2002-03-15 11:59 ` Thien-Thi Nguyen
[not found] ` <87adt9eq8e.fsf@raven.i.defaultvalue.org>
2002-04-03 3:20 ` Thien-Thi Nguyen
2002-04-03 4:22 ` Rob Browning
2002-03-15 19:54 ` Marius Vollmer
2002-03-15 23:19 ` Thien-Thi Nguyen
2002-03-16 0:08 ` Marius Vollmer
2002-03-16 0:39 ` Thien-Thi Nguyen
2002-03-16 18:12 ` Evan Prodromou
2002-03-18 20:19 ` Rob Browning
2002-03-20 21:53 ` Marius Vollmer [this message]
2002-04-03 3:33 ` Thien-Thi Nguyen
2002-04-03 4:25 ` Rob Browning
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=874rja29et.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=evan@glug.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).