From 21d718aa6c8a9d490364424f15c8fc4c21f42463 Mon Sep 17 00:00:00 2001 From: Donatas Abraitis Date: Wed, 27 Sep 2023 16:45:01 +0300 Subject: [PATCH 1/2] doc: Fix release dates in workflow Align to the release rules: Releases are scheduled in a 4-month cycle on the first Tuesday each March/July/November. Signed-off-by: Donatas Abraitis --- doc/developer/workflow.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/developer/workflow.rst b/doc/developer/workflow.rst index 5199d42db312..657139d74260 100644 --- a/doc/developer/workflow.rst +++ b/doc/developer/workflow.rst @@ -167,13 +167,13 @@ as early as possible, i.e. the first 2-week window. For reference, the expected release schedule according to the above is: +---------+------------+------------+------------+ -| Release | 2023-07-04 | 2023-10-31 | 2024-02-27 | +| Release | 2023-11-07 | 2024-03-05 | 2024-07-02 | +---------+------------+------------+------------+ -| RC | 2023-06-20 | 2023-10-17 | 2024-02-13 | +| RC | 2023-10-24 | 2024-02-20 | 2024-06-18 | +---------+------------+------------+------------+ -| dev/X.Y | 2023-06-06 | 2023-10-03 | 2024-01-30 | +| dev/X.Y | 2023-10-10 | 2024-02-06 | 2024-06-04 | +---------+------------+------------+------------+ -| freeze | 2023-05-23 | 2023-09-19 | 2024-01-16 | +| freeze | 2023-09-26 | 2024-01-23 | 2024-05-21 | +---------+------------+------------+------------+ Here is the hint on how to get the dates easily: @@ -1353,12 +1353,12 @@ Coverity static analysis errors prior to submission using the be installed. For example, this can be accomplished on Ubuntu with the ``sudo apt-get install clang-tools`` command. Then, touch the files you want scanned and invoke the ``scan-build`` command. For example:: - + cd ~/GitHub/frr touch ospfd/ospf_flood.c ospfd/ospf_vty.c ospfd/ospf_opaque.c cd build scan-build make -j32 - + The results of the scan including any static analysis errors will appear inline. Additionally, there will a directory in the /tmp containing the Coverity reports (e.g., scan-build-2023-06-09-120100-473730-1). From fb5f11ae678c8f02d59751f26f4b3430846a6c32 Mon Sep 17 00:00:00 2001 From: Donatas Abraitis Date: Wed, 27 Sep 2023 16:49:16 +0300 Subject: [PATCH 2/2] doc: Use backward order when for release dates hint Signed-off-by: Donatas Abraitis --- doc/developer/workflow.rst | 16 +++++++--------- 1 file changed, 7 insertions(+), 9 deletions(-) diff --git a/doc/developer/workflow.rst b/doc/developer/workflow.rst index 657139d74260..72d2a49376a6 100644 --- a/doc/developer/workflow.rst +++ b/doc/developer/workflow.rst @@ -180,15 +180,13 @@ Here is the hint on how to get the dates easily: .. code-block:: console - ~$ # Last freeze date was 2023-09-19 - ~$ date +%F --date='2023-09-19 +119 days' # Next freeze date - 2024-01-16 - ~$ date +%F --date='2024-01-16 +14 days' # Next dev/X.Y date - 2024-01-30 - ~$ date +%F --date='2024-01-30 +14 days' # Next RC date - 2024-02-13 - ~$ date +%F --date='2024-02-13 +14 days' # Next Release date - 2024-02-27 + ~$ # Release date is 2023-11-07 (First Tuesday each March/July/November) + ~$ date +%F --date='2023-11-07 -42 days' # Next freeze date + 2023-09-26 + ~$ date +%F --date='2023-11-07 -28 days' # Next dev/X.Y date + 2023-10-10 + ~$ date +%F --date='2023-11-07 -14 days' # Next RC date + 2023-10-24 Each release is managed by one or more volunteer release managers from the FRR community. These release managers are expected to handle the branch for a period