From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: Re: Feature freeze for notmuch 0.30: June 1
Date: Tue, 16 Jun 2020 09:05:19 -0300 [thread overview]
Message-ID: <87wo47usg0.fsf@tethera.net> (raw)
In-Reply-To: <87blm2xoxt.fsf@tethera.net>
[-- Attachment #1.1: Type: text/plain, Size: 399 bytes --]
I've tagged a 3rd release candidate (which is of course rc2, because
this week I belong to the cult of 0 based indexing). All of the blockers
I know of are fixed, and I'd consider us in "deep freeze", hopefully to
release in a week or so if there are no nasty bugs discovered.
Please test. Debian users can grab it from Debian experimental (really
this time, previously it had to go though NEW).
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2020-06-16 12:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-24 22:03 Feature freeze for notmuch 0.30: June 1 David Bremner
2020-06-02 0:59 ` David Bremner
2020-06-16 12:05 ` David Bremner [this message]
2020-06-17 9:18 ` Dan Čermák
2020-06-17 11:53 ` Tomi Ollila
2020-06-17 12:49 ` Tomi Ollila
2020-06-17 23:55 ` crypto test failures on Fedora and OpenSUSE David Bremner
2020-06-20 15:45 ` David Bremner
2020-06-28 11:33 ` David Bremner
2020-07-02 5:06 ` Daniel Kahn Gillmor
2020-07-02 8:28 ` Dan Čermák
2020-07-02 18:00 ` [PATCH 1/2] configure: can gpgme can verify signatures when decrypting with a session key? Daniel Kahn Gillmor
2020-07-02 18:00 ` [PATCH 2/2] tests: mark sig verification known-broken with session keys on buggy gpgme Daniel Kahn Gillmor
2020-07-03 1:13 ` [PATCH 1/2] configure: can gpgme can verify signatures when decrypting with a session key? David Bremner
2020-07-03 11:35 ` David Bremner
2020-07-03 11:15 ` Feature freeze for notmuch 0.30: June 1 David Bremner
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=87wo47usg0.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).