Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: Fix release dates in workflow #14495

Merged
merged 2 commits into from
Sep 27, 2023
Merged

doc: Fix release dates in workflow #14495

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
21d718a
doc: Fix release dates in workflow
ton31337 Sep 27, 2023
fb5f11a
doc: Use backward order when for release dates hint
ton31337 Sep 27, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 13 additions & 15 deletions doc/developer/workflow.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -167,28 +167,26 @@ 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:

.. 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
Expand Down Expand Up @@ -1353,12 +1351,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).
Expand Down