ReleaseProcess - SwensenSoftware/fseye GitHub Wiki
This page needs to be updated to reflect the migration from Google Code to GitHub
This processes has been adapted from Unquote's release process: https://code.google.com/p/unquote/wiki/ReleaseProcess
The latest revision in trunk is ready for release and all unit tests pass.
-
svn checkout
the head revision from trunk - Update version numbers (
<monumental>.<significant>.<minor or bug fix>
) and commit changes to trunk *AssemblyVersion
andAssemblyFileVersion
in\FsEye\AssemblyInfo.fs
- Build the Visual Studio 2010 solution in Release mode.
- Run package.bat
1. Enter the version number when prompted
1. Check the output for any errors
1. The Downloads zip will be located at
\builds\FsEye-<version>.zip
- Perform quality assurance * Unzip and test via the FsEye.fsx script in the F# interactive of at least Visual Studio 2010
- Update the milestone for all issues which are being included in the release to the proper version number
- Search within
All issues
for-has:milestone status:fixed
- Click
Select: All
to select all of them - Choose "Bulk edit" action from the "Actions..." drop-down list
- Add the label
Milestone-Release<version number>
- Click "Update ## Issues" button to save
- Search within
- Update the ReleaseNotes
- Search within
All issues
formilestone:Release<version>
- Click the "CSV" link in the bottom right-hand corner of the issue list to export the issues to a csv file
- Open the csv file in Excel
- Delete all columns except for the ID and Summary columns from the csv
- Open up the ReleaseNotes wiki page for edit
- Copy and paste the records from the csv into the ReleaseNotes following the existing formatting conventions and save
- Search within
- Upload zip (now hosted by Swensen Software)
- TODO
Tag the head revision of the trunk with the name <version number>
.
Eliminate manual Visual Studio 2010 build step, this should be automated with a script.