From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: release plans: 0.23.6, 0.24
Date: Wed, 22 Feb 2017 06:53:05 -0400 [thread overview]
Message-ID: <87bmtu4hv2.fsf@tethera.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
I'd like to release another point release, 0.23.6 on Monday Feb. 27th.
This will be the gpgconf --create-socketdir patch, and all going well
something like id:20170222103207.10000-1-david@tethera.net.
I'll then do a feature freeze for 0.24 Monday March 6, and hopefully a
release on March 13.
This double release process saves me from having to backport the patches
for Debian; others may just want to wait for 0.24.
d
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 658 bytes --]
reply other threads:[~2017-02-22 10:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bmtu4hv2.fsf@tethera.net \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).