unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Cc: Floris Bruynooghe <flub@devork.be>, Jonas Bernoulli <jonas@bernoul.li>
Subject: Release process for 0.32
Date: Sat, 10 Apr 2021 09:28:42 -0300	[thread overview]
Message-ID: <87eefitjb9.fsf@tethera.net> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 789 bytes --]


Now that the config changes have landed, it is time to consider a
release. I have the following schedule in mind:

         April 24: Feature Freeze.

         May 1: Release.

In a perfect world, the notmuch2 python bindings would be updated before
the release, but since the new API is upward compatible (and old API is
still there), I don't think this a blocker.

Typically we have a push for NEWS items after the feature freeze, but
nothing prevents getting started with some of the larger changes. I
think Jonas and I are responsible for the most of the churn in the
source. Jonas, I know a lot of what you contributed is not user visible,
but a patch for NEWS listing some of the user visible changes
(particularly things like dropped variables and functions) would be
appreciated.

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

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



             reply	other threads:[~2021-04-10 12:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-10 12:28 David Bremner [this message]
2021-04-10 12:52 ` [PATCH] NEWS: user visible config related changes for 0.32 David Bremner
2021-04-16 12:02   ` David Bremner
2021-04-24 16:36 ` Release process " David Bremner
2021-04-25 16:55   ` Felipe Contreras
2021-04-28 10:35   ` David Bremner
2021-04-28 13:24     ` Michael J Gruber
2021-04-28 14:14       ` David Bremner
2021-04-28  7:21 ` Jonas Bernoulli

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=87eefitjb9.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=flub@devork.be \
    --cc=jonas@bernoul.li \
    --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).