The TODO list before 1.0:
-- automatic patch signing (probably at import time)
- more regression tests
-- stg help should probably pipe through the $PAGER
-- configurable pull command (currently uses git-pull only)
-- fix StGIT to run correctly in subdirectories
+
+- Convert the remaining commands to the new infrastructure.
+
+- Go through the design of the UI and make sure there's nothing hard
+ to change in there that we'll regret later.
+
+- Write a user guide. I'm thinking a document on the order of 10-30
+ pages that'll explain why one would want to use StGit, and how.
+
+- Make sure the rest of the documentation is in good shape.
+
- use a separate index for some commands (refresh, fold etc.) so that
files already added/removed are not automatically checked in
-- interactive resolve command to invoke xxdiff, emacs etc.
-- debian package support
-- man page
-- document the workflow on the StGIT wiki
-- maybe a separate undo command rather than passing a --undo option to
- push and refresh
-- use same configuration file as GIT
+
+ + This is easily done with the new infrastructure. refresh now
+ uses a separate index when appropriate. fold has not yet been
+ converted.
+
- release 1.0
- multiple heads in a patch - useful for forking a patch,
synchronising with other patches (diff format or in other
repositories)
-- write bash-completion script for the StGIT commands
-- "pull" argument should default to a sane value, "origin" is wrong in
- many cases
-- commit directly to a patch which is not top
-- patch synchronisation between between branches (as some people,
- including me have the same patches based on different branches and
- they have scripts for moving the changes in one to the others)
+- numeric shortcuts for naming patches near top (eg. +1, -2)
+- (config?) parameter for number of patches included by "series -s"
~mdw / stgit / blobdiff