unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Han-Wen Nienhuys <hanwen@cs.uu.nl>
Cc: guile-devel@gnu.org
Subject: Preparing 1.6.1.
Date: Tue, 3 Sep 2002 01:51:40 +0200	[thread overview]
Message-ID: <15731.63884.253669.136106@blauw.xs4all.nl> (raw)
In-Reply-To: <87ptvw3uen.fsf@raven.i.defaultvalue.org>

rlb@defaultvalue.org writes:
> 
> Just a heads up -- as far as I can see, we haven't had any
> showstopping bugs crop up in 1.5.8, so unless there's something I've
> missed, it's time for the 1.6.1 release.
> 
> Comments?  Anything that can't wait for 1.6.2?  If not, I'll be
> preparing/checking the release as I have time over the next day or
> two.  For anyone with spare time, I'd still be happy to accept any
> NEWS revisions or improvements, or other documentation fixes, but
> please coordinate with me so you don't commit something after I've
> tagged/built the release.

Am I missing something? Isn't 1.6 or 1.6.0 supposed to come before
1.6.1 ?

(Not that I care,  just as long as it gets released quickly.. :-) 

-- 

Han-Wen Nienhuys   |   hanwen@cs.uu.nl   |   http://www.cs.uu.nl/~hanwen 


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


  reply	other threads:[~2002-09-02 23:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-02 22:21 Preparing 1.6.1 Rob Browning
2002-09-02 23:51 ` Han-Wen Nienhuys [this message]
2002-09-03  0:52   ` Rob Browning
2002-09-03 16:32     ` 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=15731.63884.253669.136106@blauw.xs4all.nl \
    --to=hanwen@cs.uu.nl \
    --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).