Hi,
I was also thinking that we need a 'howto release' document.
Modification of your Outline (also based on 1.5 release):
0. Implement and close all tickets in a specific milestone (now 1.6
milestone)
1. Be sure that the current code configures and compiles
2. Recompile bootloaders every supported OS
- visual studio 2008 on Windows (32bit and 64bit)
- LSB 4.0 on Linux (32bit and 64bit)
- gcc bundled in Mac OS X (32bit and 64bit)
3. Run tests on win, linux and mac with different python versions
4. Update CHANGES file
5. Update manual
6. Bump version in PyInstaller.__init__.py module (remove 'dev')
7. Build html and pdf manuals with new version
8. Optional: Build binaries of some real app with new version
9. Check in everything
10. Create branch for the release with name 'X.Y' where is X-major
version and Y-minor version number
11. Export the checkout by 'svn export' to ensure that everything is
there and all .svn files are removed
12. Build release files (.tgz, .zip, ...)
13. Tag the release:
14. Test release files
15. Upload release files to www.pyinstaller.org/static/source/X.Y
Update website, wiki, FAQ
16. Announce on:
- mailinglist
- http://freshmeat.net/projects/pyinstaller
- http://pypi.python.org/pypi/PyInstaller
Preparation for next release:
17. Discuss on mailinglist plan for next release
18. Increment VERSION in trunk and append 'dev' to it (also look at
doc/source/...)
19. Add entry to ChangeLog and commit change as "Post-release version
bump."
19. Create new milestone
20. Assign new tickets to this milestone
I think for now it should be enough to have this document just in svn.
If there will be more development documentation then it would be better
to have it in wiki.
Hartmut Goebel píše v Út 10. 05. 2011 v 10:36 +0200:
> Hi,
>
> 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.
>
> 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
>
> What do you think? Should the become part of the sources or go into
> the
> wiki?
--
You received this message because you are subscribed to the Google Groups
"PyInstaller" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pyinstaller?hl=en.
