From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Rob Browning Newsgroups: gmane.lisp.guile.devel Subject: Re: Release management - take 1 Date: Wed, 24 Apr 2002 08:39:07 -0500 Sender: guile-devel-admin@gnu.org Message-ID: <87hem1kyh0.fsf@raven.i.defaultvalue.org> References: <87it6tinwb.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 1019655765 16831 127.0.0.1 (24 Apr 2002 13:42:45 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 24 Apr 2002 13:42:45 +0000 (UTC) Cc: guile-devel@gnu.org Return-path: Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 170N2i-0004NE-00 for ; Wed, 24 Apr 2002 15:42:44 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 170N2J-0000Qc-00; Wed, 24 Apr 2002 09:42:19 -0400 Original-Received: from dsl-209-87-109-2.constant.com ([209.87.109.2] helo=defaultvalue.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 170MzL-0000Da-00 for ; Wed, 24 Apr 2002 09:39:15 -0400 Original-Received: from raven.i.defaultvalue.org (raven.i.defaultvalue.org [192.168.1.7]) by defaultvalue.org (Postfix) with ESMTP id 2C3FA14E2; Wed, 24 Apr 2002 08:39:14 -0500 (CDT) Original-Received: by raven.i.defaultvalue.org (Postfix, from userid 1000) id 0DACD11CE; Wed, 24 Apr 2002 08:39:08 -0500 (CDT) Original-To: ttn@glug.org In-Reply-To: (Thien-Thi Nguyen's message of "Tue, 23 Apr 2002 22:56:56 -0700") Original-Lines: 59 User-Agent: Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.2 (i386-debian-linux-gnu) Errors-To: guile-devel-admin@gnu.org X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.0.9 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:489 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:489 Thien-Thi Nguyen writes: > * Eventually workbook/tasks/TODO and a scan of workbook/bugs/* for > the relevant release-critical tags should always provide a > *complete* picture of what's holding up a release. For those > that don't have direct CVS access, please make sure you ask > someone who does to edit TODO or bugs/* accordingly. > > this latter point can be codified, and thus indicates a TODO item: > "write why-not-release? scanner" (just added). Sounds good. > * whenever all the currently listed release TODO items and release > critical bugs have been resolved (by whatever means), the release > manager will build, upload and announce a pre-release beta. > > new TODO item: "write maintainer script dist-guile" Sounds reasonable -- I've actually had a few false starts on such a script here -- initially for my own use, but if it ended up being good enough I had planned to add it to guile. I have to say, though that so far I've still been more comfortable just having the RELEASE list and doing each step by hand, but I agree that a *good* script would likely be a win, so I'll keep at it. > * If after a pre-release beta has been out for a week and no new > agreed-upon release-critical issues arise, the release manager > will build, upload, and announce the stable release. > > i would up this to two weeks given how time flies when you get old > (maybe you are lucky to not feel this :-) and how we would like to > eventually encourage all people to participate, no matter age or other > business. That's fine with me. I'll make the change. In truth, I expected there to be some slack in there anyhow, but I wanted to make sure things didn't drag out too long. You're probably right, though, two weeks is probably better, making sure at least two weekends are in there for people who need to do the work then. > everything else looks great. i like being able to visualize code > based on these descriptions... now on to the unique process... OK, I'll take my original and your comments and merge these into the workbook. I may also take your suggestion (in another message) and make doing this be the resolution to one of the "release critical" bugs, but I really don't think this should hold up the 1.6.1, since everyone here involved knows what's going on. Accordingly I'd like to reserve the right to move the relevant todo item to being 1.8 release critical if everything else is done, but let's see how far I get by Monday. -- Rob Browning rlb @defaultvalue.org, @linuxdevel.com, and @debian.org Previously @cs.utexas.edu GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://mail.gnu.org/mailman/listinfo/guile-devel