From: Behalf Of Martin Zibricky May 10, 2011 5:40 AM
> I was also thinking that we need a 'howto release' document.

It is very good practice; I use them to great advantage.

> Modification of your Outline (also based on 1.5 release):

One suggestion: It seems a lot of the steps are "release prep" and
should be done first. "Release" usually consists of bumping the
version number, whatever final rebuilds result from that, and done.

Release prep:

> 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
> 8. Optional: Build binaries of some real app with new version
> 9. Check in everything
> 11a. Export the checkout by 'svn export' to ensure that everything is
> there and all .svn files are removed

Release:

> 6. Bump version in PyInstaller.__init__.py module (remove 'dev')
> 7. Build html and pdf manuals with new version
> 10. Create branch for the release  with name  'X.Y' where is X-major
> version and Y-minor version number
> 11b. Export the checkout by 'svn export' to have an svn-free tarball
> 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

Update Trac with new version number (see bug #334)

> 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.

...Stu

-- 
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.

Reply via email to