Difference between revisions of "How to Make a Release"

From OPeNDAP Documentation
(Source release for hyrax-dependencies)
(Source release for hyrax-dependencies)
Line 34: Line 34:
 
=== Source release for hyrax-dependencies ===
 
=== Source release for hyrax-dependencies ===
 
; Note
 
; Note
: ''When you commit the various changes made for the source releases, that will trigger a binary build and those binaries will have the version numbers that making the source dists update.''
+
: ''Committing and pushing the various changes made for the source releases will trigger a binary build and those binaries will have the version numbers that making the source distributions update.''
 
# Make sure the hyrax-dependencies project is up to date and tar balls on www.o.o. If there have been changes/updates:
 
# Make sure the hyrax-dependencies project is up to date and tar balls on www.o.o. If there have been changes/updates:
 
# Update version number for the hyrax-dependencies in the Makefile
 
# Update version number for the hyrax-dependencies in the Makefile

Revision as of 14:44, 7 January 2022

1 When we decide to release software

Use the developers at opendap.org list to send out notices to all the developers about pending releases.

1.1 Planned release

If this is a planned release, send out a notice at least two weeks in advance to anyone who likely has made changes to the software. More lead time is, of course, better. This will allow developers time to get their code and documentation changes into github and onto the master branch in time for the release.

Run Coverity!

1.2 Emergency releases

If this is an 'emergency' release, then send out a notice to developers as soon as the decision to release is made, since this will give a chance for other developers to lets us know if there are new changes in the master branch that are ready for release. if we don't get an email from those developers of a particular component, then we should assume that the code might not be 100% ready for release and we should use the version tagged with/for the last release if possible.

Maybe run Coverity - depends on the scope of the changes.

2 Overview

This is an updated set of notes regarding a software release. It is tailored to a release of Hyrax, but the same process can be used for any of our code.

  1. Look for any tickets that have been bound to the label 'fix release x.y.z' and make sure those are completed. Use the Kanban board.
  2. When we are ready to release, follow the process outlined in the section below.
  3. Once done, close the board

3 Release Prerequisites

Only start this process when hyrax-dependencies, libdap, bes and OLFS master branches all building and passing their tests.

4 Steps For A Major Release (ex: 1.16.x -> 1.17.0)

  1. Security Review for libdap, BES and OLFS Now Handled By TravisCI
  2. Write a new X.Y web page. See the web site admin notes for info about this. It has important information about the menu links. Base this on the previous release page's structure/content.
  3. Follow the remaining steps for a minor release (below).

5 Steps For A Minor Release (ex: 1.16.5 -> 1.16.6)

5.1 Perform the Jira Release Process

5.2 Update the release page on website

but don't publish it. For this, copy the X.Y page and make it X.Y.n. In the future, we might use only a single page for release X.Y and simply amend it with information for version .1, .2, and so on. Don't bother to edit the links, just get the text in place.

5.3 Source release for hyrax-dependencies

Note
Committing and pushing the various changes made for the source releases will trigger a binary build and those binaries will have the version numbers that making the source distributions update.
  1. Make sure the hyrax-dependencies project is up to date and tar balls on www.o.o. If there have been changes/updates:
  2. Update version number for the hyrax-dependencies in the Makefile
  3. Save, commit, and push the changes to master branch.
  4. Once the hyrax-dependencies CI build is finished, trigger builds CI in both libdap4 and bes by pushing change(s) to the master branch of each.
  5. Tag, and push the tag. Make 'release' in github using the same basic process as for libdap and the bes

5.4 libdap: Source Release for libdap

In order to get the DOIs for libdap and BES into the OLFS README.md, you will need to make those before the OLFS source dist.

5.5 BES: Source Release for BES

5.6 OLFS: Make the OLFS release Source and Binary release files

Follow these steps to create the three .jar files needed for the OLFS release.

5.7 Upload the source distributions

Make and upload the source distributions for hyrax-dependencies, libdap, BES and, OLFS - delay signing until later. 


5.8 Install the new server on test.opendap.org

  1. For the C++ software, Transfer the binary packages built using the CI/CD process. Log into the www.opendap.org web site host using ssh and the opendap account, and then use curl -O ... or wget --no-check-certificate ... to transfer the RPMs and Debian packages from our opendap.travis.build S3 bucket. The S3 bucket can be found at: https://s3.amazonaws.com/opendap.travis.build/index.html
  2. Update the links on the web page made/copies/edited above. Test each link - source and binary. Once all of those work...
  3. Sign the packages (source and binary). Do this by downloading the packages, signing and then uploading the .sig files - no need to upload the actual packages. See Secure Email for a hack to batch sign packages.
  4. Follow the instructions in Hyrax Docker Release Guide to create the docker images on docker-hub.
  5. Publish the release page. Check the links - there are links in two menus that have to be set manually.
  6. Send out a notice.
  7. Update and of the release checklists and the 'Time to complete...' information below.

5.9 Time to complete by release

  • Hyrax 1.12.2: The total time was planned as 3w 1d 5h and turned out as 1w 2d 2h 10m.
  • Hyrax 1.15.1: 3d calendar time
  • Hyrax 1.16.2: 3d effort