PageRenderTime 28ms CodeModel.GetById 18ms RepoModel.GetById 1ms app.codeStats 0ms

Unknown | 33 lines | 29 code | 4 blank | 0 comment | 0 complexity | 4ae35f9be0fcb090933abb648910f591 MD5 | raw file
  1. Steps that we take when doing releases (so we don't forget)
  2. ===Tarball===
  3. All instructions assume a current working directory of trunk
  4. 1) Be sure changelog is up to date. Check the commit messages for important bug fixes, enhancements, features, etc.
  5. 2) Increment version number in changelog and (change "svn HEAD" to "version x.x.x")
  6. 3) Be sure man pages are up to date.
  7. 4) Update VERSION variable in src/google
  8. 5) Update version keyword argument in
  9. 6) cp src/ src/google ; chmod 755 src/google
  10. 7) Regenerate man page per instructions in src/google
  11. 8) Commit all these changes with a message like "Change to x.x.x" or "Committing updated version numbers x.x.x"
  12. 9) Use sdist to make the source distribution
  13. 10) cd dist ; tar xf googlecl-x.x.x.tar.gz ; cd googlecl-x.x.x/
  14. 11) chmod 755 src/google (sdist apparently sets whatever permissions it feels like)
  15. 12) When you're convinced it's correct, use svn copy to tag the release:
  16. $ svn copy -m "x.x.x release"
  17. 13) Update release at pypi:
  18. ===Debian package===
  19. Our .deb build currently uses git-buildpackage with a private git repo (sorry, hackers).
  20. ===Windows executable===
  21. Note: This will only work from a windows machine with py2exe installed. You MUST use Python 2.5
  22. 1) Run 'cmd' to get a terminal
  23. 2) cd to the src directory of the repository, where win_setup is.
  24. 3) Copy to google.
  25. 4) Run "C:\path\to\python25\python.exe py2exe -O2" That's a capital "o", then a 2
  26. 5) LEGAL WORRY: After py2exe does its thing, ***REMOVE MSVCR71.dll*** from the newly created dist/
  27. 6) Copy trunk/README.txt and trunk/README.config into dist/
  28. 7) Rename dist/ to googlecl (or what have you) and zip it up.
  29. On legal worries: As far as I can tell, it is a breach of the EULA to distribute that DLL unless you own a license for Microsoft Visual C++, which I do not. Users that need it can follow the instructions on the wiki's SystemRequirements page