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