linux/poky.git/documentation/set_versions.py, branch 4.2_M3

docs: add support for langdale (4.1) release

2022-10-25T12:41:36+00:00

This adds support for the Langdale (4.1) release and update the current dev branch to Mickledore. Cc: Quentin Schulz (From yocto-docs rev: 271ae164ba901acacaf2fc910db78246637994aa) Signed-off-by: Quentin Schulz Reviewed-by: Michael Opdenacker Signed-off-by: Richard Purdie

docs: auto-generate releases.rst

2022-07-20T13:25:01+00:00

In order to maintain one less file, let's auto-generate the releases.rst file which contains a link for each release ever released. This gets auto-generated by checking the tags available in this git repo and adding a link for each that exists. A few tags are notoriously missing from this git repo and they are manually listed then, until the tags are pushed for the appropriate commit. Cc: Quentin Schulz (From yocto-docs rev: c581eda3f87390b3e5223daff74d0ed6567ec51a) Signed-off-by: Quentin Schulz Reviewed-by: Michael Opdenacker Signed-off-by: Richard Purdie

docs: set_versions.py: check for first latest release tag

2022-06-02T13:46:41+00:00

Let's not maintain manually which tag should be locally available before asking the user to run git fetch --tags. Instead, let's check for the latest release first tag (e.g. for Kirkstone, 4.0 even though 4.0.1 is already out). Cc: Quentin Schulz (From yocto-docs rev: 7466c0c37ac193fc3d089fadd426d8a802cd0650) Signed-off-by: Quentin Schulz Signed-off-by: Richard Purdie

docs: set_versions.py: remove honister from active releases list

2022-06-02T13:46:41+00:00

Honister 3.4.4 is the last release of the series and the series is now considered obsolete. Let's remove honister from the list of active releases. Cc: Quentin Schulz (From yocto-docs rev: 9e90f446b16e64138ad8556de428552cac13dcc4) Signed-off-by: Quentin Schulz Signed-off-by: Richard Purdie

docs: set_versions.py: show release name in switchers.js

2022-05-10T11:52:34+00:00

Also show release names in the dropdown menu so that people have knowledge of both the version number and release name of whatever they're using or planning to use or upgrade to. This patch will make the dropdown menu show the following entries: Unstable (dev) Kirkstone (4.0) Honister (3.4.3) Cc: Quentin Schulz (From yocto-docs rev: 83867cd979810a023eb7e2d243782e6202873273) Signed-off-by: Quentin Schulz Reviewed-by: Michael Opdenacker Signed-off-by: Richard Purdie

docs: set_versions.py: remove hardknott from active releases list

2022-05-10T11:52:34+00:00

Hardknott 3.3.6 is the last release of the series and the release is now obsolete. Let's remove hardknott from the list of active releases. Cc: Quentin Schulz (From yocto-docs rev: 4ecce89b6a5d5feb0d31c735a39619e73eeb5e44) Signed-off-by: Quentin Schulz Reviewed-by: Michael Opdenacker Signed-off-by: Richard Purdie

set_versions: Add a getlatest command to obtain the latest release branch name

2022-04-26T17:25:08+00:00

This will allow the autobuilder-helper run-docs-build script to obtain the latest release name. (From yocto-docs rev: 733b7f301e44010579e1315f19eff737628d635e) Signed-off-by: Richard Purdie

set_versions: update for 4.0 release

2022-04-26T09:56:47+00:00

Uncomment langdale lines to bump the version. (From yocto-docs rev: e0016979413ab27f2e5db88ae1de180507c759c2) Signed-off-by: Michael Halstead Signed-off-by: Richard Purdie

docs: sphinx-static: switchers.js.in: fix broken switcher for branches

2022-04-20T16:25:33+00:00

The switcher expects URL subpath to match the "release" used by sphinx to build the documentation. Branches, however, are put in a subpath after their name (e.g. dunfell) while sphinx sets the "release" to X.Y.999. This means the switcher cannot replace correctly the path to switch between releases/versions. Let set_versions.py inject the list of release names into the switchers.js.in file so it can check whether the subpath is one of the release names in which case it needs to be stripped. Cc: Quentin Schulz (From yocto-docs rev: 5ef3d129b8d0d8ae98a694103930988a46285525) Signed-off-by: Quentin Schulz Signed-off-by: Richard Purdie

docs: set_versions.py: mark as obsolete only branches and old tags from obsolete releases

2022-04-20T16:25:33+00:00

Branches are identified by their .999 version suffix which means they will never be matched in the forloop above this git context. Therefore, branches will match the condition. However, branches are not necessarily obsolete (e.g. dunfell, honister and kirkstone today), so let's mark as obsolete the branches which are from obsolete releases. Old tags of currently supported releases are not defined as obsolete but outdated, therefore using the series to which they belong like it is done for branches is enough for obsolescence detection. Cc: Quentin Schulz (From yocto-docs rev: 7181a432da18b47608784363d243ea39b80be1ed) Signed-off-by: Quentin Schulz Signed-off-by: Richard Purdie