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: Items blocking release 1.6.1 (2002-04-21) Date: Sun, 21 Apr 2002 11:22:22 -0500 Sender: guile-devel-admin@gnu.org Message-ID: <87d6wtqawx.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 1019406300 719 127.0.0.1 (21 Apr 2002 16:25:00 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 21 Apr 2002 16:25:00 +0000 (UTC) Return-path: Original-Received: from fencepost.gnu.org ([199.232.76.164]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 16zK95-0000BU-00 for ; Sun, 21 Apr 2002 18:24:59 +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 16zK8F-0006qR-00; Sun, 21 Apr 2002 12:24:07 -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 16zK6Z-0006ik-00 for ; Sun, 21 Apr 2002 12:22:23 -0400 Original-Received: from raven.i.defaultvalue.org (raven.i.defaultvalue.org [192.168.1.7]) by defaultvalue.org (Postfix) with ESMTP id B3C424720 for ; Sun, 21 Apr 2002 11:22:22 -0500 (CDT) Original-Received: by raven.i.defaultvalue.org (Postfix, from userid 1000) id A1885BB0; Sun, 21 Apr 2002 11:22:22 -0500 (CDT) Original-To: guile-devel@gnu.org Original-Lines: 71 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:437 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:437 Since I've had no negative feeback regarding my release management posts, I'm planning to add those to our policy documentation and proceed accordingly. If you haven't read those messages yet, please do, but the summary is that the stable TODO section and the bugs tagged release critical represent the *complete* set of items holding up the release, and you should not change this set after the stable release has branched without discussing it with the release manager first (i.e. me). Whenever we're near a stable release, I'll be posting this "blocking list" on a regular basis as a reminder. NOTE: if you're working on something that's listed below, please contact me. If your bit is not in the TODO or bugs and marked appropriately, I may release without it. Items currently listed as holding up the 1.6 release are listed below. More information needed from: [mvo], [ttn]. (The bugs listed as belonging to me I can fix in a day, so please don't wait on me.) (1) bugs/optargs-bound-gone [mvo?] Marius: you discussed a fix for this in email, but also mention that it's functionality is fairly easily worked around via default value -- so are we fixing it for 1.6, or are we adding a NEWS entry recommending the alternative approach? If we are fixing it, and if you can describe the fix, I can do the work. (2) bugs/intructions-to-distributors [rlb] I'll handle this one -- I'll either have full fledged instructions by the release, or I'll include some information and a request for packagers to contact guile-devel before packaging. This will depend on how far I get before all the other release critical bugs are finished. (3) tasks/TODO - document libtool conventions [rlb] Needs to be done -- will do. (4) tasks/TODO - convert bug tracking/summarization process Is this really 1.6 release critical? It seems like it could be moved to a 1.8 section or "Eventually" to me, but I may be missing something. For 1.6, it seems like we can easily just create copy BUGS by hand if this is likely to hold things up any longer. (5) tasks/TODO - write build/bugs-triage.text - complete build/stability.text [ttn] - make sure all bugs have required headers Are these really 1.6 release critical? I'm inclined to want to move these to the 1.8 section as well. While I think these improvements are important, and should certainly be finished by 1.8, they don't seem like anything that can't wait until 1.6.2, etc. -- 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 -- 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