Revamp 'wizard summary', and start writing tutorial docs.

[wizard.git] / TODO

diff --git a/TODO b/TODO
index 7cf8c5b80d07419545734e592dc059e91ec2e76f..dda76d0444a4450b047becb2a60ec25b809585fc 100644 (file)
--- a/TODO
+++ b/TODO
@@ -10,6 +10,8 @@ TODO NOW:
 - Let 'wizard configure' be interactive
 - Parse output HTML for class="error" and give those errors back to the user,
   then boot them back into configure
+- Get rid of our custom sizing code and use dialog's built-in sizing (i.e. width=0, height=0).
+  Maybe our sizing code is superior, maybe not.
 
 - Replace gaierror with a more descriptive name (this is a DNS error)
 
@@ -124,6 +126,8 @@ OVERALL PLAN:
 
     X. Commit, with name "Appname x.y.z"
 
+    X. Tag as appname-x.y.z
+
     4. Checkout the master branch
 
     5. Merge the pristine branch in. Resolve any conflicts that our
@@ -265,8 +269,11 @@ OVERALL PLAN:
        perform a configuration in the production environment to extract
        out the canonical configuration files.
 
-   12. On the production server, call your wizard to perform an installation.
-       Inspect the generated configuration files, and implement:
+   12. On the production server, call your wizard to perform an installation;
+       be sure to use the option --no-commit in order to make propagating changes
+       back easier.  Inspect the generated configuration files (you can use `git
+       status` to find unversioned files that the installer created), and
+       implement:
             - extractors
             - substitutions
                 These are dictionaries of functions that perform extraction
@@ -298,7 +305,8 @@ OVERALL PLAN:
         script was buggy; try again.
 
     14. The current changes in the working copy should be merged in.  Add any new
-        files, and then `git commit --amend`.
+        files, and then `git commit --amend`.  `git push --force` to stick these
+        changes back in the "public" repository.
 
     15. In your local copy, you can pull the changes by doing `git reset --hard HEAD~`
         and then a `git pull` from the relevant source.  Otherwise, Git will complain