mirror of
https://git.proxmox.com/git/mirror_frr
synced 2025-08-11 11:21:07 +00:00
doc: Update release dates and add a hint on how to get dates correctly
Signed-off-by: Donatas Abraitis <donatas@opensourcerouting.org>
This commit is contained in:
parent
89eb8c8e4d
commit
9de44c0a1b
@ -163,15 +163,29 @@ as early as possible, i.e. the first 2-week window.
|
||||
For reference, the expected release schedule according to the above is:
|
||||
|
||||
+---------+------------+------------+------------+------------+------------+
|
||||
| Release | 2022-07-05 | 2022-11-01 | 2023-03-07 | 2023-07-04 | 2023-10-31 |
|
||||
| Release | 2023-03-07 | 2023-07-04 | 2023-10-31 | 2024-02-27 | 2024-06-25 |
|
||||
+---------+------------+------------+------------+------------+------------+
|
||||
| RC | 2022-06-21 | 2022-10-18 | 2023-02-21 | 2023-06-20 | 2023-10-17 |
|
||||
| RC | 2023-02-21 | 2023-06-20 | 2023-10-17 | 2024-02-13 | 2024-06-11 |
|
||||
+---------+------------+------------+------------+------------+------------+
|
||||
| dev/X.Y | 2022-06-07 | 2022-10-04 | 2023-02-07 | 2023-06-06 | 2023-10-03 |
|
||||
| dev/X.Y | 2023-02-07 | 2023-06-06 | 2023-10-03 | 2024-01-30 | 2024-05-28 |
|
||||
+---------+------------+------------+------------+------------+------------+
|
||||
| freeze | 2022-05-24 | 2022-09-20 | 2023-01-24 | 2023-05-23 | 2023-09-19 |
|
||||
| freeze | 2023-01-24 | 2023-05-23 | 2023-09-19 | 2024-01-16 | 2024-05-14 |
|
||||
+---------+------------+------------+------------+------------+------------+
|
||||
|
||||
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
|
||||
|
||||
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
|
||||
of one year. To spread and distribute this workload, this should be rotated for
|
||||
|
Loading…
Reference in New Issue
Block a user