How to Make a Release - Revision history

Jimg: /* Send out a notice. */

2022-07-29T17:08:46Z

Send out a notice.

← Older revision		Revision as of 17:08, 29 July 2022
Line 55:		Line 55:
	== [[Update The Hyrax Release Web Page]] ==		== [[Update The Hyrax Release Web Page]] ==
	== Send out a notice. ==		== Send out a notice. ==
	Here's a sample email message. I sent this to opendap-tech@opendap.org		Here's a sample email message. I sent this to: "OPeNDAP Inc." <opendap-tech@opendap.org>, opendap-announce@opendap.org, opendap@opendap.org

	NB: ~~Should probably acknowledge any financial support in such an email (NSF w/grant number, NASA/Raytheon)~~		Subject: We are pleased to announce the release of Hyrax 1.16.8

	<pre>		<pre>
	Greetings!		Greetings!

	OPeNDAP is pleased to announce the release of Hyrax 1.16.8. This version of the DAP2 and DAP4 data server is available as RedHat 8 and CentOS 7 RPM packages, Docker containers and source code via GitHub. See https://www.opendap.org/software/hyrax/1.16#SoftwareDownloads for the details.		OPeNDAP is pleased to announce the release of Hyrax 1.16.8. This version of the DAP2 and DAP4 data server is available as RedHat 8 and CentOS 7 RPM packages, Docker containers and source code via GitHub. See https://www.opendap.org/software/hyrax/1.16#SoftwareDownloads for the details.

	Hyrax is Open Source.		Hyrax is Open Source.
Line 68:		Line 68:
	Below are the changes/updates for this version of the server.		Below are the changes/updates for this version of the server.

			DMR++ Improvements - Direct subsetting access to data in S3
	DMR++ Improvements

	• Various improvements for supporting FillValue in dmr++ lifecycle.		• Various improvements for supporting FillValue in dmr++ lifecycle.
Line 79:		Line 78:
	bes		bes

	• Support for RHEL8		• Support for RHEL8
	• Improved the error messages returned to the client		• Improved the error messages returned to the client
	• Refactored get_dmrpp, application. Some test features are still broken but core functionality is working now.		• Refactored get_dmrpp, application. Some test features are still broken but core functionality is working now.
	• Improved support for more GES DISC level 3 and level 4 products		• Improved support for more GES DISC level 3 and level 4 products
	• Added coverage the support for the AIRS level 3 and GLDAS level products.		• Added coverage the support for the AIRS level 3 and GLDAS level products.
	• Patched bug in HDF5Array.cc introduced by the std::vector refactor		• Patched bug in HDF5Array.cc introduced by the std::vector refactor
	• Added time.h header to ppt/SocketUtilities.cc		• Added time.h header to ppt/SocketUtilities.cc
	• Modified fileout_netcdf handler to allow netcdf-3 responses to be up to 4GB in size.		• Modified fileout_netcdf handler to allow netcdf-3 responses to be up to 4GB in size.
	This behavior can be reverted by setting FONc.NC3ClassicFormat=true in the BES configuration		This behavior can be reverted by setting FONc.NC3ClassicFormat=true in the BES configuration
	(aka /etc/bes/site.conf file)		(aka /etc/bes/site.conf file)
	olfs		olfs
Line 101:		Line 100:
	The Hyrax development team: Nathan Potter, Dan Holloway, Sam Lloyd, Kodi Neumiller, Kent Yang and James Gallagher		The Hyrax development team: Nathan Potter, Dan Holloway, Sam Lloyd, Kodi Neumiller, Kent Yang and James Gallagher

			Acknowledgement: OPeNDAP thanks NASA and Raytheon for continued support of the Hyrax Data Server.
	—		—
	James Gallagher		James Gallagher
	jgallagher@opendap.org		jgallagher@opendap.org

	</pre>		</pre>

Jimg: /* Send out a notice. */

2022-07-29T16:57:34Z

Send out a notice.

← Older revision		Revision as of 16:57, 29 July 2022
Line 56:		Line 56:
	== Send out a notice. ==		== Send out a notice. ==
	Here's a sample email message. I sent this to opendap-tech@opendap.org		Here's a sample email message. I sent this to opendap-tech@opendap.org

			NB: Should probably acknowledge any financial support in such an email (NSF w/grant number, NASA/Raytheon)

	<pre>		<pre>

Jimg: /* Send out a notice. */

2022-07-29T16:56:11Z

Send out a notice.

@@ Line 55: / Line 55: @@
 == [[Update The Hyrax Release Web Page]] ==
 == Send out a notice. ==
 == Time to complete by release ==

Ndp at 15:24, 10 January 2022

2022-01-10T15:24:30Z

← Older revision		Revision as of 15:24, 10 January 2022
Line 1:		Line 1:
	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.		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.

	# 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.		# Look for any tickets that have been bound to the label 'fix release x.y.z' and make sure those are completed. Be sure to use both:
			#* The HyraxKB Kanban board in OPeNDAP's JIRA.
			#* The Hyrax board in our NASA JIRA.
	# When we are ready to release, follow the process outlined in the sections below.		# When we are ready to release, follow the process outlined in the sections below.
	# Once done, close the board		# Once done, close the board

Ndp: /* Signing And Publishing C++ Binary Distributions */

2022-01-09T22:58:32Z

Signing And Publishing C++ Binary Distributions

← Older revision		Revision as of 22:58, 9 January 2022
Line 45:		Line 45:

	=== [[Signing And Publishing C++ Binary Distributions]] ===		=== [[Signing And Publishing C++ Binary Distributions]] ===
	Note: This was already done for the java OLFS in the previous steps.		: '''Note:''' ''This was already done for the java OLFS in the previous steps.''

	=== [[HyraxDockerReleaseGuide \| Build And Publish Docker Images For The Release]] ===		=== [[HyraxDockerReleaseGuide \| Build And Publish Docker Images For The Release]] ===

Ndp: /* Sign And Publish The C++ Binary Distributions */

2022-01-09T22:58:03Z

Sign And Publish The C++ Binary Distributions

@@ Line 45: / Line 45: @@
 === [[Signing And Publishing C++ Binary Distributions]] ===
 Note: This was already done for the java OLFS in the previous steps.
 === [[HyraxDockerReleaseGuide | Build And Publish Docker Images For The Release]] ===

Ndp: /* Sign And Publish The C++ Binary Distributions */

2022-01-09T22:55:15Z

Sign And Publish The C++ Binary Distributions

← Older revision		Revision as of 22:55, 9 January 2022
Line 44:		Line 44:
	=== OLFS: [[OLFSReleaseGuide \| Source and Binary release for OLFS]] ===		=== OLFS: [[OLFSReleaseGuide \| Source and Binary release for OLFS]] ===

			=== [[Signing And Publishing C++ Binary Distributions]] ===
	=== Sign And Publish The C++ Binary Distributions ===		=== Sign And Publish The C++ Binary Distributions ===
	Note: This was already done for the java OLFS in the previous steps.		Note: This was already done for the java OLFS in the previous steps.

Ndp: /* Update The Hyrax Release Web Page On The OPeNDAP Website */

2022-01-09T18:17:27Z

Update The Hyrax Release Web Page On The OPeNDAP Website

← Older revision		Revision as of 18:17, 9 January 2022
Line 77:		Line 77:

	== [[Update The Hyrax Release Web Page]] ==		== [[Update The Hyrax Release Web Page]] ==
	~~== Update The Hyrax Release Web Page On The OPeNDAP Website ==~~
	Currently we have a single page for each major release. Minor release information is added to the major release page to which the minor release is associated. For example if you are making minor release Hyrax-1.16.5 then you would add the release information to the Hyrax-1.16 page.

	~~=== Creating A Major Release Page ===~~
	~~# If this is a major release copy the previous major release X.Y page to X.(Y+1).~~
	~~# Clear out the contents of the page while maintaining the structure:~~
	~~#* Release Information~~
	~~#** New Features (''Remove content.'')~~
	~~#** Bug Fixes (''Remove content.'')~~
	~~#* Hyrax Software Downloads (''Keep contents but update as described in the Minor Release section below.'')~~
	~~#** Required External Dependencies (''Ibid'')~~
	~~#** Binary Packages (''Ibid'')~~
	~~#*** Installation Summary (''Ibid'')~~
	~~#** Source Code (''Ibid'')~~
	~~#** GitHub (''Ibid'')~~
	~~#** Snapshots (''Ibid'')~~
	~~#* Hyrax Server Documentation (''Ibid'')~~
	~~# Follow the instructions for updating the web page for a Minor Release below.~~

	~~=== Updating The Release Page For A Minor Release ===~~

	~~==== Update the New Features section ====~~

	~~# Under "New Features" create a new sub-section (Heading 2) titled "Added in Hyrax-xx.yy.zz" section for the new release. If this is a major release then zz==0, example: Hyrax-1.16.0~~
	~~# Create an Anchor at the beginning of this new heading titled "''hyrax-.xx.yy.zz-features''".~~
	# In the abbreviated table of contents at the top of the page add a new link in the bullet list under "New Features" titled "hyrax-xx.yy.zz" and point the link to your new anchor "#hyrax-xx.yy.zz-features"
	~~# Take the entires that you made to the change log and enter them into this new section, format them for readability and navigability. (See previous releases for examples.)~~



	~~==== Update the Bugs/Issues Addressed section ====~~

	~~==== Update the Hyrax Software Downloads section ====~~
	~~# Update the links on the web page made/copies/edited above. Test each link - source and binary. Once all of those work...~~

	~~==== Publish the release page ====~~

	~~# Publish the release page. Check the links - there are links in two menus that have to be set manually.~~

	== Send out a notice. ==		== Send out a notice. ==

Ndp: /* Update The Hyrax Release Web Page On The OPeNDAP Website */

2022-01-09T18:15:38Z

Update The Hyrax Release Web Page On The OPeNDAP Website

← Older revision		Revision as of 18:15, 9 January 2022
Line 76:		Line 76:
	=== Install the new server on test.opendap.org ===		=== Install the new server on test.opendap.org ===

			== [[Update The Hyrax Release Web Page]] ==
	== Update The Hyrax Release Web Page On The OPeNDAP Website ==		== Update The Hyrax Release Web Page On The OPeNDAP Website ==
	Currently we have a single page for each major release. Minor release information is added to the major release page to which the minor release is associated. For example if you are making minor release Hyrax-1.16.5 then you would add the release information to the Hyrax-1.16 page.		Currently we have a single page for each major release. Minor release information is added to the major release page to which the minor release is associated. For example if you are making minor release Hyrax-1.16.5 then you would add the release information to the Hyrax-1.16 page.

Ndp: /* Update the New Features section */

2022-01-09T15:11:13Z

Update the New Features section

← Older revision		Revision as of 15:11, 9 January 2022
Line 106:		Line 106:


	==== Update the ~~New Features~~ section ====		==== Update the Bugs/Issues Addressed section ====

	==== Update the Hyrax Software Downloads section ====		==== Update the Hyrax Software Downloads section ====
	# Update the links on the web page made/copies/edited above. Test each link - source and binary. Once all of those work...		# Update the links on the web page made/copies/edited above. Test each link - source and binary. Once all of those work...