From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Marius Vollmer Newsgroups: gmane.lisp.guile.devel Subject: Re: Stable branch will freeze. Date: 20 Mar 2002 22:53:30 +0100 Sender: guile-devel-admin@gnu.org Message-ID: <874rja29et.fsf@zagadka.ping.de> References: <87vgbywwxp.fsf@zagadka.ping.de> <87elik1ix6.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us> <87pu216345.fsf@raven.i.defaultvalue.org> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1016662341 13733 127.0.0.1 (20 Mar 2002 22:12:21 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 20 Mar 2002 22:12:21 +0000 (UTC) Cc: Evan Prodromou , guile-devel@gnu.org Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 16noJh-0003ZO-00 for ; Wed, 20 Mar 2002 23:12:21 +0100 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16noJY-0008Dp-00; Wed, 20 Mar 2002 17:12:12 -0500 Original-Received: from dialin.speedway42.dip179.dokom.de ([195.138.42.179] helo=zagadka.ping.de) by fencepost.gnu.org with smtp (Exim 3.34 #1 (Debian)) id 16nnzP-0005gL-00 for ; Wed, 20 Mar 2002 16:51:24 -0500 Original-Received: (qmail 11462 invoked by uid 1000); 20 Mar 2002 21:53:30 -0000 Original-To: Rob Browning In-Reply-To: <87pu216345.fsf@raven.i.defaultvalue.org> Original-Lines: 20 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 Errors-To: guile-devel-admin@gnu.org X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Developers list for Guile, the GNU extensibility library List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.lisp.guile.devel:131 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:131 Rob Browning writes: > Evan Prodromou 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