• to-do for release

  last modified November 7, 2006 by ltucker

  1. [OK] Move our work in the branch to the trunk
  2. [OK] Point the buildout at the new repository location, update READMEs, homepage
  3. [OK] Kill any branches we've created
  4. [OK] Ping list about any branches we didn't create (they probably should be killed too)
  5. [OK?] Maybe put some stuff aside, not just banished to svn history, like the mod_python stuff (which we haven't reimplemented, but want to eventually)
  6. [OK] Move the buildout into the repository.  I propose z3/deliverance/buildout/trunk
  7. [OK] Review documentation in docs/ for accuracy, maybe move to web site (cabraham)
  8. [~OK] Check for docstrings
  9. [OK] Maybe add some more website documentation
  10. Put code through pylint (ianb)
  11. [~OK] Include an example (in the buildout?) -- maybe already done? there are some in the regular readme
  12. [OK] Live demo site.  Potentially deliverance.openplans.org, or something silly like mygirlyzope.openplans.org
  13. [N/A] If a live demo, then some process monitor
  14. [~OK] Maybe review the proxy command-line interface; I think it's messy (ianb)