From: David Bremner <firstname.lastname@example.org> To: email@example.com Subject: Release process for notmuch 0.35 Date: Mon, 10 Jan 2022 08:34:11 -0400 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) I plan to do a feature freeze around the end of January, with a release in the first week or so of February. As usual I'll be soliciting NEWS updates after the feature freeze. d
next reply other threads:[~2022-01-10 12:34 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-10 12:34 David Bremner [this message] 2022-01-10 12:36 ` David Bremner 2022-01-29 22:34 ` 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Release process for notmuch 0.35' \ /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
Code repositories for project(s) associated with this inbox: notmuch.git.git (no URL configured) 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).