Skip to content

Latest commit

 

History

History
174 lines (136 loc) · 8.39 KB

release_process.md

File metadata and controls

174 lines (136 loc) · 8.39 KB
Raw

This document is meant to explain the workflow to effectively and bug-freely release a new version of QGIS documentation

Versions and branch naming

Different versions of documentation are usually released by the QGIS project and are somehow tied to the development cycle of the software:

  1. testing: targets functionalities available in the development cycle or in versions newer than the latest Long Term Release (LTR). Source files are available in the master branch. The released documentation is accessible at https://docs.qgis.org/testing.
  2. latest: targets functionalities available in the current Long Term Release. Documentation source files are available in release_x.y branch where x.y represents the version number. The released documentation is accessible at https://docs.qgis.org/latest or https://docs.qgis.org/x.y.
  3. When the first release of the next-to-be LTR is published, a new release_x.y branch is also created in the documentation repository and covers features available in that version (some are not in the current LTR). The documentation is accessible through https://docs.qgis.org/x.y. When that version becomes LTR months later, latest URL is redirected to that version.

Release steps

New releases are branched off the master branch. Following changes are required:

When LTR is still unchanged

This usually happens from the October release.

Instructions when the next LTR is first released and there is no LTR switch

master branch

Before creating the new release branch

Following changes have to be done in master branch before you create the new release branch. Otherwise, you will have to do the changes twice: in master and in the new branch.

  • In substitutions.txt file, replace |CURRENT| value with the new version number
  • In docs_conf.yml file: add the new release number to the version_list parameter
  • In dependabot.yml file: Add label for backporting dependencies update to the new branch

You can now create the release_x.y branch in the repository, based on master.

After the new branch is created

  • In substitutions.txt file:
    • Remove intermediate versions substitutions and their occurrences in the rst files
    • Add substitutions for the versions of the next LTR cycle that starts (e.g. if you just create the release_3.22 branch, you should add to the master branch substitutions for 3.24, 3.26 and 3.28)

Current LTR branch

  • In docs_conf.yml file, add the new release number to the version_list parameter

New release_x.y branch

New releases are branched off the `master` branch and thus require a set of changes.
  • Ensure that changes to do in master before creating the new release branch are applied
  • If not yet done, create the release_x.y branch in the repository, based on master
  • Update the new branch, as follows:
    • In conf.py file:
      • set the version value (in the form x.y)
      • set the html_context isTesting option to False
    • In README.MD file, update the badges to point to the current branch instead of master, and current version instead of testing
    • In Makefile file, set the VERSION number as in the conf.py file
    • In doctest.dockerfile: set the project container to pull QGIS sources from (i.e. x.y)
    • In main index.rst file: replace testing with x.y in the Table Of Contents

Repositories and project configuration

  • ⚠️ Make sure that the C++ API documentation of the new version is available (normally done automatically during software release steps)
  • ⚠️ Make sure that the PyQGIS documentation of the new version is available. This may require update of the current_stable value in pyqgis_conf.yml.
  • Add new labels to triage issues and pull requests: backport <new_branch>, new target versions
  • Create a new milestone for the new cycle of LTR that starts
  • Reference the new version in the docs index page of QGIS main website. Source file is available at hub.md

Server

  • Update commands to publish the new version (in English, as html, zip and pdf) and avoid redirecting it to testing

When the new LTR is published

In February, the new version is labeled as LTR, and replaces the previous one in many places.

Instructions when the new LTR officially takes place

Old LTR branch

  • In conf.py file: set the html_context outdated option to True
  • Pull translations for all languages from transifex (see instructions in README file)
  • Build the docs one more time

New LTR branch

  • In docs_conf.yml file: add target languages to the supported_languages parameter. These are the languages that will be published in the documentation. A threshold of 5% is currently applied to candidates.
  • In docker-world.sh file: complete the langs variable with the supported languages
  • In the Makefile: add the supported languages to the LANGUAGES parameter
  • Copy the locale folder from the old LTR branch to the new LTR branch
  • Generate new English source files (see instructions in README file)

Transifex platform

Translated versions are available only for long term releases and only the active LTR is being translated. So when a new LTR is published, we disconnect the old one and connect the new one.
  • ⚠️ Make sure that the translated files from the old LTR branch have been correctly pasted to the new LTR branch
  • Link the new LTR branch to the QGIS-Documentation project (read docs on Transifex)
  • If the connection above does not correctly proceed and update files in the transifex platform, see workaround instructions in README file

master branch

  • In fix_versions.sh file:
    • add the old LTR number to the DEPRECATED parameter
    • add the new LTR number to the DOCVERSIONS parameter
  • In pofiles.yml: update branch to the new LTR branch in order to generate updated English *.po source files to push to Transifex
  • In pull_minimize_translations.yml: update target_branch to the new LTR branch in which to pull translations from Transifex
  • In translation_statistics.yml: update target_branch to the branch(es) in which to generate translation statistics
  • In dependabot.yml file: Remove label for backporting dependencies update to the old LTR version

Repository and project configuration

  • Update the docs index page. Source file is available hub.md
    • Reference the new version as current LTR
    • Move the old lTR under the "archived releases" tab.

Server

  • Redirect latest URL to the new LTR pages
  • Update commands to publish the new version (in released languages, as html, zip and pdf)

Possible improvements

Many parts of the process are currently manual. This sometimes results in failing builds because some steps were overlooked/forgotten. Automating the process as much as possible would lower the risk and make it less time consuming.

  • Some values are somehow copy-pasted across places while they could likely be put in a variable:

    • languages list: they are defined in docs_conf.yml, Makefile
    • version number: it is defined in conf.py, Makefile, doctest.dockerfile