¡This is a work in progress. It will grow and change!
These recordings show various release building activities.
Make sure you are in an environment with your git ssh keys, since you will need to be pushing commits to the git server.
See Versioning for notes on the numbering scheme.
# sudo make -f Open-ILS/src/extras/Makefile.install <os>-packager $ sudo make -f Open-ILS/src/extras/Makefile.install ubuntu-focal-packager
[Note that your Ubuntu version may be something other than 'focal'; substitute the appropriate version keyword]
$ perl build/tools/relator_map > Open-ILS/src/templates/opac/parts/relators.tt2 $ cp Open-ILS/src/templates/opac/parts/relators.tt2 Open-ILS/src/templates-bootstrap/opac/parts/relators.tt2 # if 'git status' shows changes, commit them. $ git commit -sm "Updating relator codes for XXX" Open-ILS/src/templates/opac/parts/relators.tt2 Open-ILS/src/templates-bootstrap/opac/parts/relators.tt2
=> See also the Release Notes Process for DIG Release Coordinator
git checkout -b rel_3_7 main
$ vi docs/antora.yml
edit 'latest' -> '3.7'
$ cd docs/RELEASE_NOTES_NEXT $ ./create_release_notes.sh -r 2_8
$ find . -mindepth 2 -name '*.txt' -exec git rm {} \; $ find . -mindepth 2 -name '*.adoc' -exec git rm {} \;
$ ../tools/extract_release_notes_from_commits.pl --help $ ../tools/extract_release_notes_from_commits.pl --current-branch=rel_3_7_1 --prev-release-branch=rel_3_7_0
For an alpha or beta release, this rough process is probably enough. For a real #.0 release, the resulting compiled release notes will need some TLC/cleanup.
$ cd build/i18n && make newpot
python3 build/i18n/scripts/add_translations.py -c # use -h option for help
$ git checkout -b tags/rel_3_13_1 rel_3_13
$ cd ../; # Clone the repository if necessary $ bzr branch lp:~evergreen-bugs/evergreen/translation-export-main # for main branch $ bzr branch lp:~evergreen-bugs/evergreen/translation-export-3.12 # for 3.12.x, e.g. # If already cloned, simply pull in the latest changes $ cd translation-export-SERIES; bzr pull; cd ../
# series here is "main" or "3.10" or whatever corresponding to the release # that you are building $ Evergreen/build/i18n/scripts/update_pofiles -l translation-export-SERIES -e Evergreen $ cd Evergreen $ git add -A build # pick up updates $ git commit -sm "Translation updates - po files"
Open-ILS/src/eg2/src/locale/
and commit using the following steps:$ cp ~/download/path/messages.*.xtb ./Open-ILS/src/eg2/src/locale/ $ git add -A Open-ILS/src/eg2/src/locale/ $ git commit -asm "Translation updates - xtb files"
our $VERSION = '3.0101';
$ git commit -asm "bumping Perl version string for 2.8"
:%s/3.X.X/3.12.3/
will do the trick:%s/3.X.W/3.12.2/
will do the trick$ export PATH=$PATH:/openils/bin $ build/tools/make_release -v 2.8.0 -f origin/tags/rel_2_7_3
Note that you will get a lot of warnings related to the po translation files. These can be safely ignored.
From the Evergreen directory:
# copy README and release notes to ../release/ $ export RELEASE=3_12 $ cp README ../release/README_$RELEASE $ cp docs/RELEASE_NOTES_$RELEASE.adoc ../release/ $ cd ../release/ # in ../release/ $ asciidoc -a toc -a numbered README_$RELEASE $ asciidoc -a toc -a numbered RELEASE_NOTES_$RELEASE.adoc # delete the originals $ rm README_$RELEASE RELEASE_NOTES_$RELEASE.adoc
Move the release files into the correct download directories on the evergreen-ils.org web server (which is also known as lupin):
/var/www/open-ils.org/downloads/previews/
/var/www/open-ils.org/downloads/
/var/www/open-ils.org/documentation/install/
/var/www/open-ils.org/documentation/release/
git push origin tags/rel_3_12_1:tags/rel_3_12_1
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 you skip copying to the rel_x_y branch in particular, your next point release will be missing an upgrade script in the middle of the chain!