From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Thien-Thi Nguyen Newsgroups: gmane.lisp.guile.devel Subject: Re: Release management - take 1 Date: Wed, 24 Apr 2002 10:17:58 -0700 Sender: guile-devel-admin@gnu.org Message-ID: References: <87it6tinwb.fsf@raven.i.defaultvalue.org> <87hem1kyh0.fsf@raven.i.defaultvalue.org> Reply-To: ttn@glug.org NNTP-Posting-Host: localhost.gmane.org X-Trace: main.gmane.org 1019669063 14428 127.0.0.1 (24 Apr 2002 17:24:23 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 24 Apr 2002 17:24:23 +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 170QVD-0003kb-00 for ; Wed, 24 Apr 2002 19:24:23 +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 170QUw-0001lY-00; Wed, 24 Apr 2002 13:24:06 -0400 Original-Received: from ca-crlsbd-u5-c4a-a-172.crlsca.adelphia.net ([24.48.214.172] helo=giblet) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 170QTE-0001gu-00 for ; Wed, 24 Apr 2002 13:22:20 -0400 Original-Received: from ttn by giblet with local (Exim 3.33 #1 (Debian)) id 170QP0-00085h-00; Wed, 24 Apr 2002 10:17:58 -0700 Original-To: rlb@defaultvalue.org In-Reply-To: <87hem1kyh0.fsf@raven.i.defaultvalue.org> (message from Rob Browning on Wed, 24 Apr 2002 08:39:07 -0500) 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:498 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:498 From: Rob Browning Date: Wed, 24 Apr 2002 08:39:07 -0500 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. cool. 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. i'm in parallel writing such a dist-guile (based on dist-guile-www) aimed for 1.4.1 release (so you see, i'm bugging you to write this stuff down so that i can follow your lead). it doesn't do all the things in RELEASE, just the mechanical bits. will probably checkin today. two weeks is probably better, making sure at least two weekends are in there for people who need to do the work then. good point. weekends are quite precious to volunteer efforts. 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. that's wishful thinking. the day everyone knows what's going on, the universe will blink out of existence. remember that there are lurkers (reading this) who may become guile maintainers in the future, and indeed current maintainers (self included) who are depending on you to do the thinking for them on these matters. 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. i'm glad to see checkins of process-related docs. thi _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://mail.gnu.org/mailman/listinfo/guile-devel