1 The TODO list before 1.0:
3 - Convert the remaining commands to the new infrastructure. Commands
7 - More regression tests
9 - Go through the design of the UI and make sure there's nothing hard
10 to change in there that we'll regret later.
12 - Write a user guide. I'm thinking a document on the order of 10-30
13 pages that'll explain why one would want to use StGit, and how.
15 - Make sure the rest of the documentation is in good shape.
20 The future, when time allows or if someone else does them:
22 - Patch dependency tracking
23 - Multiple heads in a patch - useful for forking a patch,
24 synchronising with other patches (diff format or in other
26 - Numeric shortcuts for naming patches near top (eg. +1, -2)