From: Nala Ginrut <nalaginrut@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: draft 3.0 release schedule
Date: Sat, 14 Dec 2019 08:26:16 +0800 [thread overview]
Message-ID: <CAPjoZof=ngCV_aOYxvakRiM6a-ZptXrtVxXmOu4zh2iTUV4QUw@mail.gmail.com> (raw)
In-Reply-To: <87lfriwo7x.fsf@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 377 bytes --]
Finally!
On Thu, Dec 12, 2019, 05:27 Andy Wingo <wingo@pobox.com> wrote:
> Hi,
>
> I've been trying to put out releases on an every-other-Friday schedule.
> Due to holidays I will probably bump this next one (2.9.7) up to this
> Friday. Current plan would then be to do 2.9.8 on 3 January 2020, and
> then if all goes well 3.0.0 on 17 January 2020.
>
> Cheers,
>
> Andy
>
>
[-- Attachment #2: Type: text/html, Size: 674 bytes --]
prev parent reply other threads:[~2019-12-14 0:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 21:23 draft 3.0 release schedule Andy Wingo
2019-12-14 0:26 ` Nala Ginrut [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='CAPjoZof=ngCV_aOYxvakRiM6a-ZptXrtVxXmOu4zh2iTUV4QUw@mail.gmail.com' \
--to=nalaginrut@gmail.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).