unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Subject: Release status 1.6.1 (2002-05-16)
Date: Thu, 16 May 2002 18:12:39 -0500	[thread overview]
Message-ID: <878z6jn0uw.fsf@raven.i.defaultvalue.org> (raw)


OK, finally finished dealing with various real-life issues and back to
working on the release.

I have finally integrated the new release policy into
workbook/build/release.txt.  It's in the "Policy" section and is
nearly identical to the first copy I posted here.  If you didn't see
the previous copy, then please look at the file, especially if you
have CVS write access.

Two notable changes are that the waiting period after a beta release
before we declare that Guile is ready for a stable release has been
extended from one to two weeks (as per ttn's suggestion), and it has
been noted that in addition to the release manager, members of the
maintainer committee are expliticly allowed to make changes to a
stable branch without talking to the release manager beforehand.  Of
course keeping in touch with the release manager is still strongly
advised :> I have also updated various other files in tasks/ and bugs/
to refer to the new release policy so that people will be more likely
to remember it.

While I was working on release.txt I also reformatted the file as an
outline, but there's still a lot of cleaning up to do, and in general,
I agree with ttn that migrating some of those steps into a well
documented script (or scripts) is probably a good idea.

OK, on with the release status.

Items blocking release 1.6.1:
-----------------------------

NOTE: if you're working on something that's NOT listed below, please
contact me.  If something is neither in the 1.6.1 section of
workbook/tasks/TODO nor marked release 1.6.1 critical in
workbook/bugs/, then I may release without it.

  (1) document libtool conventions [rlb]

  (2) make sure all bugs have required headers

      What are the required headers?  i.e. how would this TODO item be
      satisfied?

  (3) bugs/instructions-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.

  (4) bugs/COPYING-is-wrong [rlb]

      Umm, COPYING is now the GPL in CVS.  Perhaps I should fix that :>


So I'll take care of three of the four.  I'll plan to fix them shortly
-- probably in a day or so, after I finish some other non-Guile
things.  If anyone else wants to fix (4) and has the time, feel free
to.

Thanks

-- 
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


             reply	other threads:[~2002-05-16 23:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-16 23:12 Rob Browning [this message]
2002-05-22 12:52 ` Release status 1.6.1 (2002-05-16) Marius Vollmer
2002-05-22 14:23   ` Rob Browning
2002-05-22 14:52     ` Marius Vollmer
2002-05-22 15:12     ` Marius Vollmer
2002-05-25 16:01     ` Neil Jerram
2002-05-25 17:12       ` Dale P. Smith
2002-05-25 23:04       ` Rob Browning
2002-05-27 20:37         ` Marius Vollmer
2002-05-26 16:59       ` rm
2002-05-26 17:54         ` Jeff Read
2002-05-27 20:44         ` Marius Vollmer
2002-05-27 21:38           ` rm
2002-05-28  4:36             ` Rob Browning
2002-05-28 10:22               ` rm
2002-05-28 16:09                 ` Rob Browning
2002-05-28 17:45                   ` Marius Vollmer
2002-05-28 17:55                     ` Marius Vollmer
2002-05-28 18:11                       ` Rob Browning
2002-05-28 19:27                         ` Marius Vollmer
2002-05-30 16:26                           ` Rob Browning
2002-05-30 17:45                             ` Marius Vollmer
2002-05-30 18:05                               ` rm
2002-05-30 19:21                                 ` Rob Browning
2002-05-30 19:33                                 ` Marius Vollmer
2002-05-28 17:53             ` Marius Vollmer

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=878z6jn0uw.fsf@raven.i.defaultvalue.org \
    --to=rlb@defaultvalue.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).