mantisbt:release_process
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
mantisbt:release_process [2014/02/08 15:52] – dregad | mantisbt:release_process [2020/09/25 14:47] – [Bugtracker] link to manage project page dregad | ||
---|---|---|---|
Line 41: | Line 41: | ||
* optional features (e.g., graphs) | * optional features (e.g., graphs) | ||
- | The test process for Mantis in the Debian distro can be found at http://svn.debian.org/ | + | For reference, you may also read the [[http://anonscm.debian.org/ |
Line 74: | Line 74: | ||
* Remove references to any debug statements | * Remove references to any debug statements | ||
* Update CREDITS file. | * Update CREDITS file. | ||
- | * If necessary, update the '' | + | * If necessary, |
* Run the script to update the Contributor' | * Run the script to update the Contributor' | ||
$ update-credits.sh | $ update-credits.sh | ||
Line 80: | Line 80: | ||
* If needed, make any additional changes manually | * If needed, make any additional changes manually | ||
* Update the version number in core/ | * Update the version number in core/ | ||
- | * Update doc/RELEASE to include the release notes. | ||
* Commit the changes. | * Commit the changes. | ||
+ | |||
===== Cutting the Release ===== | ===== Cutting the Release ===== | ||
- | * Create an annotated tag in Git, the tag should be formatted as " | + | * Create an annotated, GPG-signed |
- | * For stable releases: GPG-signed tag < | + | |
$ git checkout master-1.M.x | $ git checkout master-1.M.x | ||
$ VERSION=1.M.N | $ VERSION=1.M.N | ||
$ git tag -s release-$VERSION -m " | $ git tag -s release-$VERSION -m " | ||
</ | </ | ||
- | * For development releases: unsigned, annotated tag < | + | * For **development releases** (e.g. alpha, beta, release candidates) |
$ git checkout master | $ git checkout master | ||
$ VERSION=1.M.N | $ VERSION=1.M.N | ||
- | $ git tag -a release-$VERSION -m " | + | $ git tag -s release-$VERSION -m " |
</ | </ | ||
Line 111: | Line 111: | ||
**Troubleshooting failure to sign tags** | **Troubleshooting failure to sign tags** | ||
- | Signing the tag fail if GIT cannot map the user with the gpg key, as in the example below < | + | Signing the tag fails if GIT cannot map the user with the gpg key, as in the example below < |
$ git tag -s release-$VERSION -m " | $ git tag -s release-$VERSION -m " | ||
gpg: skipped "Your Name < | gpg: skipped "Your Name < | ||
Line 150: | Line 150: | ||
* Update Versions | * Update Versions | ||
- | - Go to the //Manage Projects page// for the // | + | - Go to the [[https://mantisbt.org/ |
- | - Update the version being released (//1.M.x//): | + | - Update the version being released ('' |
- | * Rename it to //1.M.N// | + | * Rename it to '' |
- | * Update the "Date Order" | + | * Update the //Date Order// field to the actual release date |
- | * Copy-paste the text from the release notes into the "Description" | + | * Copy-paste the text from the release notes into the //Description// field, update as appropriate |
- | * Tick the "Released" | + | * Tick the //Released// box |
- | - Create a new //1.M.x// version | + | - Create a new '' |
- | * Set the "Date Order" | + | * Set the //Date Order// field to a future date <WRAP important 90%> |
- | * Make sure the "Released" | + | The [[mantisbt: |
+ | |||
+ | For this to work properly, it is important that the **version targeted by the //master// branch always has the most recent date**. Adjust it if necessary (e.g. when cutting a patch release). | ||
+ | </ | ||
+ | * Make sure the //Released// box is not ticked | ||
* Update issues | * Update issues | ||
- Go to the //View Issues page// | - Go to the //View Issues page// | ||
- Close all resolved issues that are fixed in the version being released | - Close all resolved issues that are fixed in the version being released | ||
- | * Set a new filter: //Status// = resolved, //Fixed in Version// = 1.M.N | + | * Set a new filter: //Status// = resolved, //Fixed in Version// = '' |
* Review listed issues, update them as needed (in particular, check that // | * Review listed issues, update them as needed (in particular, check that // | ||
* Tick the //Select all// checkbox | * Tick the //Select all// checkbox | ||
Line 169: | Line 173: | ||
* Click the //Close Issues// button | * Click the //Close Issues// button | ||
* Repeat until the filter is empty | * Repeat until the filter is empty | ||
- | - Carry open issues still targeted to 1.M.N over to the new 1.M.x version | + | - Carry open issues still targeted to '' |
- | * Set a new filter: //Hide Status// = closed (And Above), //Target Version// = 1.M.N | + | * Set a new filter: //Hide Status// = closed (And Above), //Target Version// = '' |
* Tick the //Select all// checkbox | * Tick the //Select all// checkbox | ||
* Select //Update Target Version// and click OK | * Select //Update Target Version// and click OK | ||
- | * Select | + | * Select |
* Repeat until the filter is empty | * Repeat until the filter is empty | ||
Line 182: | Line 186: | ||
* Edit main website' | * Edit main website' | ||
* Update '' | * Update '' | ||
+ | |||
+ | ==== Nightly builds ==== | ||
+ | |||
+ | When releasing a new //major// (X+1.0.0) or //minor// (X.Y+1.0) release, the nightly builds script must be updated so that the files are generated for the appropriate branches. | ||
+ | |||
+ | * Edit the script ''/ | ||
+ | * Update the // | ||
+ | |||
+ | To make the change permanent, the file should be committed to the // | ||
+ | |||
+ | If desired, the script may be executed manually at this point. Note that it normally does not produce any output; check the log file at ''/ | ||
+ | |||
+ | < | ||
Line 206: | Line 223: | ||
=== Manual process === | === Manual process === | ||
- | Also refer to MantisBT Administration Guide [[http:// | + | Also refer to MantisBT Administration Guide [[http:// |
**Upgrade Official Bug Tracker Instance** | **Upgrade Official Bug Tracker Instance** | ||
Line 213: | Line 230: | ||
* Update the code from git < | * Update the code from git < | ||
$ cd / | $ cd / | ||
- | $ git checkout master-1.2.x | + | $ git checkout master-1.3.x |
$ git pull --rebase | $ git pull --rebase | ||
$ git checkout bugs | $ git checkout bugs | ||
- | $ git rebase master-1.2.x | + | $ git rebase master-1.3.x |
- | </ | + | |
- | * Upgrade the database if needed (admin/ | + | |
- | * Run admin/ | + | |
- | * Login and do simple testing. | + | |
- | + | ||
- | + | ||
- | **Upgrade Demo Instance** | + | |
- | + | ||
- | * Make sure you are running as root (sudo bash) | + | |
- | * Update the code from git < | + | |
- | $ cd / | + | |
- | $ git checkout master-1.2.x | + | |
- | $ git pull --rebase | + | |
- | $ git checkout demo | + | |
- | $ git rebase master-1.2.x | + | |
</ | </ | ||
* Upgrade the database if needed (admin/ | * Upgrade the database if needed (admin/ | ||
Line 239: | Line 241: | ||
===== Publishing the Release ===== | ===== Publishing the Release ===== | ||
+ | |||
==== Source Forge ==== | ==== Source Forge ==== | ||
- | * Upload the release to Source Forge via the File Manager web interface | + | * Upload the release to [[http:// |
* Release through the SF.net mechanism. | * Release through the SF.net mechanism. | ||
- | * The release name should be "1.2.x" (e.g. 1.2.9). | + | * The release name should be "1.3.x" (e.g. 1.3.3). |
* Put the release in the appropriate package based on whether it is a stable or a development release. | * Put the release in the appropriate package based on whether it is a stable or a development release. | ||
- | * Release candidates | + | * Release candidates, alphas |
* Download the release off SF.net and verify correctness. | * Download the release off SF.net and verify correctness. | ||
* Click the " | * Click the " | ||
* for digests, exclude them from stats. | * for digests, exclude them from stats. | ||
- | * for zip make it default for all platforms. | + | * In case of a stable release, make the zip file the default for all platforms. |
- | * for README file exclude from stats. [1] | + | |
- | * Post news on Mantis SF project area. | + | |
+ | ==== Notifications ==== | ||
- | [1] [dregad] The Build release | + | * Blog: Post an announcement |
+ | * Twitter: announce the release | ||
+ | * Update mailing list based on official bug tracker users since users can now signup to our bugtracker to get such announcements. | ||
+ | * Use sendgrid to send out the announcement email. | ||
+ | ===== Prepare for next release ===== | ||
+ | ==== Bump the version number ==== | ||
- | ==== Notifications ==== | + | The MantisBT version constant must be increase to reflect the current state of the development branch. |
- | * Blog: Post an announcement | + | This ensures that people running Mantis from the GIT repository are not led to believe they are working with an official |
- | * Twitter: announce | + | |
- | * IRC: Change the title of #mantishelp to announce the new release and encourage people to use it. | + | * Edit '' |
- | * Forums: Announce | + | * Update // |
- | * Mailing Lists: Send a message to mantisbt-announce / mantisbt-dev to announce the new release and encourage users to upgrade. | + | * Major version: **x+1**.0.0**-dev** |
+ | * Minor version: x.**y+1**.0**-dev** | ||
+ | * Patch version: x.y.**z+1-dev** | ||
+ | * Commit and push the modified file | ||
mantisbt/release_process.txt · Last modified: 2022/05/10 10:07 by dregad