User Tools

Site Tools


dev:release_process:evergreen:2.8

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
dev:release_process:evergreen:2.8 [2018/04/18 17:36]
dbwells major revamp; try to separate core committer tasks from general buildmaster tasks
dev:release_process:evergreen:2.8 [2020/09/17 12:31] (current)
gmcharlton add a todo re the Angular staff interface
Line 26: Line 26:
  
 ==== Prepare release notes (for major version bumps only) ==== ==== Prepare release notes (for major version bumps only) ====
 +
 +=> See also the [[evergreen-docs:​release_notes_process|Release Notes Process for DIG Release Coordinator]]
  
   * Create release notes   * Create release notes
Line 45: Line 47:
  
 ==== Translations,​ Part 1: newpot (requires commit bit) ==== ==== Translations,​ Part 1: newpot (requires commit bit) ====
 +
 +TODO: NEED TO INCLUDE PROCESS FOR DEALING WITH POEDITOR FOR THE ANGULAR STAFF INTERFACE
  
   * During each release starting with beta, get the latest template changes and apply them to the main branch you are working from in origin (master/​rel_3_1/​etc.). ​ It is important to merge any new pot changes to origin so that Launchpad translations will get the latest strings that require translation.   * During each release starting with beta, get the latest template changes and apply them to the main branch you are working from in origin (master/​rel_3_1/​etc.). ​ It is important to merge any new pot changes to origin so that Launchpad translations will get the latest strings that require translation.
Line 104: Line 108:
 <code bash> <code bash>
 $ export PATH=$PATH:/​openils/​bin $ export PATH=$PATH:/​openils/​bin
-$ build/​tools/​make_release -c -v 2.8.0 -f origin/​tags/​rel_2_7_3+$ build/​tools/​make_release ​-x -c -v 2.8.0 -f origin/​tags/​rel_2_7_3
 </​code>​ </​code>​
  
Line 114: Line 118:
     * The -f flag sets the branch "​from"​ which this release this being made from, aka what was the last version of Evergreen prior to the one you're making. This guides the make_release towards creating a version-upgrade from X to Y.      * The -f flag sets the branch "​from"​ which this release this being made from, aka what was the last version of Evergreen prior to the one you're making. This guides the make_release towards creating a version-upgrade from X to Y. 
     * You can add the -r option to edit the upgrade script before it goes into the tarball. This may be necessary if tables that get altered in the upgrade scripts also have updates or inserts of new data.     * You can add the -r option to edit the upgrade script before it goes into the tarball. This may be necessary if tables that get altered in the upgrade scripts also have updates or inserts of new data.
 +    * You can add the -x option to **prevent the script from compiling and outputting the XUL staff client**.
 +
  
 ==== Generate release docs ==== ==== Generate release docs ====
dev/release_process/evergreen/2.8.1524087414.txt.gz · Last modified: 2018/04/18 17:36 by dbwells

© 2008-2017 GPLS and others. Evergreen is open source software, freely licensed under GNU GPLv2 or later.
The Evergreen Project is a member of Software Freedom Conservancy.