unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
Cc: ttn@glug.org, evan@glug.org, guile-devel@gnu.org, guile-user@gnu.org
Subject: Re: The 1.6.1 release.
Date: 01 Apr 2002 15:26:03 +0100	[thread overview]
Message-ID: <a89ta6$9u8$2@main.gmane.org> (raw)
In-Reply-To: 87lmc8fp24.fsf@raven.i.defaultvalue.org

>>>>> "Rob" == Rob Browning <rlb@defaultvalue.org> writes:

    Rob> Thien-Thi Nguyen <ttn@giblet.glug.org> writes:
    >> good question.
    >> 
    >> IMO, the more branches there are the more PITA it is to maintain them.
    >> this suggests that to cut ourselves slack we should delay branching
    >> until things are *determined* to be stable (as opposed being *declared*
    >> to be stable).

    Rob> I have no problem with this.  This is what I'd intended for the next
    Rob> release.

Although I'm probably a prime culprit (because of the elisp work in
unstable), I also agree with this.  It's a major pain having to work
with multiple branches over an extended period.

(Especially when that period includes deciding to merge all the
documentation directories and then separate them out again - d'oh!)

        Neil


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


  reply	other threads:[~2002-04-01 14:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87ofi5qm4a.fsf@raven.i.defaultvalue.org>
     [not found] ` <87r8mxs5t8.fsf@tyrell.bad-people-of-the-future.san-francisco.ca.us>
2002-03-31  0:21   ` The 1.6.1 release Thien-Thi Nguyen
2002-03-31 20:41     ` Rob Browning
2002-04-01 14:26       ` Neil Jerram [this message]
2002-04-03 10:37       ` Thien-Thi Nguyen

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='a89ta6$9u8$2@main.gmane.org' \
    --to=neil@ossau.uklinux.net \
    --cc=evan@glug.org \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@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).