User Tools

  • Logged in as: anonymous (anonymous)
  • Log Out

Site Tools


mantisbt:release_process

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
mantisbt:release_process [2019/07/15 11:31]
dregad [Bugtracker] added notice for date order field and source control integration
mantisbt:release_process [2019/08/08 19:29] (current)
dregad [Repository Preparation] link to new mailmap page
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 ''​.mailmap'' ​file at the repository'​s root, so that commit made by the same person under different names and/or e-mail addresses are properly aggregated ​(refer to [[http://​www.kernel.org/​pub/​software/​scm/​git/​docs/​git-shortlog.html#​_mapping_authors|git shortlog man page]] for details)+    * If necessary, ​[[mantisbt:​mailmap|update the .mailmap file]], so that commit made by the same person under different names and/or e-mail addresses are properly aggregated
     * Run the script to update the Contributor'​s list <​code>​     * Run the script to update the Contributor'​s list <​code>​
 $ update-credits.sh $ update-credits.sh
Line 157: Line 157:
       * Tick the //​Released//​ box       * Tick the //​Released//​ box
     - Create a new ''​1.M.x''​ version     - Create a new ''​1.M.x''​ version
-      * Set the //Date Order// field to a future date <WRAP important ​60%>+      * Set the //Date Order// field to a future date <WRAP important ​90%>
 The [[mantisbt:​plugins:​sourceintegration]] relies on this date to automatically set the //Fixed in version// field when processing commits referencing issues for resolution (i.e. ''​Fixes #​xxx''​). ​ The [[mantisbt:​plugins:​sourceintegration]] relies on this date to automatically set the //Fixed in version// field when processing commits referencing issues for resolution (i.e. ''​Fixes #​xxx''​). ​
  
-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).+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).
 </​WRAP>​ </​WRAP>​
       * Make sure the //​Released//​ box is not ticked ​       * Make sure the //​Released//​ box is not ticked ​
mantisbt/release_process.1563204688.txt.gz ยท Last modified: 2019/07/15 11:31 by dregad