From: Carl Worth <cworth@cworth.org>
To: notmuch@notmuchmail.org
Subject: Plans for the 0.2 release (this week)
Date: Wed, 07 Apr 2010 15:12:44 -0700 [thread overview]
Message-ID: <8739z6rjxf.fsf@yoom.home.cworth.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1552 bytes --]
We've obviously got a lot of interest in notmuch, and a huge pile of
features that need to be merged.
I think that means we're in a state where we can have extremely regular
releases, with continually improving feature sets. I'm thinking releases
once per week or so.
With each release, I expect people to remind me of their favorite
features that haven't been merged, (while I'll continue to work through
any backlog on my own).
For the upcoming 0.2 release, here are some things that I would like to
have in place:
* Any further changes from the Sebastian's repository. Sebastian, I
worked through one list I saw recently. Do you have another list to
propose yet?
* The big batch of emacs-client improvements from David E.'s
repository. David, do you have particular things to recommend here?
* Changes to indexing, (addition of body:, folder:, list:, etc.). This
is stuff that I'll work on.
* Some library additions (move_to_first for the iterators, and perhaps
a notmuch_database_add_message_with_data which Srinivasa requested
to support integration of notmuch into evolution). I'll work on
these as well, (I know that there are patches for some of these on
the list already).
* Anything else that people want, (especially things that already
exist and that you're already using). Support for maildir flags on
import would be great here. I'm still waiting to see a complete
solution I think.
So keep the patches coming, and the pointers to patches that you want me
to look at.
-Carl
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2010-04-07 22:12 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 22:12 Carl Worth [this message]
2010-04-07 22:23 ` Plans for the 0.2 release (this week) James Westby
2010-04-08 14:34 ` Mike Kelly
2010-04-12 18:27 ` Mike Kelly
2010-04-08 7:47 ` Sebastian Spaeth
2010-04-08 12:21 ` Anthony Towns
2010-04-13 16:02 ` Carl Worth
2010-04-08 8:13 ` David Edmondson
2010-04-08 14:54 ` Dirk Hohndel
2010-04-08 13:52 ` Jameson Rollins
2010-04-08 14:55 ` Dirk Hohndel
2010-04-13 16:06 ` Carl Worth
2010-04-08 14:03 ` Jameson Rollins
2010-04-08 14:58 ` Dirk Hohndel
2010-04-08 15:21 ` Michal Sojka
2010-04-08 15:57 ` draft handling [was: Re: Plans for the 0.2 release (this week)] Jameson Rollins
2010-04-08 21:28 ` Plans for the 0.2 release (this week) Carl Worth
2010-04-08 21:38 ` Jameson Rollins
2010-04-09 0:22 ` Mike Kelly
2010-04-08 15:30 ` Mike Kelly
2010-04-09 3:22 ` Anthony Towns
2010-04-09 4:25 ` Michal Sojka
2010-04-09 16:21 ` micah anderson
2010-04-08 14:22 ` Michal Sojka
2010-04-09 4:32 ` Michal Sojka
2010-04-09 7:35 ` Sebastian Spaeth
2010-04-09 17:14 ` Dirk Hohndel
2010-04-10 3:06 ` Carl n∅tmuch 䚳 Worth
2010-04-10 4:44 ` Dirk Hohndel
2010-04-10 4:47 ` Dirk Hohndel
2010-04-10 13:05 ` Jameson Rollins
2010-04-10 14:39 ` Dirk Hohndel
2010-04-10 9:02 ` Michal Sojka
2010-04-10 13:06 ` Jameson Rollins
2010-04-10 13:09 ` Jameson Rollins
2010-04-10 14:06 ` Michael Elkins
2010-04-10 19:58 ` Michal Sojka
2010-04-10 13:52 ` Sebastian Spaeth
2010-04-10 13:56 ` Jameson Rollins
2010-04-10 14:41 ` Dirk Hohndel
2010-04-13 17:20 ` Carl Worth
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=8739z6rjxf.fsf@yoom.home.cworth.org \
--to=cworth@cworth.org \
--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).