From: David Bremner <david@tethera.net>
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: Winter is coming [upcoming release 0.10]
Date: Mon, 21 Nov 2011 07:50:55 -0400 [thread overview]
Message-ID: <878vn9u21s.fsf@zancas.localnet> (raw)
In-Reply-To: <87zkfwn4lm.fsf@zancas.localnet>
[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]
On Tue, 15 Nov 2011 23:11:49 -0400, David Bremner <david@tethera.net> wrote:
> We are now frozen for 0.10 release. As is my habit, I tagged 0.10_rc1,
> but didn't upload tarballs. I also upload 0.10~rc1 packages to Debian
> experimental.
I have now tagged 0.10_rc2, which mainly has doc changes since _rc1,
except for two patches trying to make the test suites use of dtach more
robust.
The emacs tests are still failing on the Debian autobuilders (not sure
why) and in places where TMPDIR is set to some absurdly long path. We
may or may not need to fix this before release.
The license of notmuch-deliver is a concern. notmuch-deliver is GPL2
(only) and notmuch is GPL3+. Now, I'm fairly confident that notmuch
upstream is not going to sue, but it seems that binaries of
notmuch-deliver are probably not distributable according to a strict
reading of the licenses (or the FSF FAQ).
We still are missing a few NEWS items; some of which which we could
perhaps ignore.
>
> Ali Polatel:
> Some announcement for notmuch-deliver in contrib
>
> Dmitry Kurochkin:
> emacs: add invisible space after the search widget field in notmuch-hello
This is probably ignorable from a NEWS point of view.
>
> Michal Sojka:
> Do not query on notmuch-search exit
>
[-- Attachment #2: Type: application/pgp-signature, Size: 315 bytes --]
prev parent reply other threads:[~2011-11-21 11:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 14:19 Winter is coming [upcoming release 0.10] David Bremner
2011-11-13 16:34 ` [PATCH] Don't link libnotmuch if libutil isn't linked in properly Tom Prince
2011-11-13 17:05 ` [PATCH] Link libutil using filenmae, rather than using -l Tom Prince
2011-11-13 19:09 ` David Bremner
2011-11-13 17:09 ` [PATCH] Don't link libnotmuch if libutil isn't linked in properly Tom Prince
2011-11-19 19:20 ` David Bremner
2011-11-13 17:13 ` Winter is coming [upcoming release 0.10] Austin Clements
2011-11-16 3:11 ` David Bremner
2011-11-16 3:13 ` [PATCH] NEWS: discuss contrib and nmbug David Bremner
2011-11-16 11:48 ` David Bremner
2011-11-16 15:30 ` Winter is coming [upcoming release 0.10] Tomi Ollila
2011-11-16 15:43 ` Austin Clements
2011-11-16 17:08 ` David Bremner
2011-11-16 20:37 ` Pieter Praet
2011-11-16 20:37 ` [PATCH 1/2] NEWS: add entries for stashing-related keybinding and tests Pieter Praet
2011-11-16 20:37 ` [PATCH 2/2] NEWS: fix some old typos and trailing whitespace Pieter Praet
2011-11-16 20:54 ` Tomi Ollila
2011-11-16 21:38 ` Pieter Praet
2011-11-17 6:21 ` Jani Nikula
2012-01-12 17:06 ` Pieter Praet
2012-01-13 3:11 ` David Bremner
2012-01-14 9:01 ` Pieter Praet
2011-11-16 22:17 ` Winter is coming [upcoming release 0.10] David Bremner
2011-11-16 23:26 ` Pieter Praet
2011-11-21 11:50 ` David Bremner [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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878vn9u21s.fsf@zancas.localnet \
--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).