From: Andy Wingo <wingo@pobox.com>
To: guile-devel@gnu.org
Subject: 2.2.0 release plan
Date: Tue, 14 Mar 2017 16:01:37 +0100 [thread overview]
Message-ID: <87bmt37vhq.fsf@pobox.com> (raw)
Hi,
I think we are ready to go for 2.2.0. I am going to make a provisional
2.2.0 tag today and update the version. I will dist a tarball and
upload to somewhere provisional.
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.
This will give us a chance to update the web site, prepare nice release
notes, make a binary build using the new "guix pack", and test
everything out. It could be we find some showstopper like a libtool age
issue or something. If that's the case, we can fix it and re-spin a
release. Since I won't have uploaded the tag, all should be good.
Thoughts welcome :)
Andy
next reply other threads:[~2017-03-14 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 15:01 Andy Wingo [this message]
2017-03-14 15:25 ` 2.2.0 release plan Greg Troxel
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=87bmt37vhq.fsf@pobox.com \
--to=wingo@pobox.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).