[PyInstaller] How-to Release document?

[Hartmut Goebel]

Hi,




Outline (based on my own process which is based on OpenVAS'):
0. Requirments for building a release
1. Be sure that the current code configures and compiles
2. Run tests
3. Update VERSION: Remove suffix ".SVN"
4. Update CHANGES file
5. Bump version
6. Build Manuals with new version
7. Optional: Build binaries with new version
8. Check in everything
9. Export the checkout to ensure that everything is there (but not more)
10. Build release files (.tgz, .exe, ...)
11. Tag the release:
12. Test release files
13. Upload release files
14. Change VERSION again (also look at doc/source/...): append "dev"
15. Add entry to ChangeLog and commit change as "Post-release version bump."
16. Update website / wiki
17. Announce on mailinglist



--
Schönen Gruß - Regards
Hartmut Goebel
Dipl.-Informatiker (univ.), CISSP, CSSLP

Goebel Consult
Spezialist für IT-Sicherheit in komplexen Umgebungen
http://www.goebel-consult.de

Monatliche Kolumne: http://www.cissp-gefluester.de/
Goebel Consult mit Mitglied bei http://www.7-it.de

I'm thinking about a "howto release" document. This should describe what steps are to be performed when releasing. OpenVAS uses one an I find it very helpful. What do you think? Should the become part of the sources or go into the wiki?

smime.p7s
Description: S/MIME Cryptographic Signature