unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: guile-devel@gnu.org
Subject: Re: Stable branch will freeze.
Date: Tue, 02 Apr 2002 19:20:40 -0800	[thread overview]
Message-ID: <E16sbKC-00020K-00@giblet> (raw)
In-Reply-To: <87adt9eq8e.fsf@raven.i.defaultvalue.org> (message from Rob Browning on Fri, 15 Mar 2002 10:43:29 -0600)

   From: Rob Browning <rlb@defaultvalue.org>
   Date: Fri, 15 Mar 2002 10:43:29 -0600

   Agreed, and without having some kind of say about what does and
   doesn't go into the stable branch I certainly won't be able to
   effectively manage a release.

   [release management requirements]

do you mind if i add these to workbook/build/stability.text (or
"release-management-requirements.text" or wherever)?  probably a lot of
discussion would be better grounded if we record these items.

thi

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  parent reply	other threads:[~2002-04-03  3:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-14 23:29 Stable branch will freeze Marius Vollmer
2002-03-14 23:47 ` Neil Jerram
2002-03-15  0:02   ` Rob Browning
2002-03-15 19:38     ` Marius Vollmer
2002-03-15  0:02   ` Rob Browning
2002-03-15  0:05 ` Thien-Thi Nguyen
2002-03-15  9:24   ` Neil Jerram
2002-03-15 11:47     ` Thien-Thi Nguyen
2002-03-15 11:59     ` Thien-Thi Nguyen
     [not found]     ` <87adt9eq8e.fsf@raven.i.defaultvalue.org>
2002-04-03  3:20       ` Thien-Thi Nguyen [this message]
2002-04-03  4:22         ` Rob Browning
2002-03-15 19:54   ` Marius Vollmer
2002-03-15 23:19     ` Thien-Thi Nguyen
2002-03-16  0:08       ` Marius Vollmer
2002-03-16  0:39         ` Thien-Thi Nguyen
2002-03-16 18:12 ` Evan Prodromou
2002-03-18 20:19   ` Rob Browning
2002-03-20 21:53     ` Marius Vollmer
2002-04-03  3:33   ` Thien-Thi Nguyen
2002-04-03  4:25     ` Rob Browning

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=E16sbKC-00020K-00@giblet \
    --to=ttn@giblet.glug.org \
    --cc=guile-devel@gnu.org \
    --cc=ttn@glug.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).