From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: Guile 1.7.91 has been released.
Date: Tue, 14 Feb 2006 23:32:00 +0200 [thread overview]
Message-ID: <87d5hpzkxb.fsf@zagadka.de> (raw)
In-Reply-To: <dssf98$33n$1@sea.gmane.org> (Han-Wen Nienhuys's message of "Tue, 14 Feb 2006 11:35:04 +0000 (UTC)")
hanwen@byrd.xs4all.nl (Han-Wen Nienhuys) writes:
> what is your plan for maintaining the branches?
The release-1-6 branch remains stable of course, and the release-1-8
branch will be stable after 1.8.0 has been released, and is now in
feature freeze. "Stable" should mean "we try very hard to not
regress and to remain binary compatible".
> I've just put Ludovic's scm_t_sweep_statistics patch in HEAD, can I
> also put it 1.8?
No. :-) I will look at it more closely, tho. Maybe it makes sense to
put it into 1.8.1.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2006-02-14 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 23:15 Guile 1.7.91 has been released Marius Vollmer
2006-02-13 8:37 ` Han-Wen Nienhuys
2006-02-13 21:48 ` Kevin Ryde
2006-02-14 11:35 ` Han-Wen Nienhuys
2006-02-14 21:32 ` Marius Vollmer [this message]
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=87d5hpzkxb.fsf@zagadka.de \
--to=mvo@zagadka.de \
--cc=guile-devel@gnu.org \
--cc=guile-user@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).