forked from mochi/mochikit
-
Notifications
You must be signed in to change notification settings - Fork 0
Guide: building & packaging a release
cederberg edited this page Oct 12, 2010
·
4 revisions
A checklist for building and packaging a new MochiKit release. The version number 1.4 is used as an example below.
- Check all tests in various browsers (Firefox, Internet Explorer, Safari, Chrome...)
- Update doc/rst/MochiKit/VersionHistory.rst
- Run scripts/build.py
- Tag last commit as MochiKit-1.4
- Switch to the web site branch --
git checkout gh-pages
- Merge in all changes (docs, code) --
git merge master
- Add MochiKit-1.4.zip file to dist directory
- Update download.html to point to new version
- Announce on mailing list and freshmeat.net
- Prepare master branch for next major version by updating all version numbers in the source code