TPPDev:ReleaseChecklist
From SPCTools
(Difference between revisions)
| Revision as of 21:04, 26 October 2011 JoeS (Talk | contribs) (→Releasing) ← Previous diff |
Current revision Luis (Talk | contribs) (→Release Time) |
||
| Line 30: | Line 30: | ||
| * Upload source tar ball and windows installer to folder in sourceforge | * Upload source tar ball and windows installer to folder in sourceforge | ||
| - | |||
| ** Set default sourceforge download to be this release | ** Set default sourceforge download to be this release | ||
| * Update front page of tools.proteomecenter.org to point to version | * Update front page of tools.proteomecenter.org to point to version | ||
| + | ** Update ''ttpv.xml'' with newest version info | ||
| * Send notice out on spctools-announce and spctools-dev | * Send notice out on spctools-announce and spctools-dev | ||
Current revision
Checklist for releasing a TPP versions.
[edit]
Initiate
- Create a subversion branch from trunk
- Notify spctools-dev about the new branch (remind developers check in policy)
[edit]
Pre-release Preparation
- Copy current release's release notes wiki page on tools.proteomecenter.org and edit appropriately
- Create a dump of the svn log for the branch
- Create a new folder for the release in sourceforge
- Create release candidates, upload to sourceforge, rinse, repeat
[edit]
Release Time
- Tag branch
- Export (using version tag) TPP source
- Build source tar ball
- Build windows installer and test
- Update svn log for the release on tools.proteomecenter.org
- Finalize tools.proteomecenter.org release notes for the release
- Upload source tar ball and windows installer to folder in sourceforge
- Set default sourceforge download to be this release
- Update front page of tools.proteomecenter.org to point to version
- Update ttpv.xml with newest version info
- Send notice out on spctools-announce and spctools-dev
