#44374: S3_2 branching
Open Date: 2022-04-14 13:43
Last Update: 2022-04-25 14:59
URL for this Ticket:
https://osdn.net//projects/freeciv/ticket/44374
RSS feed for this Ticket:
https://osdn.net/ticket/ticket_rss.php?group_id=12505&tid=44374
---------------------------------------------------------------------
Last Changes/Comment on this Ticket:
2022-04-25 14:59 Updated by: cazfi
Comment:
Reply To alain_bkr
Why create in advance a S3_2 branch, and not keep development in master until it reaches a alpha status ?
Yes, branching is where we change the version label to "alpha". That people tend to after branching try (and get) to get in such development that really belongs to master only is another problem. The time our versions live in "stable" (that's what 'S' is supposed to mean) is ridiculous, though it's partly due to compatibility freeze levels.
---------------------------------------------------------------------
Ticket Status:
Reporter: cazfi
Owner: cazfi
Type: Tasks
Status: Open [Owner assigned]
Priority: 5 - Medium
MileStone: (None)
Component: (None)
Severity: 5 - Medium
Resolution: None
---------------------------------------------------------------------
Ticket details:
This ticket is for collecting things needed for next branching from master, namely that of S3_2.
For reference, ticket about S3_1 branching: https://www.hostedredmine.com/issues/656468
S3_1 was branched in the beginning of February 2021. With the planned every-two-years frequency we then aim to S3_2 branching in early 2023.
--
#44375 - Rename of 'master'
--
Ticket information of Freeciv project
Freeciv Project is hosted on OSDN
Project URL: https://osdn.net/projects/freeciv/
OSDN: https://osdn.net
URL for this Ticket:
https://osdn.net/projects/freeciv/ticket/44374
RSS feed for this Ticket:
https://osdn.net/ticket/ticket_rss.php?group_id=12505&tid=44374