unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Greg Troxel <gdt@lexort.com>
Cc: guile-devel@gnu.org
Subject: Re: 2.2.0 release plan
Date: Tue, 14 Mar 2017 16:50:49 +0100	[thread overview]
Message-ID: <8737ef7t7q.fsf@pobox.com> (raw)
In-Reply-To: <smupohjyj6t.fsf@linuxpal.mit.edu> (Greg Troxel's message of "Tue, 14 Mar 2017 11:25:14 -0400")

On Tue 14 Mar 2017 16:25, Greg Troxel <gdt@lexort.com> writes:

> Andy Wingo <wingo@pobox.com> writes:
>
>> However!  Even though the code says 2.2.0 and the tag says 2.2.0, the
>> release is not until Thursday.  I will not upload the tag yet.
>
> I have just barely caught up with 2.0.x in pkgsrc, and haven't gotten to
> testing 2.1.x yet.  I wonder how many platforms 2.1.x has been tested
> on, and really I mean "has it been tested on other than GNU/Linux".

Things are in the early days, you are right.  GNU/Linux and macOS have
been tested.  Cygwin builds and works though it has some test errors; we
are working on it.  I don't know about mingw yet.  I think there might
be some errors on the other BSDs but I don't know yet.

> So if you think it's ready, I would suggest preparing a 2.2.0rc1, or
> simply a new 2.1.x with the notion that aside from version numbers it's
> an RC, and call for all people engaged in packaging to try to package it
> as 2.2, and to give them a few weeks.

I have done exactly that in the past weeks with 2.1.7 and 2.1.8 :) I
think a 2.2.1 will follow very soon (within a month or so from 2.2.0, I
would imagine), so any portability fixes will naturally be included
there.  That's about the same timeframe you are asking for, so all is
well in that regard.

Happy hacking,

Andy



  reply	other threads:[~2017-03-14 15:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-14 15:01 2.2.0 release plan Andy Wingo
2017-03-14 15:25 ` Greg Troxel
2017-03-14 15:50   ` Andy Wingo [this message]
2017-03-15  0:35     ` Matt Wette
2017-03-15  2:59       ` Matt Wette
2017-03-15 13:07         ` Matt Wette
2017-03-16  2:04           ` Matt Wette

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=8737ef7t7q.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=gdt@lexort.com \
    --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).