dev:release_process:evergreen:how_to_build
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| dev:release_process:evergreen:how_to_build [2024/05/14 09:16] – [Prepare release notes (for major version bumps only)] also remove content from miscellaneous.adoc sandbergja | dev:release_process:evergreen:how_to_build [2024/07/18 09:17] (current) – [Translations, Part 2: update_pofiles] sandbergja | ||
|---|---|---|---|
| Line 14: | Line 14: | ||
| Make sure you are in an environment with your git ssh keys, since you will need to be pushing commits to the git server. | Make sure you are in an environment with your git ssh keys, since you will need to be pushing commits to the git server. | ||
| + | |||
| + | To upload translations to Launchpad, you will also need to register an ssh key with Launchpad. See the [[https:// | ||
| See [[:: | See [[:: | ||
| Line 100: | Line 102: | ||
| During each release starting with beta, get the latest template changes and apply them to the main branch you are working from in origin (main/ | During each release starting with beta, get the latest template changes and apply them to the main branch you are working from in origin (main/ | ||
| - | * Update pot in Evergreen <code bash>$ cd build/i18n && make newpot</ | + | * Update pot in the Evergreen |
| * From the Evergreen directory, run the python script to commit any changes that do more than modify metadata <code bash> | * From the Evergreen directory, run the python script to commit any changes that do more than modify metadata <code bash> | ||
| Line 127: | Line 129: | ||
| * NOTE: See here to find the correct translation branch for the version you are building: https:// | * NOTE: See here to find the correct translation branch for the version you are building: https:// | ||
| + | * It will give you an error "You have not informed bzr of your Launchpad ID, and you must do this to write to Launchpad or access private data." | ||
| * Then, sync translated files with Evergreen. Update PO files in the appropriate branch in origin: | * Then, sync translated files with Evergreen. Update PO files in the appropriate branch in origin: | ||
| Line 185: | Line 188: | ||
| * Use the highest numbered previous version for the second version value. | * Use the highest numbered previous version for the second version value. | ||
| * For example, building 3.13-beta, the script should start from the highest 3.12 release at the time of branching: <code bash>$ build/ | * For example, building 3.13-beta, the script should start from the highest 3.12 release at the time of branching: <code bash>$ build/ | ||
| - | * For a .0 release, the script should start from (probably) | + | * For a .0 release, the script should start from the highest point release |
| * For a point release, the script should start from the previous point release in the series: <code bash>$ build/ | * For a point release, the script should start from the previous point release in the series: <code bash>$ build/ | ||
| * Use the -v flag when your branch name does not match the normal pattern, otherwise auto-detect works | * Use the -v flag when your branch name does not match the normal pattern, otherwise auto-detect works | ||
| Line 230: | Line 233: | ||
| * Release notes go in ''/ | * Release notes go in ''/ | ||
| + | Because the release notes document is cumulative for each release series, a symbolic link exists for each release series so that (e.g.) '' | ||
| + | |||
| + | When updating the downloads page to the website, the URL should use the symbolic link, not the release notes for the specific release, e.g., '' | ||
| ==== " | ==== " | ||
| Line 240: | Line 246: | ||
| If doing a final release, you will need to copy the upgrade script you created to main and your current rel_x_y branch. | If doing a final release, you will need to copy the upgrade script you created to main and your current rel_x_y branch. | ||
| + | For example, if you just created a release 3.12.6 and were on the branch tags/ | ||
| + | |||
| + | <code bash> | ||
| + | git checkout rel_3_12 | ||
| + | git checkout tags/ | ||
| + | git commit -sm " | ||
| + | git checkout main | ||
| + | git cherry-pick rel_3_12 | ||
| + | </ | ||
| ==== Announcing and recording the release ==== | ==== Announcing and recording the release ==== | ||
| * Update evergreen_history.txt file in history repo with release dates. | * Update evergreen_history.txt file in history repo with release dates. | ||
| * Release team / outreach committee make announcements following [[https:// | * Release team / outreach committee make announcements following [[https:// | ||
dev/release_process/evergreen/how_to_build.1715692609.txt.gz · Last modified: 2024/05/14 09:16 by sandbergja