Difference between revisions of "Source Release for BES"

From OPeNDAP Documentation
m (Update the Version Numbers for Humans)
(Update the internal library (API/ABI) version numbers.)
 
(58 intermediate revisions by 2 users not shown)
Line 4: Line 4:
 
We now depend on the CI/CD process to build binary packages and to test the source builds.
 
We now depend on the CI/CD process to build binary packages and to test the source builds.
  
== The Release Process ==
 
 
:'''Tip''': If, while working on the release, you find you need to make changes to the code and you know the CI build will fail, do so on a ''release branch'' that you can merge and discard later. Do not make a release branch if you don't '''need''' it, since it complicates making tags.
 
:'''Tip''': If, while working on the release, you find you need to make changes to the code and you know the CI build will fail, do so on a ''release branch'' that you can merge and discard later. Do not make a release branch if you don't '''need''' it, since it complicates making tags.
  
===  Verify the code base ===
+
==  Verify the code base ==
# We release using the ''master'' branch. The code on ''master'' must pass the CI build.
+
# We release using the ''master'' branch. The code on ''master'' must have passed the CI builds. '''This includes the hyrax-docker builds since that CI build runs the full server regression tests!'''
 
# Make sure that the source code you're using for the following steps is up-to-date. (''git pull'')
 
# Make sure that the source code you're using for the following steps is up-to-date. (''git pull'')
  
=== Determine the scope of API/ABI changes in C++ sources ===
+
== Update the internal library (API/ABI) version numbers. ==
Determine the new software version (assuming you don't already know the extent of the changes that have been made)
+
The BES is '''''not''''' a shared library, it is a set of c++ applications that are typically built as statically linked binaries. Because of this the usual CURRENT:REVISION:AGE tuples used to express the binary compatibility state of a c++ shared object library have little meaning for the BES code. So, what we choose to do is simply bump the REVISION numbers by one value for each release.
: For C++, build a file of the methods and their arguments using the command:
 
:: <tt style="font-size: 1.1em; font-weight: bold;">nm .libs/libdap.a | c++filt | grep ' T .*::' | sed 's@.* T \(.*\)@\1@' > libdap_funcs</tt>
 
: and compare that using <tt>diff</tt> on the previous release's library.
 
Assess the changes you find based on the following rules for the values of <tt>CURRENT</tt>,<tt>REVISION</tt>, and <tt>AGE</tt>
 
* No interfaces changed, only implementations (good): ==> Increment REVISION.
 
* Interfaces added, none removed (good): ==> Increment CURRENT, increment AGE, set REVISION to 0.
 
* Interfaces removed or changed (BAD, breaks upward compatibility): ==> Increment CURRENT, set AGE and REVISION to 0.
 
The current value of  <tt>CURRENT</TT>,<tt>REVISION</tt>, and <tt>AGE</tt> can be found in <tt>configure.ac</tt>:
 
<source lang="bash">
 
LIB_DIS_CURRENT=14
 
LIB_DIS_AGE=6
 
LIB_DIS_REVISION=1
 
</source>
 
  
=== Update Release Files ===
+
* In the '''configure.ac''' file locate each of:
Once you have determined the new values of the <tt>CURRENT:REVISION:AGE</tt>  strings then:
+
** LIB_DIS_REVISION
* Edit the configure.ac and update the version values to the new ones.
+
** LIB_PPT_REVISION
 +
** LIB_XML_CMD_REVISION
 +
* Increase the value of each by one (1).
 +
* Save the file.
 
* Update the text documentation files and version numbers in the configuration files:
 
* Update the text documentation files and version numbers in the configuration files:
  
==== Update the '''ChangeLog''' file. ====
+
Example of the relevant section from configure.ac:
 +
<source lang-="bash">
 +
LIB_DIS_CURRENT=18
 +
LIB_DIS_AGE=3
 +
LIB_DIS_REVISION=3
 +
AC_SUBST(LIB_DIS_CURRENT)
 +
AC_SUBST(LIB_DIS_AGE)
 +
AC_SUBST(LIB_DIS_REVISION)
 +
LIBDISPATCH_VERSION="$LIB_DIS_CURRENT:$LIB_DIS_REVISION:$LIB_DIS_AGE"
 +
AC_SUBST(LIBDISPATCH_VERSION)
 +
 
 +
LIB_PPT_CURRENT=5
 +
LIB_PPT_AGE=1
 +
LIB_PPT_REVISION=2
 +
AC_SUBST(LIB_PPT_CURRENT)
 +
AC_SUBST(LIB_PPT_AGE)
 +
AC_SUBST(LIB_PPT_REVISION)
 +
LIBPPT_VERSION="$LIB_PPT_CURRENT:$LIB_PPT_REVISION:$LIB_PPT_AGE"
 +
AC_SUBST(LIBPPT_VERSION)
 +
 
 +
LIB_XML_CMD_CURRENT=5
 +
LIB_XML_CMD_AGE=4
 +
LIB_XML_CMD_REVISION=2
 +
AC_SUBST(LIB_XML_CMD_CURRENT)
 +
AC_SUBST(LIB_XML_CMD_AGE)
 +
AC_SUBST(LIB_XML_CMD_REVISION)
 +
LIBXMLCOMMAND_VERSION="$LIB_XML_CMD_CURRENT:$LIB_XML_CMD_REVISION:$LIB_XML_CMD_AGE"
 +
AC_SUBST(LIBXMLCOMMAND_VERSION)
 +
</source>
 +
 
 +
== Update the '''ChangeLog''' file. ==
 
Use the script <tt>gitlog-to-changelog</tt> (which can be found with Google) to update the '''ChangeLog''' file by running it using the <tt>--since="<date>"</tt> option with a date one day later in time than the newest entry in the current ChangeLog.  
 
Use the script <tt>gitlog-to-changelog</tt> (which can be found with Google) to update the '''ChangeLog''' file by running it using the <tt>--since="<date>"</tt> option with a date one day later in time than the newest entry in the current ChangeLog.  
 
: <tt style="font-size: 1.1em; font-weight: bold;">gitlog-to-changelog --since="1970-01-01"</tt>
 
: <tt style="font-size: 1.1em; font-weight: bold;">gitlog-to-changelog --since="1970-01-01"</tt>
Line 41: Line 60:
 
'''Tip''': ''When you're making the commit log entries, use line breaks so ChangeLog will be readable. That is, use lines < 80 characters long.''
 
'''Tip''': ''When you're making the commit log entries, use line breaks so ChangeLog will be readable. That is, use lines < 80 characters long.''
  
==== Update the NEWS file ====
+
== Update the '''NEWS''' file ==
To update the NEWS file, just read over the new ChangeLog entries and summarize.
+
To update the NEWS file, just read over the new ChangeLog entries and summarize.  
 +
 
 +
The new entries to the NEWS file will be used later when making the GitHub release and when writing the server's release page on www.opendap.org.
 +
 
 +
We might replace this:
 +
* It's also helpful to have, in the '''NEWS''' file and the Web site and the release notes, a list of the Jira tickets that have been closed since the last release. The best way to do this is to goto ''Jira's Issues'' page and look at the ''Tickets closed recently'' item. From there, click on ''Advanced'' and edit the time range so it matches the time range since the past release to now, then ''Export'' that info as an excel spreadsheet (the icon with a hat and a down arrow). YMMV regarding how easy this is and Jira's UI changes often.)
 +
 
 +
With instructions about making an associated release in JIRA using version tagging.
 +
 
 +
== Update the Version Numbers for Humans ==
 +
;Affected Files:
 +
: configure.ac
 +
: debian/changelog (see [https://www.debian.org/doc/manuals/maint-guide/dreq.en.html#changelog] Debian ChangeLog)
 +
: NEWS
 +
: README.md
 +
: INSTALL
  
==== Update the Version Numbers for Humans ====
 
 
# Determine the human version number. This appears to be a somewhat subjective process.
 
# Determine the human version number. This appears to be a somewhat subjective process.
 
# Edit each of the ''Affected Files'' and update the human version number.
 
# Edit each of the ''Affected Files'' and update the human version number.
 +
# In the '''README.md''' file be sure to update the description of how to locate the DOI for the release with the new version number.
 +
 +
== Update the libdap version ==
 +
Determine the libdap version associated with this release by checking the contents of the file <tt>libdap4-snapshot</tt> The <tt>libdap4-snapshot</tt> file should contain a single line like this example:
 +
<pre>
 +
libdap4-3.20.9-0 2021-12-28T19:23:45+0000
 +
</pre>
 +
 +
The libdap version for the above example is: <tt>libdap-3.20.9</tt> (The version is NOT <tt>libdap4-3.20.9</tt>)
 +
 +
=== Update the libdap version in the .travis.yml file ===
 +
;Affected Files
 +
: .travis.yml
 +
 +
In the .travis.yml file update the value of  ''LIBDAP_RPM_VERSION'' in the ''env: global:'' section so that it contains the complete numerical value of the libdap version you located in the previous step. Using the previous example the value would be:
 +
<pre>
 +
    - LIBDAP_RPM_VERSION=3.20.9-0
 +
</pre>
 +
 +
=== Update the libdap version in the RPM spec files ===
 +
;Affected Files
 +
: ''bes.spec*.in''
 +
Update the <tt>bes.spec*.in</tt> files by changing the <tt>Requires</tt> and <tt>BuildRequires</tt> entries for libdap. Based on our example the result would be:
  
:;Affected Files:
+
<pre>
:: configure.ac
+
Requires:       libdap >= 3.20.9
:: *.spec (In the BES it's ''bes.spec.*'')
+
BuildRequires: libdap-devel >= 3.20.9
:: debian/changelog (see [https://www.debian.org/doc/manuals/maint-guide/dreq.en.html#changelog] Debian ChangeLog)
+
</pre>
:: .travis.yml (for BES only; edit the ''LIBDAP_RPM_VERSION'' in the ''env: global:'' section)
 
:: NEWS
 
:: README.md (Add the libdap version the README.md)
 
:: INSTALL
 
  
It's helpful to have, in the '''NEWS''' file and the Web site and the release notes, a list of the Jira tickets that have been closed since the last release. The best way to do this is to goto ''Jira's Issues'' page and look at the ''Tickets closed recently'' item. From there, click on ''Advanced'' and edit the time range so it matches the time range since the past release to now, then ''Export'' that info as an excel spreadsheet (the icon with a hat and a down arrow). YMMV regarding how easy this is and Jira's UI changes often.
+
(''These lines may not be adjacent to each other in the spec files'')
  
==== Update the RPM dependencies ====
+
=== Update the libdap version in the README.md file ===
In the RPM ''.spec'' file, update the dependencies as needed.
+
;Affected Files
 +
: README.md
 +
# [https://zenodo.org Get the DOI markdown from Zenodo] by using the search bar and searching for the libdap version string that you determined at the beginning of this section.
 +
# Update the '''README.md''' file with libdap version and the associated DOI link (using the markdown you got from Zenodo).
  
 +
; Note
 +
: You will also need this DOI markdown when making the GitHub release page for the BES.
 +
 +
See the section on this page titled "''Get the BES DOI from Zenodo''"  for more details about getting the DOI markdown.
 +
 +
== Update the RPM dependencies ==
 
;Affected Files:  
 
;Affected Files:  
: *.spec (In the BES it's ''bes.spec.*''')
+
:''bes.spec*.in''
  
==== Update the internal library version numbers ====
+
In the RPM ''.spec'' file, update the dependencies as needed.  
There are really 2 version numbers for each of these project items. The ''human'' version (like bes-3.17.5) and the ''library'' API/ABI version which is represented as <tt>CURRENT:REVISION:AGE</tt>. There are special rules for when each of the numbers in the library API/ABI version get incremented that are triggered by the kinds of changes that where made to the code base. The human version number is more arbitrary. So for example, we might make a major API/ABI change and have to change to a new Libtool version like <tt>25:0:0</tt> but the human version might only change from bes-3.17.3 to bes-3.18.0
+
* The libdap version dependency was covered in a previous step.
 +
* Be attentive to changes that have been made to the hyrax-dependencies since the last release.
  
The rules for shared image version numbers:
+
== Update the module version numbers for humans ==
# No interfaces changed, only implementations (good): Increment REVISION.
+
In bes/modules/common, check that the file all-modules.txt is complete and update as needed. Then run:
# Interfaces added, none removed (good): Increment CURRENT, increment AGE, set REVISION to 0.
 
# Interfaces removed or changed (BAD, breaks upward compatibility): Increment CURRENT, set AGE and REVISION to 0.
 
  
See ''How to see the scope of API/ABI changes in C++ sources'' below for gruesome details. Often basic knowledge of the edits is good enough.
+
for d in `cat all_modules.txt`
 +
do
 +
  ./version_update_modules.sh -v $d
 +
done
  
;Affected Files:
+
This will update the patch number (x.y.patch) for each of the named modules.
: configure.ac
+
 
 +
If a particular module has significant fixes, hand edit the number, in the Makefile.am.
 +
 
 +
See below for special info about the HDF4/5 modules (which also applies to any modules not in the BES GitHub repo).
  
==== For the BES HDF4/5 modules (BES only) ====
+
== For the BES HDF4/5 modules (BES only) ==
 +
# ''Make sure that you are working on the master branch of each module!!''
 
# Goto those directories and update the ChangeLog, NEWS, README, and INSTALL files (even though INSTALL is not used by many).
 
# Goto those directories and update the ChangeLog, NEWS, README, and INSTALL files (even though INSTALL is not used by many).
 
# Update the module version numbers in their respective Makefile.am files.
 
# Update the module version numbers in their respective Makefile.am files.
 
# Commit and Push these changes.
 
# Commit and Push these changes.
  
=== Commit Changes ===
+
== Update the Build Offset ==
 +
''Setting the build offset correctly will set the build number for the new release to "0".''
 +
 
 +
In the file <tt>travis/travis_bes_build_offset.sh</tt> set the value of <tt>BES_TRAVIS_BUILD_OFFSET</tt> to the number of the last TravisCI build plus one. The previous commit and push will have triggered a TravisCI build. Find the build number for the previous commit in [https://app.travis-ci.com/github/OPENDAP/bes the TravisCI page for the BES] and use that build number plus 1.
 +
 
 +
== Commit Changes ==
 +
''Be sure that you have completed all of the changes to the various ChangeLog, NEWS, INSTALL, configure.ac,  <tt>travis/travis_bes_build_offset.sh</tt>, and other files before proceeding!''
 +
 
 
# Commit and push the BES code. Wait for the CI/CD builds to complete. You must be working on the ''master'' branch to get the CD package builds to work.
 
# Commit and push the BES code. Wait for the CI/CD builds to complete. You must be working on the ''master'' branch to get the CD package builds to work.
  
=== Tag & Release ===
+
== Tag the BES code ==
==== Tag the BES code ====
 
 
# Tag the bes code using command line git in your local (up-to-date) '''bes''' project
 
# Tag the bes code using command line git in your local (up-to-date) '''bes''' project
#* <tt style="font-size: 1.1em; font-weight: bold;">git tag -a version-<numbers> -m "Version <number>"</tt>
+
#* <tt style="font-size: 1.1em; font-weight: bold;">git tag -m "Version <number>" -a <numbers> </tt>
#* <tt style="font-size: 1.1em; font-weight: bold;">git push origin version-<numbers></tt>
+
#* <tt style="font-size: 1.1em; font-weight: bold;">git push origin <numbers></tt>
 
#: <br/>
 
#: <br/>
 
# If this is part of a Hyrax Release, then tag this point in the master branch with the Hyrax release number
 
# If this is part of a Hyrax Release, then tag this point in the master branch with the Hyrax release number
#* <tt style="font-size: 1.1em; font-weight: bold;">git tag -a hyrax-<numbers> -m "Hyrax <number>"</tt>
+
#* <tt style="font-size: 1.1em; font-weight: bold;">git tag -m "Hyrax <number>" -a hyrax-<numbers></tt>
 
#* <tt style="font-size: 1.1em; font-weight: bold;">git push origin hyrax-<numbers></tt>
 
#* <tt style="font-size: 1.1em; font-weight: bold;">git push origin hyrax-<numbers></tt>
 
#: '''NB:''' ''Instead of tagging the HDF4/5 modules, use the saved commit hashes that git tracks for submodules. This cuts down on the bookkeeping for releases and removes one source of error.''
 
#: '''NB:''' ''Instead of tagging the HDF4/5 modules, use the saved commit hashes that git tracks for submodules. This cuts down on the bookkeeping for releases and removes one source of error.''
  
==== Create the release on Github ====
+
== Create the BES release on Github ==
 
# [https://github.com/OPENDAP/bes Goto the BES project page in GitHub]
 
# [https://github.com/OPENDAP/bes Goto the BES project page in GitHub]
 
# Choose the '''releases''' tab.
 
# Choose the '''releases''' tab.
Line 108: Line 181:
 
#** If you have previously edited the release page you can click '''Update this release'''
 
#** If you have previously edited the release page you can click '''Update this release'''
  
=== Publish and Sign ===
+
== Publish and Sign ==
  
 
When the release is made on GitHub the source tar bundle is made automatically. However, this bundle is '''not''' the one we wish to publish because it requires people to have ''autoconf'' installed. Rather we want to use the result of "<tt>make dist</tt>" which will have the <tt>configure</tt> script pre-generated.
 
When the release is made on GitHub the source tar bundle is made automatically. However, this bundle is '''not''' the one we wish to publish because it requires people to have ''autoconf'' installed. Rather we want to use the result of "<tt>make dist</tt>" which will have the <tt>configure</tt> script pre-generated.
Line 114: Line 187:
 
All you need do is build the tar file using <tt>make list</tt>, sign it, and push (or pull) these files onto www.opendap.org/pub/source.  
 
All you need do is build the tar file using <tt>make list</tt>, sign it, and push (or pull) these files onto www.opendap.org/pub/source.  
  
# Go to the '''bes''' project on your local machine and run <tt>make dist</tt> which will make a bes-x.y.z,tar.gz file at the top level of the '''bes''' project.
+
# Go to the '''bes''' project on your local machine and run ''<tt>make dist</tt>'' which will make a bes-x.y.z,tar.gz file at the top level of the '''bes''' project.
 
# Use '''gpg''' to sign the tar bundle:
 
# Use '''gpg''' to sign the tar bundle:
 
#: <tt>gpg --detach-sign --local-user security@opendap.org bes-x.y.z.tgz</tt>
 
#: <tt>gpg --detach-sign --local-user security@opendap.org bes-x.y.z.tgz</tt>
Line 129: Line 202:
 
##: <tt> gpg --verify bes-x.y.z.tgz.sig bes-x.y.z.tgz</tt>
 
##: <tt> gpg --verify bes-x.y.z.tgz.sig bes-x.y.z.tgz</tt>
  
=== Get the DOI from Zenodo ===
+
== Get the BES DOI from Zenodo ==
 +
Get the Zenodo DOI for the newly created BES release and add it to the associated GitHub BES release page.
 +
 
 
# [https://zenodo.org Goto Zenodo]  
 
# [https://zenodo.org Goto Zenodo]  
 
# Look at the 'upload' page. If there is nothing there (perhaps because you are not ''jhrg'' or whoever set up the connection between the BES project and Zenodo) you can use the search bar to search for '''bes'''.  
 
# Look at the 'upload' page. If there is nothing there (perhaps because you are not ''jhrg'' or whoever set up the connection between the BES project and Zenodo) you can use the search bar to search for '''bes'''.  
 
#: Since the libdap, BES and OLFS repositories are linked to Zenodo, the newly-tagged code is uploaded to Zenodo automatically and a DOI is minted for us.
 
#: Since the libdap, BES and OLFS repositories are linked to Zenodo, the newly-tagged code is uploaded to Zenodo automatically and a DOI is minted for us.
 
# Click on the new version, then click on the DOI tag in the pane on the right of the page for the given release.
 
# Click on the new version, then click on the DOI tag in the pane on the right of the page for the given release.
# Copy the DOI as markdown from the window that pops up and paste that into the info for the version back in Github land.
+
# Copy the DOI as markdown from the window that pops up.
# Also paste that into the README file. Commit using ''[skip ci]'' so we don't do a huge build (or do the build, it really doesn't matter that much).
+
# Edit the GitHub release page for the BES release you just created and paste the DOI markdown into the top of the description.
  
 
'''Tip:''' ''If you are trying to locate the '''libdap''' releases in Zenodo you have to search for the string:'' <tt style="font-size: 1.1em; font-weight: bold;">libdap4</tt>
 
'''Tip:''' ''If you are trying to locate the '''libdap''' releases in Zenodo you have to search for the string:'' <tt style="font-size: 1.1em; font-weight: bold;">libdap4</tt>
  
===== Images =====
+
=== Images ===
 
[[File:Screenshot 2018-12-06 11.06.44.png|none|thumb|400px|border|left|Zenodo upload page]]
 
[[File:Screenshot 2018-12-06 11.06.44.png|none|thumb|400px|border|left|Zenodo upload page]]

Latest revision as of 16:14, 3 January 2022

This pages covers the steps required to release the BES software for Hyrax.

We now depend on the CI/CD process to build binary packages and to test the source builds.

Tip: If, while working on the release, you find you need to make changes to the code and you know the CI build will fail, do so on a release branch that you can merge and discard later. Do not make a release branch if you don't need it, since it complicates making tags.

1 Verify the code base

  1. We release using the master branch. The code on master must have passed the CI builds. This includes the hyrax-docker builds since that CI build runs the full server regression tests!
  2. Make sure that the source code you're using for the following steps is up-to-date. (git pull)

2 Update the internal library (API/ABI) version numbers.

The BES is not a shared library, it is a set of c++ applications that are typically built as statically linked binaries. Because of this the usual CURRENT:REVISION:AGE tuples used to express the binary compatibility state of a c++ shared object library have little meaning for the BES code. So, what we choose to do is simply bump the REVISION numbers by one value for each release.

  • In the configure.ac file locate each of:
    • LIB_DIS_REVISION
    • LIB_PPT_REVISION
    • LIB_XML_CMD_REVISION
  • Increase the value of each by one (1).
  • Save the file.
  • Update the text documentation files and version numbers in the configuration files:

Example of the relevant section from configure.ac:

LIB_DIS_CURRENT=18
LIB_DIS_AGE=3
LIB_DIS_REVISION=3
AC_SUBST(LIB_DIS_CURRENT)
AC_SUBST(LIB_DIS_AGE)
AC_SUBST(LIB_DIS_REVISION)
LIBDISPATCH_VERSION="$LIB_DIS_CURRENT:$LIB_DIS_REVISION:$LIB_DIS_AGE"
AC_SUBST(LIBDISPATCH_VERSION)

LIB_PPT_CURRENT=5
LIB_PPT_AGE=1
LIB_PPT_REVISION=2
AC_SUBST(LIB_PPT_CURRENT)
AC_SUBST(LIB_PPT_AGE)
AC_SUBST(LIB_PPT_REVISION)
LIBPPT_VERSION="$LIB_PPT_CURRENT:$LIB_PPT_REVISION:$LIB_PPT_AGE"
AC_SUBST(LIBPPT_VERSION)

LIB_XML_CMD_CURRENT=5
LIB_XML_CMD_AGE=4
LIB_XML_CMD_REVISION=2
AC_SUBST(LIB_XML_CMD_CURRENT)
AC_SUBST(LIB_XML_CMD_AGE)
AC_SUBST(LIB_XML_CMD_REVISION)
LIBXMLCOMMAND_VERSION="$LIB_XML_CMD_CURRENT:$LIB_XML_CMD_REVISION:$LIB_XML_CMD_AGE"
AC_SUBST(LIBXMLCOMMAND_VERSION)

3 Update the ChangeLog file.

Use the script gitlog-to-changelog (which can be found with Google) to update the ChangeLog file by running it using the --since="<date>" option with a date one day later in time than the newest entry in the current ChangeLog.

gitlog-to-changelog --since="1970-01-01"
(Specify a date one day later than the one at the top of the existing ChangeLog file.)

Save the result to a temp file and combine the two files:

cat tmp ChangeLog > ChangeLog.tmp; mv ChangeLog.tmp ChangeLog

If you're making the first ChangeLog entries, then you'll need to create the ChangeLog file first.
Tip: When you're making the commit log entries, use line breaks so ChangeLog will be readable. That is, use lines < 80 characters long.

4 Update the NEWS file

To update the NEWS file, just read over the new ChangeLog entries and summarize.

The new entries to the NEWS file will be used later when making the GitHub release and when writing the server's release page on www.opendap.org.

We might replace this:

  • It's also helpful to have, in the NEWS file and the Web site and the release notes, a list of the Jira tickets that have been closed since the last release. The best way to do this is to goto Jira's Issues page and look at the Tickets closed recently item. From there, click on Advanced and edit the time range so it matches the time range since the past release to now, then Export that info as an excel spreadsheet (the icon with a hat and a down arrow). YMMV regarding how easy this is and Jira's UI changes often.)

With instructions about making an associated release in JIRA using version tagging.

5 Update the Version Numbers for Humans

Affected Files
configure.ac
debian/changelog (see [1] Debian ChangeLog)
NEWS
README.md
INSTALL
  1. Determine the human version number. This appears to be a somewhat subjective process.
  2. Edit each of the Affected Files and update the human version number.
  3. In the README.md file be sure to update the description of how to locate the DOI for the release with the new version number.

6 Update the libdap version

Determine the libdap version associated with this release by checking the contents of the file libdap4-snapshot The libdap4-snapshot file should contain a single line like this example:

libdap4-3.20.9-0 2021-12-28T19:23:45+0000

The libdap version for the above example is: libdap-3.20.9 (The version is NOT libdap4-3.20.9)

6.1 Update the libdap version in the .travis.yml file

Affected Files
.travis.yml

In the .travis.yml file update the value of LIBDAP_RPM_VERSION in the env: global: section so that it contains the complete numerical value of the libdap version you located in the previous step. Using the previous example the value would be:

    - LIBDAP_RPM_VERSION=3.20.9-0

6.2 Update the libdap version in the RPM spec files

Affected Files
bes.spec*.in

Update the bes.spec*.in files by changing the Requires and BuildRequires entries for libdap. Based on our example the result would be:

Requires:       libdap >= 3.20.9
BuildRequires:  libdap-devel >= 3.20.9

(These lines may not be adjacent to each other in the spec files)

6.3 Update the libdap version in the README.md file

Affected Files
README.md
  1. Get the DOI markdown from Zenodo by using the search bar and searching for the libdap version string that you determined at the beginning of this section.
  2. Update the README.md file with libdap version and the associated DOI link (using the markdown you got from Zenodo).
Note
You will also need this DOI markdown when making the GitHub release page for the BES.

See the section on this page titled "Get the BES DOI from Zenodo" for more details about getting the DOI markdown.

7 Update the RPM dependencies

Affected Files
bes.spec*.in

In the RPM .spec file, update the dependencies as needed.

  • The libdap version dependency was covered in a previous step.
  • Be attentive to changes that have been made to the hyrax-dependencies since the last release.

8 Update the module version numbers for humans

In bes/modules/common, check that the file all-modules.txt is complete and update as needed. Then run:

for d in `cat all_modules.txt`
do
  ./version_update_modules.sh -v $d
done

This will update the patch number (x.y.patch) for each of the named modules.

If a particular module has significant fixes, hand edit the number, in the Makefile.am.

See below for special info about the HDF4/5 modules (which also applies to any modules not in the BES GitHub repo).

9 For the BES HDF4/5 modules (BES only)

  1. Make sure that you are working on the master branch of each module!!
  2. Goto those directories and update the ChangeLog, NEWS, README, and INSTALL files (even though INSTALL is not used by many).
  3. Update the module version numbers in their respective Makefile.am files.
  4. Commit and Push these changes.

10 Update the Build Offset

Setting the build offset correctly will set the build number for the new release to "0".

In the file travis/travis_bes_build_offset.sh set the value of BES_TRAVIS_BUILD_OFFSET to the number of the last TravisCI build plus one. The previous commit and push will have triggered a TravisCI build. Find the build number for the previous commit in the TravisCI page for the BES and use that build number plus 1.

11 Commit Changes

Be sure that you have completed all of the changes to the various ChangeLog, NEWS, INSTALL, configure.ac, travis/travis_bes_build_offset.sh, and other files before proceeding!

  1. Commit and push the BES code. Wait for the CI/CD builds to complete. You must be working on the master branch to get the CD package builds to work.

12 Tag the BES code

  1. Tag the bes code using command line git in your local (up-to-date) bes project
    • git tag -m "Version <number>" -a <numbers>
    • git push origin <numbers>

  2. If this is part of a Hyrax Release, then tag this point in the master branch with the Hyrax release number
    • git tag -m "Hyrax <number>" -a hyrax-<numbers>
    • git push origin hyrax-<numbers>
    NB: Instead of tagging the HDF4/5 modules, use the saved commit hashes that git tracks for submodules. This cuts down on the bookkeeping for releases and removes one source of error.

13 Create the BES release on Github

  1. Goto the BES project page in GitHub
  2. Choose the releases tab.
  3. On the Releases page click the 'Tags' tab.
  4. On the Tags page, locate the tag (created above) associated with this new release.
  5. Click the ellipses (...) located on the far right side of the version-x.y.z tag 'frame' for this release and and choose Create release.
    • Enter a title for the release
    • Copy the most recent text from the NEWS file into the describe field
    • Click Publish release or Save draft.
      • If you have previously edited the release page you can click Update this release

14 Publish and Sign

When the release is made on GitHub the source tar bundle is made automatically. However, this bundle is not the one we wish to publish because it requires people to have autoconf installed. Rather we want to use the result of "make dist" which will have the configure script pre-generated.

All you need do is build the tar file using make list, sign it, and push (or pull) these files onto www.opendap.org/pub/source.

  1. Go to the bes project on your local machine and run make dist which will make a bes-x.y.z,tar.gz file at the top level of the bes project.
  2. Use gpg to sign the tar bundle:
    gpg --detach-sign --local-user security@opendap.org bes-x.y.z.tgz
  3. Use sftp to push the signature file and the tar bundle to the /httpdocs/pub/source directory on www.opendap.org
    (Assuming your current working directory is the top of the bes project)
    sftp opendap@www.opendap.org
    cd httpdocs/pub/source
    put bes-x.y.z.tgz.sig
    put bes-x.y.z.tgz
    quit
  4. Check your work!
    1. Download the source tar bundle and signature from www.opendap.org.
    2. Verify the signature:
      gpg --verify bes-x.y.z.tgz.sig bes-x.y.z.tgz

15 Get the BES DOI from Zenodo

Get the Zenodo DOI for the newly created BES release and add it to the associated GitHub BES release page.

  1. Goto Zenodo
  2. Look at the 'upload' page. If there is nothing there (perhaps because you are not jhrg or whoever set up the connection between the BES project and Zenodo) you can use the search bar to search for bes.
    Since the libdap, BES and OLFS repositories are linked to Zenodo, the newly-tagged code is uploaded to Zenodo automatically and a DOI is minted for us.
  3. Click on the new version, then click on the DOI tag in the pane on the right of the page for the given release.
  4. Copy the DOI as markdown from the window that pops up.
  5. Edit the GitHub release page for the BES release you just created and paste the DOI markdown into the top of the description.

Tip: If you are trying to locate the libdap releases in Zenodo you have to search for the string: libdap4

15.1 Images

Zenodo upload page