Tagged v2.6.1 . (12540a01) · Commits · CAMS / CSO

doc/source/conf.py

+1 −1

Original line number	Diff line number	Diff line
		@@ -22,7 +22,7 @@ copyright = '2020-2023, Arjo Segers'
		author = 'Arjo Segers'

		# The full version, including alpha/beta/rc tags
		release = 'v2.6'
		release = 'v2.6.1'


		# -- General configuration ---------------------------------------------------

+16 −10

Original line number	Diff line number	Diff line
		@@ -91,7 +91,7 @@ A summary of the versions and changes.
		\| Support new Copernicus DataSpace portal to download Sentinel data.
		\| (2023-11)

		* \| v2.6
		* \| v2.6.1
		\| Support SO\ :sub:`2` COBRA product from PAL website.
		\| (2024-01)

		@@ -135,24 +135,30 @@ A wishlist of developments.
		How to create a version tag
		===========================

		Example for tag "v2.4".
		Example for tag "v2.6.1".

		1. Update the source file `doc/source/history.rst <../../source/history.rst>`_ of this chapter.
		1. Ensure that all changes are committed and pushed::

		2. Change the release tag that will be shown in the documentation in the file
		git status
		git commit -m 'Recent updates.' .
		git push

		2. Update the source file `doc/source/history.rst <../../source/history.rst>`_ of this chapter.

		3. Change the release tag that will be shown in the documentation in the file
		`doc/source/conf.py <../../source/conf.py>`_::

		# The full version, including alpha/beta/rc tags
		release = "v2.4"
		release = "v2.6.1"

		3. Commit these changes::
		4. Commit these changes::

		git commit -m 'Tagged v2.4 .' doc/source/history.rst doc/source/conf.py
		git commit -m 'Tagged v2.6.1 .' doc/source/history.rst doc/source/conf.py

		4. Tag and push the code to the git repository::
		5. Tag and push the code to the git repository::

		git tag -a 'v2.4' -m 'Tagged v2.4'
		git push origin v2.4
		git tag -a 'v2.6.1' -m 'Tagged v2.6.1'
		git push origin 'v2.6.1'