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

[-- Attachment #1: Type: text/plain, Size: 886 bytes --]


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".

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.

The basic issue is that getting widespread testing relies on a bunch of
people for whom hacking on guile is one little thing among many, and not
their main Free Software focus.  This is not about guile; I see this in
a vast number of projects.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 162 bytes --]

  reply	other threads:[~2017-03-14 15:25 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 [this message]
2017-03-14 15:50   ` Andy Wingo
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=smupohjyj6t.fsf@linuxpal.mit.edu \
    --to=gdt@lexort.com \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.com \
    /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).