From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: priorities for 0.7
Date: Wed, 06 Jul 2011 09:55:00 -0700 [thread overview]
Message-ID: <877h7vgxi3.fsf@servo.factory.finestructure.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 2986 bytes --]
Hey, folks. Now that 0.6 is *finally* out the door, it's time to start
working on 0.7. As Interim Distinguished co-Chief Vice Tyrant I have
been tasked with starting the discussion on 0.7 release priorities.
Below is just the beginning of list of things that have been discussed
on the list that we should consider merging or working on for 0.7. It's
weighted towards stuff that I've worked on only because I'm more
familiar with the state of those patches. Please send follow-ups to
this list to elaborate on certain things, or bring up other patches that
should be considered [0]. We can then push on Carl to merge these ahead
of the 0.7 freeze.
- notmuch-new atomicity:
id:"1307822683-848-1-git-send-email-amdragon@mit.edu"
I believe that the above is that latest version of this series; Austin
can point us to the right one if it's not. This is an important
series that is long overdue to be merged. It should definitely be a
top priority.
- message/rfc822 part support:
id:"1307120466-4980-1-git-send-email-jrollins@finestructure.net"
id:"1307320169-29905-1-git-send-email-jrollins@finestructure.net"
rfc822 part handling is a bit broken now after the notmuch-show
rework. The above patch series should have been included in 0.6 to
fix a couple of regressions. In the meantime Austin and I have
started looking at further rework of notmuch-show to try to clean it
up even more. This rework might supersedes these patches, but it
depends on how far we get.
- emacs: Add notmuch-show-refresh-view function
id:"1306627784-3401-1-git-send-email-jrollins@finestructure.net"
- emacs: Add callback functions to crypto sigstatus button.
id:"1306861633-3873-1-git-send-email-jrollins@finestructure.net"
- emacs: notmuch-hello improvements (Daniel Schoepe, Michal Sojka,
Dmitry Kurochkin, Pieter Praet)
These guys have been working on various improvements to the
notmuch-hello page. I'll let them comment on where they're at with
that, and what should be merged.
- emacs: tagging race conditions (Austin Clements, Pieter Praet)
Austin and Pieter have been looking at home to eliminate some race
conditions when tagging from the emacs interface. I'll let them
comment on where that's at.
- emacs: default key bindings
There's been a lot of discussion about default key bindings for the
emacs UI. This issue frankly terrifies me since I worry that it is
basically impossible to converge on anything. I think we'll need to
see a specific full proposal before we can really consider what to do
here.
- I know there are other old patches that are sinking in to the abyss.
Hopefully any of those that are still relevant can be excavated.
jamie.
[0] It's maybe not mainline notmuch related, but we really need to get
some sort of tag sharing system worked out. I can only imagine what
useful info is encoded in Carl's tags that would be invaluable for
everyone else to see, especially the release managers.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next reply other threads:[~2011-07-06 16:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 16:55 Jameson Graef Rollins [this message]
2011-07-06 17:51 ` priorities for 0.7 Aneesh Kumar K.V
2011-07-06 17:56 ` Aneesh Kumar K.V
2011-07-06 19:08 ` David Bremner
2011-07-07 18:34 ` Daniel Schoepe
2011-07-07 19:55 ` David Bremner
2011-07-10 15:40 ` Daniel Schoepe
2011-07-10 12:58 ` David Bremner
2011-07-10 16:00 ` Pieter Praet
2011-07-10 16:34 ` Austin Clements
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=877h7vgxi3.fsf@servo.factory.finestructure.net \
--to=jrollins@finestructure.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).