Differences

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

--- 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/06/06 15:21] (current) – [Prerequisites] aneiman
@@ 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.
+To upload translations to Launchpad, you will also need to register an ssh key with Launchpad. See the [[https://code.launchpad.net/~evergreen-bugs/evergreen/translation-export-3.13|3.13 translation page for an example]].
 See [[::versioning|Versioning]] for notes on the numbering scheme.
@@ Line 185: / Line 187: @@
   * 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/tools/make_release -v 3.13-beta -f origin/tags/rel_3_12_3</code>
-    * For a .0 release, the script should start from (probably) the release candidate: <code bash>$ build/tools/make_release -v 3.13.0 -f origin/tags/rel_3_13_rc</code>
+    * For a .0 release, the script should start from the highest point release in the previous series: <code bash>$ build/tools/make_release -v 3.13.0 -f origin/tags/rel_3_12_3</code>
     * For a point release, the script should start from the previous point release in the series: <code bash>$ build/tools/make_release -v 3.13.1 -f origin/tags/rel_3_13_0</code>
   * Use the -v flag when your branch name does not match the normal pattern, otherwise auto-detect works
@@ Line 230: / Line 232: @@
     * Release notes go in ''/var/www/open-ils.org/documentation/release/''
+Because the release notes document is cumulative for each release series, a symbolic link exists for each release series so that (e.g.) ''RELEASE_NOTES_3_666.html'' points to the latest release in the series (e.g., ''RELEASE_NOTES_3_666.html'' → ''RELEASE_NOTES_3_666_7.html''). Therefore, when uploading the release notes, update that symbolic link. When uploading the first alpha or beta for a series, it will be necessary to create the symbolic link.
+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., ''https://evergreen-ils.org/documentation/release/RELEASE_NOTES_3_666.html'', not ''https://evergreen-ils.org/documentation/release/RELEASE_NOTES_3_666_7.html''.
 ==== "Tag" Working Branch (requires commit bit) ====