unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: hanwen@byrd.xs4all.nl (Han-Wen Nienhuys)
Subject: Re: Branching for 1.8 on 2006-02-05
Date: Sun, 29 Jan 2006 12:45:00 +0000 (UTC)	[thread overview]
Message-ID: <dridcc$7sm$1@sea.gmane.org> (raw)
In-Reply-To: 87fyn8xtj3.fsf@zagadka.de

In article <87fyn8xtj3.fsf@zagadka.de>, Marius Vollmer  <mvo@zagadka.de> wrote:
>Hi,
>
>I need to kick myself to get going with the 1.8 release, and want to
>do it by just branching for 1.8 soon and thus get out of the way of
>the devlopment happening on the trunk.
>
>I want to branch next weekend, on Sunday, 5. Feb.  Before that, the
>following things should be settled in trunk, I'd say:
>
>  Inlining `scm_is_pair ()'
>  `try-module-autoload' and `current-reader'
>  API naming bugs (the "frame" name issue)
>  Backtrace and enhanced catch
>
>I'll take care that this happens.
>
>(What we have in the 1.8 branch is not immediately the 1.8.0 release,
>but should be very close.)

YAY!




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


  parent reply	other threads:[~2006-01-29 12:45 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 [this message]
2006-02-03 23:49 ` Kevin Ryde
2006-02-04 19:38   ` Rob Browning
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='dridcc$7sm$1@sea.gmane.org' \
    --to=hanwen@byrd.xs4all.nl \
    --cc=hanwen@xs4all.nl \
    /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).