Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Rich Lane <rlane@club.cc.cmu.edu>
To: sup-devel <sup-devel@rubyforge.org>
Subject: [sup-devel] patch backlog cleared / plans
Date: Sat, 27 Feb 2010 15:29:35 -0500	[thread overview]
Message-ID: <1267296421-sup-7450@zyrg.net> (raw)

AFAIK I've applied or replied to all the patches floating on the list.
If I've ignored one please reply to it to let me know.

My current plan is to nuke ferret, make a few utf8 fixes, and then
release 0.11 in about a week with what's currently on master (big
features: saved searches and 256 color support). I'll also add a
deprecation warning to IMAP/mbox+ssh so that I can kill them on master
immediately after the release (giving me freedom to refactor the source
interface).

Once that's done, I'm going to gradually start integrating sup-server
features. First up is sup-cmd, which is basically an (incompatible)
notmuch CLI. This could be useful by itself (it outputs YAML, so it's
surprisingly human readable). Next is a sup-server executable that
sup-cmd connects to. Then comes an intermediate stage where a sup-server
can run inside the Ncurses UI, so that sup-cmd and the UI can be used
simultaneously. Finally, the difficult work of converting the UI to use
sup-server instead of accessing the index directly.

A major benefit of having a sup-server even if the UI can't use it is to
get some test coverage on Index internals.

I'll want to have a discussion about how best to change the UI to use
sup-server closer to that time. sup-server uses Actors and in the long
run I'd like to move the UI to that if only to kill our locking bugs. It
probably isn't necessary to actorify the UI to get it to use sup-server.

The release schedule for 0.12 will mostly depend on incoming patches. I
want to include sup-cmd at least so that people can figure out cool
things to do with it (more UIs).

I also hope to see maildir sync-back support in 0.12. Many people I've
tried to convert use mobile clients and tell me this is a dealbreaker,
so I think this is a very important feature. Is anyone currently working
on it?
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


                 reply	other threads:[~2010-02-27 20:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1267296421-sup-7450@zyrg.net \
    --to=rlane@club.cc.cmu.edu \
    --cc=sup-devel@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox