unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Branching for 1.8 on 2006-02-05
Date: Sat, 04 Feb 2006 11:38:45 -0800	[thread overview]
Message-ID: <87r76i7w3e.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <87ek2k80ks.fsf@zip.com.au> (Kevin Ryde's message of "Sat, 04 Feb 2006 10:49:39 +1100")

Kevin Ryde <user42@zip.com.au> writes:

>> (What we have in the 1.8 branch is not immediately the 1.8.0 release,
>> but should be very close.)
>
> Do you really want to branch at all?

For what it's worth, I'd say there a benefit to branching as late as
possible.  If there aren't any items waiting to be committed to the
upcoming 1.9 tree, then the longer we can continue working (toward the
release) on the main branch, the fewer commits will have to be applied
to two branches.

(Oh, and I still have at least one outstanding bit that needs to go
into 1.7.  I need to add the slib changes.  I hope to get to that
later today or sometime tomorrow.)

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4


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


  reply	other threads:[~2006-02-04 19:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-28 15:26 Branching for 1.8 on 2006-02-05 Marius Vollmer
2006-01-29  9:13 ` Neil Jerram
2006-01-29 12:45 ` Han-Wen Nienhuys
2006-02-03 23:49 ` Kevin Ryde
2006-02-04 19:38   ` Rob Browning [this message]
2006-02-05 19:02     ` Marius Vollmer
2006-02-05 20:30       ` Rob Browning
2006-02-06  9:25         ` Ludovic Courtès
2006-02-07  0:18           ` 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=87r76i7w3e.fsf@trouble.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=guile-devel@gnu.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).