BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//releases.openstack.org//EN
X-WR-CALNAME:OpenStack Release Schedule
BEGIN:VEVENT
SUMMARY:Antelope R-23
DTSTART;VALUE=DATE:20221010
DTEND;VALUE=DATE:20221015
DTSTAMP:20221021T120850Z
UID:Antelope-R-23
END:VEVENT
BEGIN:VEVENT
SUMMARY:Antelope R-22 (2023.1 Antelope Project Team Gathering (PTG))
DTSTART;VALUE=DATE:20221017
DTEND;VALUE=DATE:20221022
DTSTAMP:20221021T120850Z
UID:Antelope-R-22
DESCRIPTION:2023.1 Antelope Project Team Gathering (PTG)\n\nA Virtual PTG 
 will be held during this week (October 17-21\, 2022). The Project Teams Ga
 thering provides an opportunity for teams to collaborate and plan\, and di
 scuss requirements for future releases.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Antelope R-21
DTSTART;VALUE=DATE:20221024
DTEND;VALUE=DATE:20221029
DTSTAMP:20221021T120850Z
UID:Antelope-R-21
END:VEVENT
BEGIN:VEVENT
SUMMARY:Antelope R-20
DTSTART;VALUE=DATE:20221031
DTEND;VALUE=DATE:20221105
DTSTAMP:20221021T120850Z
UID:Antelope-R-20
END:VEVENT
BEGIN:VEVENT
SUMMARY:Antelope R-19
DTSTART;VALUE=DATE:20221107
DTEND;VALUE=DATE:20221112
DTSTAMP:20221021T120850Z
UID:Antelope-R-19
END:VEVENT
BEGIN:VEVENT
SUMMARY:Antelope R-18 (Antelope-1 milestone)
DTSTART;VALUE=DATE:20221114
DTEND;VALUE=DATE:20221119
DTSTAMP:20221021T120850Z
UID:Antelope-R-18
DESCRIPTION:Antelope-1 milestone\n\n17 November\, 2022 is the Antelope-1 m
 ilestone. See project-specific notes for relevant deadlines.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Antelope R-17
DTSTART;VALUE=DATE:20221121
DTEND;VALUE=DATE:20221126
DTSTAMP:20221021T120850Z
UID:Antelope-R-17
END:VEVENT
BEGIN:VEVENT
SUMMARY:Antelope R-16
DTSTART;VALUE=DATE:20221128
DTEND;VALUE=DATE:20221203
DTSTAMP:20221021T120850Z
UID:Antelope-R-16
END:VEVENT
BEGIN:VEVENT
SUMMARY:Antelope R-15
DTSTART;VALUE=DATE:20221205
DTEND;VALUE=DATE:20221210
DTSTAMP:20221021T120850Z
UID:Antelope-R-15
END:VEVENT
BEGIN:VEVENT
SUMMARY:Antelope R-14 (Zed Cycle-Trailing Release Deadline)
DTSTART;VALUE=DATE:20221212
DTEND;VALUE=DATE:20221217
DTSTAMP:20221021T120850Z
UID:Antelope-R-14
DESCRIPTION:Zed Cycle-Trailing Release Deadline\n\nAll projects following 
 the cycle-trailing release model must release their Zed deliverables by 14
  December\, 2022.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Antelope R-13
DTSTART;VALUE=DATE:20221219
DTEND;VALUE=DATE:20221224
DTSTAMP:20221021T120850Z
UID:Antelope-R-13
END:VEVENT
BEGIN:VEVENT
SUMMARY:Antelope R-12
DTSTART;VALUE=DATE:20221226
DTEND;VALUE=DATE:20221231
DTSTAMP:20221021T120850Z
UID:Antelope-R-12
END:VEVENT
BEGIN:VEVENT
SUMMARY:Antelope R-11 (Antelope-2 milestone\; Membership Freeze)
DTSTART;VALUE=DATE:20230102
DTEND;VALUE=DATE:20230107
DTSTAMP:20221021T120850Z
UID:Antelope-R-11
DESCRIPTION:Antelope-2 milestone\n\n05 January\, 2023 is the Antelope-2 mi
 lestone. See project-specific notes for relevant deadlines.\n\n\n\nMembers
 hip Freeze\n\nProjects must participate in at least two milestones in orde
 r to be considered part of the release. Projects made official after the s
 econd milestone\, or which fail to produce milestone releases for at least
  one of the first and second milestones as well as the third milestone\, a
 re therefore not considered part of the release for the cycle. This does n
 ot apply to cycle-trailing packaging / lifecycle management projects.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Antelope R-10
DTSTART;VALUE=DATE:20230109
DTEND;VALUE=DATE:20230114
DTSTAMP:20221021T120850Z
UID:Antelope-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Antelope R-9
DTSTART;VALUE=DATE:20230116
DTEND;VALUE=DATE:20230121
DTSTAMP:20221021T120850Z
UID:Antelope-R-9
END:VEVENT
BEGIN:VEVENT
SUMMARY:Antelope R-8
DTSTART;VALUE=DATE:20230123
DTEND;VALUE=DATE:20230128
DTSTAMP:20221021T120850Z
UID:Antelope-R-8
END:VEVENT
BEGIN:VEVENT
SUMMARY:Antelope R-7 (Extra-ATC freeze\; 2023.2 Election Nomination Begins
 )
DTSTART;VALUE=DATE:20230130
DTEND;VALUE=DATE:20230204
DTSTAMP:20221021T120850Z
UID:Antelope-R-7
DESCRIPTION:Extra-ATC freeze\n\nAll contributions to OpenStack are valuabl
 e\, but some are not expressed as Gerrit code changes. That allow teams to
  list active contributors to their projects and who do not have a code con
 tribution this cycle\, and therefore won’t automatically be considered a
 n Active Technical Contributor and allowed to vote. This is done by adding
  extra-atcs to https://opendev.org/openstack/governance/src/branch/master/
 reference/projects.yaml before the Extra-ATC freeze on 02 February\, 2023.
 \n\n2023.2 Election Nomination Begins\n\nCandidates interested in serving 
 for the next calendar year (TC)\, or development cycle (PTL) should announ
 ce their candidacies and platforms during this week.  Please see the Elect
 ion site for specific timing information.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Antelope R-6 (Final release for non-client libraries)
DTSTART;VALUE=DATE:20230206
DTEND;VALUE=DATE:20230211
DTSTAMP:20221021T120850Z
UID:Antelope-R-6
DESCRIPTION:Final release for non-client libraries\n\nLibraries that are n
 ot client libraries (Oslo and others) should issue their final release dur
 ing this week. That allows to give time for last-minute changes before fea
 ture freeze.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Antelope R-5 (Antelope-3 milestone\; Feature freeze\; Final releas
 e for client libraries\; Soft StringFreeze\; Requirements freeze\; 2023.2 
 Election Campaigning Begins)
DTSTART;VALUE=DATE:20230213
DTEND;VALUE=DATE:20230218
DTSTAMP:20221021T120850Z
UID:Antelope-R-5
DESCRIPTION:Antelope-3 milestone\n\n16 February\, 2023 is the Antelope-3 m
 ilestone. See project-specific notes for relevant deadlines.\n\n\n\nFeatur
 e freeze\n\nThe Antelope-3 milestone marks feature freeze for projects fol
 lowing the release:cycle-with-rc model. No featureful patch should be land
 ed after this point. Exceptions may be granted by the project PTL.\n\n\n\n
 \n\nFinal release for client libraries\n\nClient libraries should issue th
 eir final release during this week\, to match feature freeze.\n\n\n\nSoft 
 StringFreeze\n\nYou are no longer allowed to accept proposed changes conta
 ining modifications in user-facing strings. Such changes should be rejecte
 d by the review team and postponed until the next series development opens
  (which should happen when RC1 is published).\n\n\n\nRequirements freeze\n
 \nAfter the Antelope-3 milestone\, only critical requirements and constrai
 nts changes will be allowed. Freezing our requirements list gives packager
 s downstream an opportunity to catch up and prepare packages for everythin
 g necessary for distributions of the upcoming release. The requirements re
 main frozen until the stable branches are created\, with the release candi
 dates.\n\n\n\n2023.2 Election Campaigning Begins\n\nThe electorate has tim
 e to ask candidates questions about their platforms and debate topics befo
 re polling begins.  Please see the Election site for specific timing infor
 mation.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Antelope R-4 (Cycle Highlights\; 2023.2 Election Polling Begins)
DTSTART;VALUE=DATE:20230220
DTEND;VALUE=DATE:20230225
DTSTAMP:20221021T120850Z
UID:Antelope-R-4
DESCRIPTION:Cycle Highlights\n\nCycle highlights need to be added to the r
 elease deliverables after the feature freeze to be included in any marketi
 ng release messaging. Highlights may be added after this point\, but they 
 will likely only be useful for historical purposes.\n\nSee the Project Tea
 m Guide for more details and instructions on adding these highlights.\n\nF
 or examples of previous release highlights: Stein Highlights\, Train Highl
 ights\, Ussuri Highlights\, Victoria Highlights\, Wallaby Highlights\, Xen
 a Highlights\, Yoga Highlights\, Zed Highlights.\n\n\n\n2023.2 Election Po
 lling Begins\n\nElection polling for open seats on the TC and any required
  PTL elections. Please see the Election site for specific timing informati
 on.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Antelope R-3 (RC1 target week\; Hard StringFreeze)
DTSTART;VALUE=DATE:20230227
DTEND;VALUE=DATE:20230304
DTSTAMP:20221021T120850Z
UID:Antelope-R-3
DESCRIPTION:RC1 target week\n\nThe week of 27 February\, 2023 is the targe
 t date for projects following the release:cycle-with-rc model to issue the
 ir first release candidate.\n\n\n\nHard StringFreeze\n\nThis happens when 
 the RC1 for the project is tagged. At this point\, ideally no strings are 
 changed (or added\, or removed)\, to give translators time to finish up th
 eir efforts.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Antelope R-2 (2023.2 Election Polling Ends)
DTSTART;VALUE=DATE:20230306
DTEND;VALUE=DATE:20230311
DTSTAMP:20221021T120850Z
UID:Antelope-R-2
DESCRIPTION:2023.2 Election Polling Ends\n\nAll polls close in the 2023.2 
 Election and results announced.  Please see the Election site for specific
  timing information.\n\n\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Antelope R-1 (Final RCs and intermediary releases)
DTSTART;VALUE=DATE:20230313
DTEND;VALUE=DATE:20230318
DTSTAMP:20221021T120850Z
UID:Antelope-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of 13th - 17th
  March\, 2023 is the last week to issue release candidates or intermediary
  releases before release week. During release week\, only final-release-cr
 itical releases will be accepted (at the discretion of the release team).\
 n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Antelope R+0 (Antelope release)
DTSTART;VALUE=DATE:20230320
DTEND;VALUE=DATE:20230325
DTSTAMP:20221021T120850Z
UID:Antelope-R+0
DESCRIPTION:Antelope release\n\nThe Antelope coordinated release will happ
 en on Wednesday\, 22 March\, 2023.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-27 (PTG (virtual))
DTSTART;VALUE=DATE:20230327
DTEND;VALUE=DATE:20230401
DTSTAMP:20230703T201539Z
UID:Bobcat-R-27
DESCRIPTION:PTG (virtual)\n\nFrom March 27 to March 31 we’ll have a virt
 ual PTG to plan the Bobcat release schedule.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-26
DTSTART;VALUE=DATE:20230403
DTEND;VALUE=DATE:20230408
DTSTAMP:20230703T201539Z
UID:Bobcat-R-26
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-25
DTSTART;VALUE=DATE:20230410
DTEND;VALUE=DATE:20230415
DTSTAMP:20230703T201539Z
UID:Bobcat-R-25
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-24
DTSTART;VALUE=DATE:20230417
DTEND;VALUE=DATE:20230422
DTSTAMP:20230703T201539Z
UID:Bobcat-R-24
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-23
DTSTART;VALUE=DATE:20230424
DTEND;VALUE=DATE:20230429
DTSTAMP:20230703T201539Z
UID:Bobcat-R-23
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-22
DTSTART;VALUE=DATE:20230501
DTEND;VALUE=DATE:20230506
DTSTAMP:20230703T201539Z
UID:Bobcat-R-22
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-21 (Bobcat-1 milestone)
DTSTART;VALUE=DATE:20230508
DTEND;VALUE=DATE:20230513
DTSTAMP:20230703T201539Z
UID:Bobcat-R-21
DESCRIPTION:Bobcat-1 milestone\n\nMay 11\, 2023 is the Bobcat-1 milestone.
  See project-specific notes for relevant deadlines.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-20
DTSTART;VALUE=DATE:20230515
DTEND;VALUE=DATE:20230520
DTSTAMP:20230703T201539Z
UID:Bobcat-R-20
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-19
DTSTART;VALUE=DATE:20230522
DTEND;VALUE=DATE:20230527
DTSTAMP:20230703T201539Z
UID:Bobcat-R-19
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-18 (Antelope Cycle-Trailing Release Deadline)
DTSTART;VALUE=DATE:20230529
DTEND;VALUE=DATE:20230603
DTSTAMP:20230703T201539Z
UID:Bobcat-R-18
DESCRIPTION:Antelope Cycle-Trailing Release Deadline\n\nAll projects follo
 wing the cycle-trailing release model must release their Antelope delivera
 bles by June 1st\, 2023.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-17
DTSTART;VALUE=DATE:20230605
DTEND;VALUE=DATE:20230610
DTSTAMP:20230703T201539Z
UID:Bobcat-R-17
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-16 (OpenInfra Summit in Vancouver)
DTSTART;VALUE=DATE:20230612
DTEND;VALUE=DATE:20230617
DTSTAMP:20230703T201539Z
UID:Bobcat-R-16
DESCRIPTION:OpenInfra Summit in Vancouver\n\nFrom June 13 to June 15\, 202
 3\, the OpenStack community will gather in Vancouver for the OpenInfra Sum
 mit. Discussions on the future of the software\, as well as project team m
 eetings will happen there.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-15
DTSTART;VALUE=DATE:20230619
DTEND;VALUE=DATE:20230624
DTSTAMP:20230703T201539Z
UID:Bobcat-R-15
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-14
DTSTART;VALUE=DATE:20230626
DTEND;VALUE=DATE:20230701
DTSTAMP:20230703T201539Z
UID:Bobcat-R-14
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-13 (Bobcat-2 milestone\; Membership Freeze)
DTSTART;VALUE=DATE:20230703
DTEND;VALUE=DATE:20230708
DTSTAMP:20230703T201539Z
UID:Bobcat-R-13
DESCRIPTION:Bobcat-2 milestone\n\nJuly 6\, 2023 is the Bobcat-2 milestone.
  See project-specific notes for relevant deadlines.\n\n\n\nMembership Free
 ze\n\nProjects must participate in at least two milestones in order to be 
 considered part of the release. Projects made official after the second mi
 lestone\, or which fail to produce milestone releases for at least one of 
 the first and second milestones as well as the third milestone\, are there
 fore not considered part of the release for the cycle. This does not apply
  to cycle-trailing packaging / lifecycle management projects.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-12
DTSTART;VALUE=DATE:20230710
DTEND;VALUE=DATE:20230715
DTSTAMP:20230703T201539Z
UID:Bobcat-R-12
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-11
DTSTART;VALUE=DATE:20230717
DTEND;VALUE=DATE:20230722
DTSTAMP:20230703T201539Z
UID:Bobcat-R-11
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-10
DTSTART;VALUE=DATE:20230724
DTEND;VALUE=DATE:20230729
DTSTAMP:20230703T201539Z
UID:Bobcat-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-9
DTSTART;VALUE=DATE:20230731
DTEND;VALUE=DATE:20230805
DTSTAMP:20230703T201539Z
UID:Bobcat-R-9
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-8
DTSTART;VALUE=DATE:20230807
DTEND;VALUE=DATE:20230812
DTSTAMP:20230703T201539Z
UID:Bobcat-R-8
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-7 (Extra-ATC freeze)
DTSTART;VALUE=DATE:20230814
DTEND;VALUE=DATE:20230819
DTSTAMP:20230703T201539Z
UID:Bobcat-R-7
DESCRIPTION:Extra-ATC freeze\n\nAll contributions to OpenStack are valuabl
 e\, but some are not expressed as Gerrit code changes. That allow teams to
  list active contributors to their projects and who do not have a code con
 tribution this cycle\, and therefore won’t automatically be considered a
 n Active Technical Contributor and allowed to vote. This is done by adding
  extra-atcs to https://opendev.org/openstack/governance/src/branch/master/
 reference/projects.yaml before the Extra-ATC freeze on August 17\, 2023.\n
 \n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-6 (Final release for non-client libraries\; 2024.1 Electi
 on Nomination Begins)
DTSTART;VALUE=DATE:20230821
DTEND;VALUE=DATE:20230826
DTSTAMP:20230703T201539Z
UID:Bobcat-R-6
DESCRIPTION:Final release for non-client libraries\n\nLibraries that are n
 ot client libraries (Oslo and others) should issue their final release dur
 ing this week. That allows to give time for last-minute changes before fea
 ture freeze.\n\n\n\n2024.1 Election Nomination Begins\n\nCandidates intere
 sted in serving for the next calendar year (TC)\, or development cycle (PT
 L) should announce their candidacies and platforms during this week.  Plea
 se see the Election site for specific timing information.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-5 (Bobcat-3 milestone\; Feature freeze\; Final release fo
 r client libraries\; Soft StringFreeze\; Requirements freeze\; Cycle Highl
 ights\; 2024.1 Election Nomination Begins)
DTSTART;VALUE=DATE:20230828
DTEND;VALUE=DATE:20230902
DTSTAMP:20230703T201539Z
UID:Bobcat-R-5
DESCRIPTION:Bobcat-3 milestone\n\nAugust 31\, 2023 is the Bobcat-3 milesto
 ne. See project-specific notes for relevant deadlines.\n\n\n\nFeature free
 ze\n\nThe Bobcat-3 milestone marks feature freeze for projects following t
 he release:cycle-with-rc model. No featureful patch should be landed after
  this point. Exceptions may be granted by the project PTL.\n\n\n\n\n\nFina
 l release for client libraries\n\nClient libraries should issue their fina
 l release during this week\, to match feature freeze.\n\n\n\nSoft StringFr
 eeze\n\nYou are no longer allowed to accept proposed changes containing mo
 difications in user-facing strings. Such changes should be rejected by the
  review team and postponed until the next series development opens (which 
 should happen when RC1 is published).\n\n\n\nRequirements freeze\n\nAfter 
 the Bobcat-3 milestone\, only critical requirements and constraints change
 s will be allowed. Freezing our requirements list gives packagers downstre
 am an opportunity to catch up and prepare packages for everything necessar
 y for distributions of the upcoming release. The requirements remain froze
 n until the stable branches are created\, with the release candidates.\n\n
 \n\nCycle Highlights\n\nCycle highlights need to be added to the release d
 eliverables after the feature freeze to be included in any marketing relea
 se messaging. Highlights may be added after this point\, but they will lik
 ely only be useful for historical purposes.\n\nSee the Project Team Guide 
 for more details and instructions on adding these highlights.\n\nFor examp
 les of previous release highlights: Stein Highlights\, Train Highlights\, 
 Ussuri Highlights\, Victoria Highlights\, Wallaby Highlights\, Xena Highli
 ghts\, Yoga Highlights\, Zed Highlights.\n\n\n\n2024.1 Election Nomination
  Begins\n\nCandidates interested in serving for the next calendar year (TC
 )\, or development cycle (PTL) should announce their candidacies and platf
 orms during this week.  Please see the Election site for specific timing i
 nformation.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-4 (2024.1 Election Email Deadline\; 2024.1 Election Campa
 igning Begins)
DTSTART;VALUE=DATE:20230904
DTEND;VALUE=DATE:20230909
DTSTAMP:20230703T201539Z
UID:Bobcat-R-4
DESCRIPTION:2024.1 Election Email Deadline\n\nContributors that will be in
  the electorate for the upcoming election should confirm their gerrit emai
 l addresses by this date (August 30th\, 2023 at 00:00 UTC). Electorate rol
 ls are generated after this date and ballots will be sent to the listed ge
 rrit email address.\n\n\n\n2024.1 Election Campaigning Begins\n\nThe elect
 orate has time to ask candidates questions about their platforms and debat
 e topics before polling begins.  Please see the Election site for specific
  timing information.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-3 (RC1 target week\; Hard StringFreeze\; 2024.1 Election 
 Polling Begins)
DTSTART;VALUE=DATE:20230911
DTEND;VALUE=DATE:20230916
DTSTAMP:20230703T201539Z
UID:Bobcat-R-3
DESCRIPTION:RC1 target week\n\nThe week of September 11\, 2023 is the targ
 et date for projects following the release:cycle-with-rc model to issue th
 eir first release candidate.\n\n\n\nHard StringFreeze\n\nThis happens when
  the RC1 for the project is tagged. At this point\, ideally no strings are
  changed (or added\, or removed)\, to give translators time to finish up t
 heir efforts.\n\n\n\n2024.1 Election Polling Begins\n\nElection polling fo
 r open seats on the TC and any required PTL elections. Please see the Elec
 tion site for specific timing information.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-2 (2024.1 Election Polling Begins)
DTSTART;VALUE=DATE:20230918
DTEND;VALUE=DATE:20230923
DTSTAMP:20230703T201539Z
UID:Bobcat-R-2
DESCRIPTION:2024.1 Election Polling Begins\n\nElection polling for open se
 ats on the TC and any required PTL elections. Please see the Election site
  for specific timing information.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R-1 (Final RCs and intermediary releases\; 2024.1 Election 
 Polling Ends)
DTSTART;VALUE=DATE:20230925
DTEND;VALUE=DATE:20230930
DTSTAMP:20230703T201539Z
UID:Bobcat-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of September 2
 5\, 2023 is the last week to issue release candidates or intermediary rele
 ases before release week. During release week\, only final-release-critica
 l releases will be accepted (at the discretion of the release team).\n\n\n
 \n2024.1 Election Polling Ends\n\nAll polls close in the 2024.1 Election a
 nd results announced.  Please see the Election site for specific timing in
 formation.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Bobcat R+0 (Bobcat release)
DTSTART;VALUE=DATE:20231002
DTEND;VALUE=DATE:20231007
DTSTAMP:20230703T201539Z
UID:Bobcat-R+0
DESCRIPTION:Bobcat release\n\nThe Bobcat coordinated release will happen o
 n Wednesday\, October 4\, 2023.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-25
DTSTART;VALUE=DATE:20231009
DTEND;VALUE=DATE:20231014
DTSTAMP:20240110T112953Z
UID:Caracal-R-25
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-24
DTSTART;VALUE=DATE:20231016
DTEND;VALUE=DATE:20231021
DTSTAMP:20240110T112953Z
UID:Caracal-R-24
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-23 (PTG (virtual))
DTSTART;VALUE=DATE:20231023
DTEND;VALUE=DATE:20231028
DTSTAMP:20240110T112953Z
UID:Caracal-R-23
DESCRIPTION:PTG (virtual)\n\nFrom October 23 to October 27 we’ll have a 
 virtual PTG to plan the Caracal release schedule.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-22
DTSTART;VALUE=DATE:20231030
DTEND;VALUE=DATE:20231104
DTSTAMP:20240110T112953Z
UID:Caracal-R-22
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-21
DTSTART;VALUE=DATE:20231106
DTEND;VALUE=DATE:20231111
DTSTAMP:20240110T112953Z
UID:Caracal-R-21
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-20 (Caracal-1 milestone)
DTSTART;VALUE=DATE:20231113
DTEND;VALUE=DATE:20231118
DTSTAMP:20240110T112953Z
UID:Caracal-R-20
DESCRIPTION:Caracal-1 milestone\n\nNovember 16\, 2023 is the Caracal-1 mil
 estone. See project-specific notes for relevant deadlines.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-19
DTSTART;VALUE=DATE:20231120
DTEND;VALUE=DATE:20231125
DTSTAMP:20240110T112953Z
UID:Caracal-R-19
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-18
DTSTART;VALUE=DATE:20231127
DTEND;VALUE=DATE:20231202
DTSTAMP:20240110T112953Z
UID:Caracal-R-18
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-17 (Bobcat Cycle-Trailing Release Deadline)
DTSTART;VALUE=DATE:20231204
DTEND;VALUE=DATE:20231209
DTSTAMP:20240110T112953Z
UID:Caracal-R-17
DESCRIPTION:Bobcat Cycle-Trailing Release Deadline\n\nAll projects followi
 ng the cycle-trailing release model must release their Bobcat deliverables
  by 7 December\, 2023.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-16
DTSTART;VALUE=DATE:20231211
DTEND;VALUE=DATE:20231216
DTSTAMP:20240110T112953Z
UID:Caracal-R-16
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-15
DTSTART;VALUE=DATE:20231218
DTEND;VALUE=DATE:20231223
DTSTAMP:20240110T112953Z
UID:Caracal-R-15
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-14
DTSTART;VALUE=DATE:20231225
DTEND;VALUE=DATE:20231230
DTSTAMP:20240110T112953Z
UID:Caracal-R-14
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-13
DTSTART;VALUE=DATE:20240101
DTEND;VALUE=DATE:20240106
DTSTAMP:20240110T112953Z
UID:Caracal-R-13
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-12 (Caracal-2 milestone\; Membership Freeze)
DTSTART;VALUE=DATE:20240108
DTEND;VALUE=DATE:20240113
DTSTAMP:20240110T112953Z
UID:Caracal-R-12
DESCRIPTION:Caracal-2 milestone\n\nJanuary 11\, 2024 is the Caracal-2 mile
 stone. See project-specific notes for relevant deadlines.\n\n\n\nMembershi
 p Freeze\n\nProjects must participate in at least two milestones in order 
 to be considered part of the release. Projects made official after the sec
 ond milestone\, or which fail to produce milestone releases for at least o
 ne of the first and second milestones as well as the third milestone\, are
  therefore not considered part of the release for the cycle. This does not
  apply to cycle-trailing packaging / lifecycle management projects.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-11
DTSTART;VALUE=DATE:20240115
DTEND;VALUE=DATE:20240120
DTSTAMP:20240110T112953Z
UID:Caracal-R-11
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-10
DTSTART;VALUE=DATE:20240122
DTEND;VALUE=DATE:20240127
DTSTAMP:20240110T112953Z
UID:Caracal-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-9
DTSTART;VALUE=DATE:20240129
DTEND;VALUE=DATE:20240203
DTSTAMP:20240110T112953Z
UID:Caracal-R-9
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-8
DTSTART;VALUE=DATE:20240205
DTEND;VALUE=DATE:20240210
DTSTAMP:20240110T112953Z
UID:Caracal-R-8
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-7 (Extra-AC freeze)
DTSTART;VALUE=DATE:20240212
DTEND;VALUE=DATE:20240217
DTSTAMP:20240110T112953Z
UID:Caracal-R-7
DESCRIPTION:Extra-AC freeze\n\nAll contributions to OpenStack are valuable
 \, but some are not expressed as Gerrit code changes. That allow teams to 
 list active contributors to their projects and who do not have a code cont
 ribution this cycle\, and therefore won’t automatically be considered an
  Active Contributor and allowed to vote. This is done by adding extra-acs 
 to https://opendev.org/openstack/governance/src/branch/master/reference/pr
 ojects.yaml before the Extra-AC freeze date.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-6 (Final release for non-client libraries\; 2024.2 Elect
 ion Nomination Begins)
DTSTART;VALUE=DATE:20240219
DTEND;VALUE=DATE:20240224
DTSTAMP:20240110T112953Z
UID:Caracal-R-6
DESCRIPTION:Final release for non-client libraries\n\nLibraries that are n
 ot client libraries (Oslo and others) should issue their final release dur
 ing this week. That allows to give time for last-minute changes before fea
 ture freeze.\n\n\n\n2024.2 Election Nomination Begins\n\nCandidates intere
 sted in serving for the next calendar year (TC)\, or development cycle (PT
 L) should announce their candidacies and platforms during this week.  Plea
 se see the Election site for specific timing information.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-5 (Caracal-3 milestone\; Feature freeze\; Final release 
 for client libraries\; Soft StringFreeze\; Requirements freeze\; 2024.2 El
 ection Nomination Begins\; 2024.2 Election Email Deadline)
DTSTART;VALUE=DATE:20240226
DTEND;VALUE=DATE:20240302
DTSTAMP:20240110T112953Z
UID:Caracal-R-5
DESCRIPTION:Caracal-3 milestone\n\nFebruary 29\, 2024 is the Caracal-3 mil
 estone. See project-specific notes for relevant deadlines.\n\n\n\nFeature 
 freeze\n\nThe Caracal-3 milestone marks feature freeze for projects follow
 ing the release:cycle-with-rc model. No featureful patch should be landed 
 after this point. Exceptions may be granted by the project PTL.\n\n\n\n\n\
 nFinal release for client libraries\n\nClient libraries should issue their
  final release during this week\, to match feature freeze.\n\n\n\nSoft Str
 ingFreeze\n\nYou are no longer allowed to accept proposed changes containi
 ng modifications in user-facing strings. Such changes should be rejected b
 y the review team and postponed until the next series development opens (w
 hich should happen when RC1 is published).\n\n\n\nRequirements freeze\n\nA
 fter the Caracal-3 milestone\, only critical requirements and constraints 
 changes will be allowed. Freezing our requirements list gives packagers do
 wnstream an opportunity to catch up and prepare packages for everything ne
 cessary for distributions of the upcoming release. The requirements remain
  frozen until the stable branches are created\, with the release candidate
 s.\n\n\n\n2024.2 Election Nomination Begins\n\nCandidates interested in se
 rving for the next calendar year (TC)\, or development cycle (PTL) should 
 announce their candidacies and platforms during this week.  Please see the
  Election site for specific timing information.\n\n\n\n2024.2 Election Ema
 il Deadline\n\nContributors that will be in the electorate for the upcomin
 g election should confirm their gerrit email addresses by this date (Febru
 ary 28th\, 2024 at 00:00 UTC). Electorate rolls are generated after this d
 ate and ballots will be sent to the listed gerrit email address.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-4 (Cycle Highlights\; 2024.2 Election Campaigning Begins
 )
DTSTART;VALUE=DATE:20240304
DTEND;VALUE=DATE:20240309
DTSTAMP:20240110T112953Z
UID:Caracal-R-4
DESCRIPTION:Cycle Highlights\n\nCycle highlights need to be added to the r
 elease deliverables after the feature freeze to be included in any marketi
 ng release messaging. Highlights may be added after this point\, but they 
 will likely only be useful for historical purposes.\n\nSee the Project Tea
 m Guide for more details and instructions on adding these highlights.\n\nF
 or examples of previous release highlights: Stein Highlights\, Train Highl
 ights\, Ussuri Highlights\, Victoria Highlights\, Wallaby Highlights\, Xen
 a Highlights\, Yoga Highlights\, Zed Highlights.\n\n\n\n2024.2 Election Ca
 mpaigning Begins\n\nThe electorate has time to ask candidates questions ab
 out their platforms and debate topics before polling begins.  Please see t
 he Election site for specific timing information.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-3 (RC1 target week\; Hard StringFreeze\; 2024.2 Election
  Polling Begins)
DTSTART;VALUE=DATE:20240311
DTEND;VALUE=DATE:20240316
DTSTAMP:20240110T112953Z
UID:Caracal-R-3
DESCRIPTION:RC1 target week\n\nThe week of March 11\, 2024 is the target d
 ate for projects following the release:cycle-with-rc model to issue their 
 first release candidate.\n\n\n\nHard StringFreeze\n\nThis happens when the
  RC1 for the project is tagged. At this point\, ideally no strings are cha
 nged (or added\, or removed)\, to give translators time to finish up their
  efforts.\n\n\n\n2024.2 Election Polling Begins\n\nElection polling for op
 en seats on the TC and any required PTL elections. Please see the Election
  site for specific timing information.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-2 (2024.2 Election Polling Begins)
DTSTART;VALUE=DATE:20240318
DTEND;VALUE=DATE:20240323
DTSTAMP:20240110T112953Z
UID:Caracal-R-2
DESCRIPTION:2024.2 Election Polling Begins\n\nElection polling for open se
 ats on the TC and any required PTL elections. Please see the Election site
  for specific timing information.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R-1 (Final RCs and intermediary releases\; 2024.2 Election
  Polling Ends)
DTSTART;VALUE=DATE:20240325
DTEND;VALUE=DATE:20240330
DTSTAMP:20240110T112953Z
UID:Caracal-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of March 25\, 
 2024 is the last week to issue release candidates or intermediary releases
  before release week. During release week\, only final-release-critical re
 leases will be accepted (at the discretion of the release team).\n\n\n\n20
 24.2 Election Polling Ends\n\nAll polls close in the 2024.2 Election and r
 esults announced.  Please see the Election site for specific timing inform
 ation.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Caracal R+0 (Caracal release)
DTSTART;VALUE=DATE:20240401
DTEND;VALUE=DATE:20240406
DTSTAMP:20240110T112953Z
UID:Caracal-R+0
DESCRIPTION:Caracal release\n\nThe Caracal coordinated release will happen
  on Wednesday\, April 3\, 2024.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-25 (PTG (virtual))
DTSTART;VALUE=DATE:20240408
DTEND;VALUE=DATE:20240413
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-25
DESCRIPTION:PTG (virtual)\n\nFrom April 8 to April 12 we’ll have a virtu
 al PTG to plan the Dalmatian release schedule.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-24
DTSTART;VALUE=DATE:20240415
DTEND;VALUE=DATE:20240420
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-24
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-23
DTSTART;VALUE=DATE:20240422
DTEND;VALUE=DATE:20240427
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-23
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-22
DTSTART;VALUE=DATE:20240429
DTEND;VALUE=DATE:20240504
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-22
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-21
DTSTART;VALUE=DATE:20240506
DTEND;VALUE=DATE:20240511
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-21
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-20 (Dalmatian-1 milestone)
DTSTART;VALUE=DATE:20240513
DTEND;VALUE=DATE:20240518
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-20
DESCRIPTION:Dalmatian-1 milestone\n\nMay 16\, 2024 is the Dalmatian-1 mile
 stone. See project-specific notes for relevant deadlines.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-19
DTSTART;VALUE=DATE:20240520
DTEND;VALUE=DATE:20240525
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-19
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-18
DTSTART;VALUE=DATE:20240527
DTEND;VALUE=DATE:20240601
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-18
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-17 (2024.1 Caracal Cycle-Trailing Release Deadline)
DTSTART;VALUE=DATE:20240603
DTEND;VALUE=DATE:20240608
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-17
DESCRIPTION:2024.1 Caracal Cycle-Trailing Release Deadline\n\nAll projects
  following the cycle-trailing release model must release their 2024.1 Cara
 cal deliverables by June 6\, 2024.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-16
DTSTART;VALUE=DATE:20240610
DTEND;VALUE=DATE:20240615
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-16
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-15
DTSTART;VALUE=DATE:20240617
DTEND;VALUE=DATE:20240622
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-15
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-14
DTSTART;VALUE=DATE:20240624
DTEND;VALUE=DATE:20240629
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-14
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-13 (Dalmatian-2 milestone\; Membership Freeze)
DTSTART;VALUE=DATE:20240701
DTEND;VALUE=DATE:20240706
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-13
DESCRIPTION:Dalmatian-2 milestone\n\nJuly 4\, 2024 is the Dalmatian-2 mile
 stone. See project-specific notes for relevant deadlines.\n\n\n\nMembershi
 p Freeze\n\nProjects must participate in at least two milestones in order 
 to be considered part of the release. Projects made official after the sec
 ond milestone\, or which fail to produce milestone releases for at least o
 ne of the first and second milestones as well as the third milestone\, are
  therefore not considered part of the release for the cycle. This does not
  apply to cycle-trailing packaging / lifecycle management projects.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-12
DTSTART;VALUE=DATE:20240708
DTEND;VALUE=DATE:20240713
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-12
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-11
DTSTART;VALUE=DATE:20240715
DTEND;VALUE=DATE:20240720
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-11
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-10
DTSTART;VALUE=DATE:20240722
DTEND;VALUE=DATE:20240727
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-9
DTSTART;VALUE=DATE:20240729
DTEND;VALUE=DATE:20240803
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-9
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-8
DTSTART;VALUE=DATE:20240805
DTEND;VALUE=DATE:20240810
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-8
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-7 (Extra-AC freeze\; 2025.1 Election Nominations Open)
DTSTART;VALUE=DATE:20240812
DTEND;VALUE=DATE:20240817
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-7
DESCRIPTION:Extra-AC freeze\n\nAll contributions to OpenStack are valuable
 \, but some are not expressed as Gerrit code changes. That allow teams to 
 list active contributors to their projects and who do not have a code cont
 ribution this cycle\, and therefore won’t automatically be considered an
  Active Contributor and allowed to vote. This is done by adding extra-acs 
 to https://opendev.org/openstack/governance/src/branch/master/reference/pr
 ojects.yaml before the Extra-AC freeze date.\n\n\n\n2025.1 Election Nomina
 tions Open\n\nCandidates interested in serving for the next calendar year 
 (TC)\, or development cycle (PTL) should announce their candidacies and pl
 atforms during this two week window. The nomination period runs between 20
 24-08-14 23:45 UTC and 2024-08-28 23:45 UTC. Please see the Election site 
 for more information.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-6 (Final release for non-client libraries\; 2025.1 Ele
 ction Nominations Open)
DTSTART;VALUE=DATE:20240819
DTEND;VALUE=DATE:20240824
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-6
DESCRIPTION:Final release for non-client libraries\n\nLibraries that are n
 ot client libraries (Oslo and others) should issue their final release dur
 ing this week. That allows to give time for last-minute changes before fea
 ture freeze.\n\n\n\n2025.1 Election Nominations Open\n\nCandidates interes
 ted in serving for the next calendar year (TC)\, or development cycle (PTL
 ) should announce their candidacies and platforms during this two week win
 dow. The nomination period runs between 2024-08-14 23:45 UTC and 2024-08-2
 8 23:45 UTC. Please see the Election site for more information.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-5 (Dalmatian-3 milestone\; Feature freeze\; Final rele
 ase for client libraries\; Soft StringFreeze\; Requirements freeze\; 2025.
 1 Election Nominations Open\; 2025.1 Election Email Deadline\; 2025.1 Elec
 tion Campaigning Week)
DTSTART;VALUE=DATE:20240826
DTEND;VALUE=DATE:20240831
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-5
DESCRIPTION:Dalmatian-3 milestone\n\nAugust 29\, 2024 is the Dalmatian-3 m
 ilestone. See project-specific notes for relevant deadlines.\n\n\n\nFeatur
 e freeze\n\nThe Dalmatian-3 milestone marks feature freeze for projects fo
 llowing the release:cycle-with-rc model. No featureful patch should be lan
 ded after this point. Exceptions may be granted by the project PTL.\n\n\n\
 n\n\nFinal release for client libraries\n\nClient libraries should issue t
 heir final release during this week\, to match feature freeze.\n\n\n\nSoft
  StringFreeze\n\nYou are no longer allowed to accept proposed changes cont
 aining modifications in user-facing strings. Such changes should be reject
 ed by the review team and postponed until the next series development open
 s (which should happen when RC1 is published).\n\n\n\nRequirements freeze\
 n\nAfter the Dalmatian-3 milestone\, only critical requirements and constr
 aints changes will be allowed. Freezing our requirements list gives packag
 ers downstream an opportunity to catch up and prepare packages for everyth
 ing necessary for distributions of the upcoming release. The requirements 
 remain frozen until the stable branches are created\, with the release can
 didates.\n\n\n\n2025.1 Election Nominations Open\n\nCandidates interested 
 in serving for the next calendar year (TC)\, or development cycle (PTL) sh
 ould announce their candidacies and platforms during this two week window.
  The nomination period runs between 2024-08-14 23:45 UTC and 2024-08-28 23
 :45 UTC. Please see the Election site for more information.\n\n\n\n2025.1 
 Election Email Deadline\n\nContributors that will be in the electorate for
  the upcoming election should confirm their gerrit email addresses by 2024
 -08-28 00:00 UTC. Electorate rolls are generated after this date and ballo
 ts will be sent to the listed preferred gerrit email address.\n\n\n\n2025.
 1 Election Campaigning Week\n\nElection Campaigning window is between 2024
 -08-28 23:45 UTC and 2024-09-04 23:45 UTC. The electorate can use this tim
 e to ask candidates questions about their platforms and debate topics befo
 re polling begins. Please see the Election site for specific timing inform
 ation.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-4 (Cycle Highlights\; 2025.1 Election Campaigning Week
 \; 2025.1 Election Polling Open)
DTSTART;VALUE=DATE:20240902
DTEND;VALUE=DATE:20240907
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-4
DESCRIPTION:Cycle Highlights\n\nCycle highlights need to be added to the r
 elease deliverables after the feature freeze to be included in any marketi
 ng release messaging. Highlights may be added after this point\, but they 
 will likely only be useful for historical purposes.\n\nSee the Project Tea
 m Guide for more details and instructions on adding these highlights.\n\nF
 or examples of previous release highlights: Stein Highlights\, Train Highl
 ights\, Ussuri Highlights\, Victoria Highlights\, Wallaby Highlights\, Xen
 a Highlights\, Yoga Highlights\, Zed Highlights. 2023.1 Antelope Highlight
 s. 2023.2 Bobcat Highlights. 2024.1 Caracal Highlights.\n\n\n\n2025.1 Elec
 tion Campaigning Week\n\nElection Campaigning window is between 2024-08-28
  23:45 UTC and 2024-09-04 23:45 UTC. The electorate can use this time to a
 sk candidates questions about their platforms and debate topics before pol
 ling begins. Please see the Election site for specific timing information.
 \n\n\n\n2025.1 Election Polling Open\n\nElection polling for open seats on
  the TC and any required PTL elections begins at 2024-09-04 23:45 UTC. Ple
 ase see the Election site for more information.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-3 (RC1 target week\; Hard StringFreeze\; 2025.1 Electi
 on Polling Open)
DTSTART;VALUE=DATE:20240909
DTEND;VALUE=DATE:20240914
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-3
DESCRIPTION:RC1 target week\n\nThe week of September 9\, 2024 is the targe
 t date for projects following the release:cycle-with-rc model to issue the
 ir first release candidate.\n\n\n\nHard StringFreeze\n\nThis happens when 
 the RC1 for the project is tagged. At this point\, ideally no strings are 
 changed (or added\, or removed)\, to give translators time to finish up th
 eir efforts.\n\n\n\n2025.1 Election Polling Open\n\nElection polling for o
 pen seats on the TC and any required PTL elections begins at 2024-09-04 23
 :45 UTC. Please see the Election site for more information.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-2 (2025.1 Election Polling Open\; 2025.1 Election Poll
 ing End)
DTSTART;VALUE=DATE:20240916
DTEND;VALUE=DATE:20240921
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-2
DESCRIPTION:2025.1 Election Polling Open\n\nElection polling for open seat
 s on the TC and any required PTL elections begins at 2024-09-04 23:45 UTC.
  Please see the Election site for more information.\n\n\n\n2025.1 Election
  Polling End\n\nAll polls close in the 2025.1 Election at 2024-09-18 23:45
  UTC and results are announced. Please see the Election site for more info
 rmation.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R-1 (Final RCs and intermediary releases)
DTSTART;VALUE=DATE:20240923
DTEND;VALUE=DATE:20240928
DTSTAMP:20240614T153627Z
UID:Dalmatian-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of September 2
 3\, 2024 is the last week to issue release candidates or intermediary rele
 ases before release week. During release week\, only final-release-critica
 l releases will be accepted (at the discretion of the release team).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Dalmatian R+0 (Dalmatian release)
DTSTART;VALUE=DATE:20240930
DTEND;VALUE=DATE:20241005
DTSTAMP:20240614T153627Z
UID:Dalmatian-R+0
DESCRIPTION:Dalmatian release\n\nThe Dalmatian coordinated release will ha
 ppen on Wednesday\, October 2\, 2024.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-25
DTSTART;VALUE=DATE:20241007
DTEND;VALUE=DATE:20241012
DTSTAMP:20250219T153135Z
UID:Epoxy-R-25
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-24
DTSTART;VALUE=DATE:20241014
DTEND;VALUE=DATE:20241019
DTSTAMP:20250219T153135Z
UID:Epoxy-R-24
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-23 (PTG (virtual))
DTSTART;VALUE=DATE:20241021
DTEND;VALUE=DATE:20241026
DTSTAMP:20250219T153135Z
UID:Epoxy-R-23
DESCRIPTION:PTG (virtual)\n\nFrom October 21 to 25 we’ll have a virtual 
 PTG to plan the Epoxy release schedule.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-22
DTSTART;VALUE=DATE:20241028
DTEND;VALUE=DATE:20241102
DTSTAMP:20250219T153135Z
UID:Epoxy-R-22
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-21
DTSTART;VALUE=DATE:20241104
DTEND;VALUE=DATE:20241109
DTSTAMP:20250219T153135Z
UID:Epoxy-R-21
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-20 (Epoxy-1 milestone)
DTSTART;VALUE=DATE:20241111
DTEND;VALUE=DATE:20241116
DTSTAMP:20250219T153135Z
UID:Epoxy-R-20
DESCRIPTION:Epoxy-1 milestone\n\nNovember 14\, 2024 is the Epoxy-1 milesto
 ne. See project-specific notes for relevant deadlines.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-19
DTSTART;VALUE=DATE:20241118
DTEND;VALUE=DATE:20241123
DTSTAMP:20250219T153135Z
UID:Epoxy-R-19
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-18
DTSTART;VALUE=DATE:20241125
DTEND;VALUE=DATE:20241130
DTSTAMP:20250219T153135Z
UID:Epoxy-R-18
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-17 (2024.2 Dalmatian Cycle-Trailing Release Deadline)
DTSTART;VALUE=DATE:20241202
DTEND;VALUE=DATE:20241207
DTSTAMP:20250219T153135Z
UID:Epoxy-R-17
DESCRIPTION:2024.2 Dalmatian Cycle-Trailing Release Deadline\n\nAll projec
 ts following the cycle-trailing release model must release their 2024.2 Da
 lmatian deliverables by December 5\, 2024.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-16
DTSTART;VALUE=DATE:20241209
DTEND;VALUE=DATE:20241214
DTSTAMP:20250219T153135Z
UID:Epoxy-R-16
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-15
DTSTART;VALUE=DATE:20241216
DTEND;VALUE=DATE:20241221
DTSTAMP:20250219T153135Z
UID:Epoxy-R-15
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-14
DTSTART;VALUE=DATE:20241223
DTEND;VALUE=DATE:20241228
DTSTAMP:20250219T153135Z
UID:Epoxy-R-14
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-13
DTSTART;VALUE=DATE:20241230
DTEND;VALUE=DATE:20250104
DTSTAMP:20250219T153135Z
UID:Epoxy-R-13
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-12 (Epoxy-2 milestone\; Membership Freeze)
DTSTART;VALUE=DATE:20250106
DTEND;VALUE=DATE:20250111
DTSTAMP:20250219T153135Z
UID:Epoxy-R-12
DESCRIPTION:Epoxy-2 milestone\n\nJanuary 9\, 2025 is the Epoxy-2 milestone
 . See project-specific notes for relevant deadlines.\n\n\n\nMembership Fre
 eze\n\nProjects must participate in at least two milestones in order to be
  considered part of the release. Projects made official after the second m
 ilestone\, or which fail to produce milestone releases for at least one of
  the first and second milestones as well as the third milestone\, are ther
 efore not considered part of the release for the cycle. This does not appl
 y to cycle-trailing packaging / lifecycle management projects.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-11
DTSTART;VALUE=DATE:20250113
DTEND;VALUE=DATE:20250118
DTSTAMP:20250219T153135Z
UID:Epoxy-R-11
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-10
DTSTART;VALUE=DATE:20250120
DTEND;VALUE=DATE:20250125
DTSTAMP:20250219T153135Z
UID:Epoxy-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-9
DTSTART;VALUE=DATE:20250127
DTEND;VALUE=DATE:20250201
DTSTAMP:20250219T153135Z
UID:Epoxy-R-9
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-8
DTSTART;VALUE=DATE:20250203
DTEND;VALUE=DATE:20250208
DTSTAMP:20250219T153135Z
UID:Epoxy-R-8
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-7 (Extra-AC freeze\; 2025.2 Election Nomination Begins)
DTSTART;VALUE=DATE:20250210
DTEND;VALUE=DATE:20250215
DTSTAMP:20250219T153135Z
UID:Epoxy-R-7
DESCRIPTION:Extra-AC freeze\n\nAll contributions to OpenStack are valuable
 \, but some are not expressed as Gerrit code changes. That allow teams to 
 list active contributors to their projects and who do not have a code cont
 ribution this cycle\, and therefore won’t automatically be considered an
  Active Contributor and allowed to vote. This is done by adding extra-acs 
 to https://opendev.org/openstack/governance/src/branch/master/reference/pr
 ojects.yaml before the Extra-AC freeze date.\n\n\n\n2025.2 Election Nomina
 tion Begins\n\nCandidates interested in serving for the next calendar year
  (TC)\, or development cycle (PTL) should announce their candidacies and p
 latforms during this week.  Please see the Election site for specific timi
 ng information.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-6 (Final release for non-client libraries\; 2025.2 Electio
 n Nomination Begins)
DTSTART;VALUE=DATE:20250217
DTEND;VALUE=DATE:20250222
DTSTAMP:20250219T153135Z
UID:Epoxy-R-6
DESCRIPTION:Final release for non-client libraries\n\nLibraries that are n
 ot client libraries (Oslo and others) should issue their final release dur
 ing this week. That allows to give time for last-minute changes before fea
 ture freeze.\n\n\n\n2025.2 Election Nomination Begins\n\nCandidates intere
 sted in serving for the next calendar year (TC)\, or development cycle (PT
 L) should announce their candidacies and platforms during this week.  Plea
 se see the Election site for specific timing information.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-5 (Epoxy-3 milestone\; Feature freeze\; Final release for 
 client libraries\; Soft StringFreeze\; Requirements freeze\; 2025.2 Electi
 on Email Deadline\; 2025.2 Election Campaigning Begins)
DTSTART;VALUE=DATE:20250224
DTEND;VALUE=DATE:20250301
DTSTAMP:20250219T153135Z
UID:Epoxy-R-5
DESCRIPTION:Epoxy-3 milestone\n\nFebruary 27\, 2025 is the Epoxy-3 milesto
 ne. See project-specific notes for relevant deadlines.\n\n\n\nFeature free
 ze\n\nThe Epoxy-3 milestone marks feature freeze for projects following th
 e release:cycle-with-rc model. No featureful patch should be landed after 
 this point. Exceptions may be granted by the project PTL.\n\n\n\n\n\nFinal
  release for client libraries\n\nClient libraries should issue their final
  release during this week\, to match feature freeze.\n\n\n\nSoft StringFre
 eze\n\nYou are no longer allowed to accept proposed changes containing mod
 ifications in user-facing strings. Such changes should be rejected by the 
 review team and postponed until the next series development opens (which s
 hould happen when RC1 is published).\n\n\n\nRequirements freeze\n\nAfter t
 he Epoxy-3 milestone\, only critical requirements and constraints changes 
 will be allowed. Freezing our requirements list gives packagers downstream
  an opportunity to catch up and prepare packages for everything necessary 
 for distributions of the upcoming release. The requirements remain frozen 
 until the stable branches are created\, with the release candidates.\n\n\n
 \n2025.2 Election Email Deadline\n\nContributors that will be in the elect
 orate for the upcoming election should confirm their gerrit email addresse
 s by this date (February 19th\, 2025 at 00:00 UTC). Electorate rolls are g
 enerated after this date and ballots will be sent to the listed gerrit ema
 il address.\n\n\n\n2025.2 Election Campaigning Begins\n\nThe electorate ha
 s time to ask candidates questions about their platforms and debate topics
  before polling begins.  Please see the Election site for specific timing 
 information.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-4 (Cycle Highlights\; 2025.2 Election Polling Begins)
DTSTART;VALUE=DATE:20250303
DTEND;VALUE=DATE:20250308
DTSTAMP:20250219T153135Z
UID:Epoxy-R-4
DESCRIPTION:Cycle Highlights\n\nCycle highlights need to be added to the r
 elease deliverables after the feature freeze to be included in any marketi
 ng release messaging. Highlights may be added after this point\, but they 
 will likely only be useful for historical purposes.\n\nSee the Project Tea
 m Guide for more details and instructions on adding these highlights.\n\nF
 or examples of previous release highlights: Zed Highlights. 2023.1 Antelop
 e Highlights. 2023.2 Bobcat Highlights. 2024.1 Caracal Highlights.\n\n\n\n
 2025.2 Election Polling Begins\n\nElection polling for open seats on the T
 C and any required PTL elections. Please see the Election site for specifi
 c timing information.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-3 (RC1 target week\; Hard StringFreeze\; 2025.2 Election P
 olling Begins)
DTSTART;VALUE=DATE:20250310
DTEND;VALUE=DATE:20250315
DTSTAMP:20250219T153135Z
UID:Epoxy-R-3
DESCRIPTION:RC1 target week\n\nThe week of March 10\, 2025 is the target d
 ate for projects following the release:cycle-with-rc model to issue their 
 first release candidate.\n\n\n\nHard StringFreeze\n\nThis happens when the
  RC1 for the project is tagged. At this point\, ideally no strings are cha
 nged (or added\, or removed)\, to give translators time to finish up their
  efforts.\n\n\n\n2025.2 Election Polling Begins\n\nElection polling for op
 en seats on the TC and any required PTL elections. Please see the Election
  site for specific timing information.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-2 (2025.2 Election Polling Begins)
DTSTART;VALUE=DATE:20250317
DTEND;VALUE=DATE:20250322
DTSTAMP:20250219T153135Z
UID:Epoxy-R-2
DESCRIPTION:2025.2 Election Polling Begins\n\nElection polling for open se
 ats on the TC and any required PTL elections. Please see the Election site
  for specific timing information.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R-1 (Final RCs and intermediary releases\; 2025.2 Election P
 olling Ends)
DTSTART;VALUE=DATE:20250324
DTEND;VALUE=DATE:20250329
DTSTAMP:20250219T153135Z
UID:Epoxy-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of March 24\, 
 2025 is the last week to issue release candidates or intermediary releases
  before release week. During release week\, only final-release-critical re
 leases will be accepted (at the discretion of the release team).\n\n\n\n20
 25.2 Election Polling Ends\n\nAll polls close in the 2025.2 Election and r
 esults announced.  Please see the Election site for specific timing inform
 ation.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Epoxy R+0 (Epoxy release)
DTSTART;VALUE=DATE:20250331
DTEND;VALUE=DATE:20250405
DTSTAMP:20250219T153135Z
UID:Epoxy-R+0
DESCRIPTION:Epoxy release\n\nThe Epoxy coordinated release will happen on 
 Wednesday\, April 2\, 2025.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-25 (PTG (virtual))
DTSTART;VALUE=DATE:20250407
DTEND;VALUE=DATE:20250412
DTSTAMP:20250219T153135Z
UID:Flamingo-R-25
DESCRIPTION:PTG (virtual)\n\nFrom April 7 to 11\, 2025 we’ll have a virt
 ual PTG to plan the 2025.2 Flamingo release schedule.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-24
DTSTART;VALUE=DATE:20250414
DTEND;VALUE=DATE:20250419
DTSTAMP:20250219T153135Z
UID:Flamingo-R-24
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-23
DTSTART;VALUE=DATE:20250421
DTEND;VALUE=DATE:20250426
DTSTAMP:20250219T153135Z
UID:Flamingo-R-23
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-22
DTSTART;VALUE=DATE:20250428
DTEND;VALUE=DATE:20250503
DTSTAMP:20250219T153135Z
UID:Flamingo-R-22
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-21
DTSTART;VALUE=DATE:20250505
DTEND;VALUE=DATE:20250510
DTSTAMP:20250219T153135Z
UID:Flamingo-R-21
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-20 (Flamingo-1 milestone)
DTSTART;VALUE=DATE:20250512
DTEND;VALUE=DATE:20250517
DTSTAMP:20250219T153135Z
UID:Flamingo-R-20
DESCRIPTION:Flamingo-1 milestone\n\nMay 15\, 2025 is the Flamingo-1 milest
 one. See project-specific notes for relevant deadlines.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-19
DTSTART;VALUE=DATE:20250519
DTEND;VALUE=DATE:20250524
DTSTAMP:20250219T153135Z
UID:Flamingo-R-19
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-18
DTSTART;VALUE=DATE:20250526
DTEND;VALUE=DATE:20250531
DTSTAMP:20250219T153135Z
UID:Flamingo-R-18
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-17 (2025.1 Epoxy Cycle-Trailing Release Deadline)
DTSTART;VALUE=DATE:20250602
DTEND;VALUE=DATE:20250607
DTSTAMP:20250219T153135Z
UID:Flamingo-R-17
DESCRIPTION:2025.1 Epoxy Cycle-Trailing Release Deadline\n\nAll projects f
 ollowing the cycle-trailing release model must release their 2025.1 Epoxy 
 deliverables by June 5\, 2025.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-16
DTSTART;VALUE=DATE:20250609
DTEND;VALUE=DATE:20250614
DTSTAMP:20250219T153135Z
UID:Flamingo-R-16
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-15
DTSTART;VALUE=DATE:20250616
DTEND;VALUE=DATE:20250621
DTSTAMP:20250219T153135Z
UID:Flamingo-R-15
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-14
DTSTART;VALUE=DATE:20250623
DTEND;VALUE=DATE:20250628
DTSTAMP:20250219T153135Z
UID:Flamingo-R-14
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-13 (Flamingo-2 milestone)
DTSTART;VALUE=DATE:20250630
DTEND;VALUE=DATE:20250705
DTSTAMP:20250219T153135Z
UID:Flamingo-R-13
DESCRIPTION:Flamingo-2 milestone\n\nJuly 3\, 2025 is the Flamingo-2 milest
 one. See project-specific notes for relevant deadlines.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-12
DTSTART;VALUE=DATE:20250707
DTEND;VALUE=DATE:20250712
DTSTAMP:20250219T153135Z
UID:Flamingo-R-12
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-11
DTSTART;VALUE=DATE:20250714
DTEND;VALUE=DATE:20250719
DTSTAMP:20250219T153135Z
UID:Flamingo-R-11
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-10
DTSTART;VALUE=DATE:20250721
DTEND;VALUE=DATE:20250726
DTSTAMP:20250219T153135Z
UID:Flamingo-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-9
DTSTART;VALUE=DATE:20250728
DTEND;VALUE=DATE:20250802
DTSTAMP:20250219T153135Z
UID:Flamingo-R-9
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-8
DTSTART;VALUE=DATE:20250804
DTEND;VALUE=DATE:20250809
DTSTAMP:20250219T153135Z
UID:Flamingo-R-8
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-7 (Extra-AC freeze)
DTSTART;VALUE=DATE:20250811
DTEND;VALUE=DATE:20250816
DTSTAMP:20250219T153135Z
UID:Flamingo-R-7
DESCRIPTION:Extra-AC freeze\n\nAll contributions to OpenStack are valuable
 \, but some are not expressed as Gerrit code changes. That allow teams to 
 list active contributors to their projects and who do not have a code cont
 ribution this cycle\, and therefore won’t automatically be considered an
  Active Contributor and allowed to vote. This is done by adding extra-acs 
 to https://opendev.org/openstack/governance/src/branch/master/reference/pr
 ojects.yaml before the Extra-AC freeze date.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-6 (Final release for non-client libraries)
DTSTART;VALUE=DATE:20250818
DTEND;VALUE=DATE:20250823
DTSTAMP:20250219T153135Z
UID:Flamingo-R-6
DESCRIPTION:Final release for non-client libraries\n\nLibraries that are n
 ot client libraries (Oslo and others) should issue their final release dur
 ing this week. That allows to give time for last-minute changes before fea
 ture freeze.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-5 (Flamingo-3 milestone\; Feature freeze\; Final releas
 e for client libraries\; Soft StringFreeze\; Requirements freeze)
DTSTART;VALUE=DATE:20250825
DTEND;VALUE=DATE:20250830
DTSTAMP:20250219T153135Z
UID:Flamingo-R-5
DESCRIPTION:Flamingo-3 milestone\n\nAugust 28\, 2025 is the Flamingo-3 mil
 estone. See project-specific notes for relevant deadlines.\n\n\n\nFeature 
 freeze\n\nThe Flamingo-3 milestone marks feature freeze for projects follo
 wing the release:cycle-with-rc model. No featureful patch should be landed
  after this point. Exceptions may be granted by the project PTL.\n\n\n\n\n
 \nFinal release for client libraries\n\nClient libraries should issue thei
 r final release during this week\, to match feature freeze.\n\n\n\nSoft St
 ringFreeze\n\nYou are no longer allowed to accept proposed changes contain
 ing modifications in user-facing strings. Such changes should be rejected 
 by the review team and postponed until the next series development opens (
 which should happen when RC1 is published).\n\n\n\nRequirements freeze\n\n
 After the Flamingo-3 milestone\, only critical requirements and constraint
 s changes will be allowed. Freezing our requirements list gives packagers 
 downstream an opportunity to catch up and prepare packages for everything 
 necessary for distributions of the upcoming release. The requirements rema
 in frozen until the stable branches are created\, with the release candida
 tes.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-4 (Cycle Highlights)
DTSTART;VALUE=DATE:20250901
DTEND;VALUE=DATE:20250906
DTSTAMP:20250219T153135Z
UID:Flamingo-R-4
DESCRIPTION:Cycle Highlights\n\nCycle highlights need to be added to the r
 elease deliverables after the feature freeze to be included in any marketi
 ng release messaging. Highlights may be added after this point\, but they 
 will likely only be useful for historical purposes.\n\nSee the Project Tea
 m Guide for more details and instructions on adding these highlights.\n\nF
 or examples of previous release highlights: 2024.1 Caracal Highlights. 202
 4.2 Dalmatian Highlights.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-3 (RC1 target week\; Hard StringFreeze)
DTSTART;VALUE=DATE:20250908
DTEND;VALUE=DATE:20250913
DTSTAMP:20250219T153135Z
UID:Flamingo-R-3
DESCRIPTION:RC1 target week\n\nThe week of September 8\, 2025 is the targe
 t date for projects following the release:cycle-with-rc model to issue the
 ir first release candidate.\n\n\n\nHard StringFreeze\n\nThis happens when 
 the RC1 for the project is tagged. At this point\, ideally no strings are 
 changed (or added\, or removed)\, to give translators time to finish up th
 eir efforts.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-2
DTSTART;VALUE=DATE:20250915
DTEND;VALUE=DATE:20250920
DTSTAMP:20250219T153135Z
UID:Flamingo-R-2
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R-1 (Final RCs and intermediary releases)
DTSTART;VALUE=DATE:20250922
DTEND;VALUE=DATE:20250927
DTSTAMP:20250219T153135Z
UID:Flamingo-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of September 2
 2\, 2025 is the last week to issue release candidates or intermediary rele
 ases before release week. During release week\, only final-release-critica
 l releases will be accepted (at the discretion of the release team).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Flamingo R+0 (2025.2 Flamingo release)
DTSTART;VALUE=DATE:20250929
DTEND;VALUE=DATE:20251004
DTSTAMP:20250219T153135Z
UID:Flamingo-R+0
DESCRIPTION:2025.2 Flamingo release\n\nThe 2025.2 Flamingo coordinated rel
 ease will happen on Wednesday\, October 1\, 2025.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-15
DTSTART;VALUE=DATE:20161107
DTEND;VALUE=DATE:20161112
DTSTAMP:20170104T100241Z
UID:Ocata-R-15
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-14 (Ocata-1 milestone\; Ocata Community Goals Acknowledgem
 ent)
DTSTART;VALUE=DATE:20161114
DTEND;VALUE=DATE:20161119
DTSTAMP:20170104T100241Z
UID:Ocata-R-14
DESCRIPTION:Ocata-1 milestone\n\n17 November is the ocata-1 milestone wind
 ow for projects following the cycle-with-milestones model.\n\n\n\nOcata Co
 mmunity Goals Acknowledgement\n\nTeams should prepare their acknowledgemen
 t of the community-wide goals for Ocata.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-13
DTSTART;VALUE=DATE:20161121
DTEND;VALUE=DATE:20161126
DTSTAMP:20170104T100241Z
UID:Ocata-R-13
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-12
DTSTART;VALUE=DATE:20161128
DTEND;VALUE=DATE:20161203
DTSTAMP:20170104T100241Z
UID:Ocata-R-12
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-11 (Ocata-2 milestone\; Membership Freeze)
DTSTART;VALUE=DATE:20161205
DTEND;VALUE=DATE:20161210
DTSTAMP:20170104T100241Z
UID:Ocata-R-11
DESCRIPTION:Ocata-2 milestone\n\n15 December is the ocata-2 milestone wind
 ow for projects following the cycle-with-milestones model.\n\n\n\nMembersh
 ip Freeze\n\nProjects must participate in at least two milestones in order
  to be considered part of the release. Projects made official after the se
 cond milestone\, or which fail to produce milestone releases for at least 
 one of the first and second milestones as well as the third milestone\, ar
 e therefore not considered part of the release for the cycle.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-10
DTSTART;VALUE=DATE:20161212
DTEND;VALUE=DATE:20161217
DTSTAMP:20170104T100241Z
UID:Ocata-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-9
DTSTART;VALUE=DATE:20161219
DTEND;VALUE=DATE:20161224
DTSTAMP:20170104T100241Z
UID:Ocata-R-9
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-8
DTSTART;VALUE=DATE:20161226
DTEND;VALUE=DATE:20161231
DTSTAMP:20170104T100241Z
UID:Ocata-R-8
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-7 (Extra-ATCs deadline)
DTSTART;VALUE=DATE:20170102
DTEND;VALUE=DATE:20170107
DTSTAMP:20170104T100241Z
UID:Ocata-R-7
DESCRIPTION:Extra-ATCs deadline\n\nProject teams should identify contribut
 ors who have had a significant impact this cycle but who would not qualify
  for ATC status using the regular process because they have not submitted 
 a patch. Those names should be added to the governance repo for considerat
 ion as ATC for the future.\n\nAlthough extra ATCs can be nominated at any 
 point\, there is a deadline to be included in electorate for the next rele
 ase cycle.  The ATC list needs to be approved by the TC by (TBD)\, and in 
 order to appear on the TC agenda to be discussed\, the proposals need to b
 e submitted to the openstack/governance repository by (TBD).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-6
DTSTART;VALUE=DATE:20170109
DTEND;VALUE=DATE:20170114
DTSTAMP:20170104T100241Z
UID:Ocata-R-6
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-5 (Final release for non-client libraries)
DTSTART;VALUE=DATE:20170116
DTEND;VALUE=DATE:20170121
DTSTAMP:20170104T100241Z
UID:Ocata-R-5
DESCRIPTION:Final release for non-client libraries\n\nLibraries that are n
 ot client libraries (Oslo and others) should issue their final release dur
 ing this week. That allows to give time for last-minute changes before fea
 ture freeze.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-4 (Ocata-3 milestone\; Feature freeze\; Final release for 
 client libraries\; Soft StringFreeze\; Requirements freeze\; Ocata Communi
 ty Goals Completed)
DTSTART;VALUE=DATE:20170123
DTEND;VALUE=DATE:20170128
DTSTAMP:20170104T100241Z
UID:Ocata-R-4
DESCRIPTION:Ocata-3 milestone\n\n26 January is the ocata-3 milestone windo
 w for projects following the cycle-with-milestones model.\n\n\n\nFeature f
 reeze\n\nThe ocata-3 milestone marks feature freeze for projects following
  the cycle-with-milestones model. No featureful patch should be landed aft
 er this point. Exceptions may be granted by the project PTL.\n\n\n\nFinal 
 release for client libraries\n\nClient libraries should issue their final 
 release during this week\, to match feature freeze.\n\n\n\nSoft StringFree
 ze\n\nYou are no longer allowed to accept proposed changes containing modi
 fications in user-facing strings. Such changes should be rejected by the r
 eview team and postponed until the next series development opens (which sh
 ould happen when RC1 is published).\n\n\n\nRequirements freeze\n\nAfter th
 e ocata-3 milestone\, only critical requirements and constraints changes w
 ill be allowed. Freezing our requirements list gives packagers downstream 
 an opportunity to catch up and prepare packages for everything necessary f
 or distributions of the upcoming release. The requirements remain frozen u
 ntil the stable branches are created\, with the release candidates.\n\n\n\
 nOcata Community Goals Completed\n\nTeams should prepare their documentati
 on for completing the community-wide goals for Ocata.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-3 (RC1 target week\; Hard StringFreeze)
DTSTART;VALUE=DATE:20170130
DTEND;VALUE=DATE:20170204
DTSTAMP:20170104T100241Z
UID:Ocata-R-3
DESCRIPTION:RC1 target week\n\nThe week of 30 January - 3 February is the 
 target date for projects following the cycle-with-milestones model to issu
 e their first release candidate\, with a deadline of 2 February.\n\n\n\nHa
 rd StringFreeze\n\nThis happens when the RC1 for the project is tagged. At
  this point\, ideally no strings are changed (or added\, or removed)\, to 
 give translator time to finish up their efforts.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-2
DTSTART;VALUE=DATE:20170206
DTEND;VALUE=DATE:20170211
DTSTAMP:20170104T100241Z
UID:Ocata-R-2
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-1 (Final RCs and intermediary releases)
DTSTART;VALUE=DATE:20170213
DTEND;VALUE=DATE:20170218
DTSTAMP:20170104T100241Z
UID:Ocata-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of 13-17 Febru
 ary is the last week to issue release candidates or intermediary releases 
 before release week. During release week\, only final-release-critical rel
 eases will be accepted (at the discretion of the release team).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R+0 (Ocata release\; Pike Project Team Gathering (PTG))
DTSTART;VALUE=DATE:20170220
DTEND;VALUE=DATE:20170225
DTSTAMP:20170104T100241Z
UID:Ocata-R+0
DESCRIPTION:Ocata release\n\nThe Ocata coordinated release will happen on 
 22 February.\n\n\n\nPike Project Team Gathering (PTG)\n\nProject team gath
 ering for the Pike release 20-24 February 2017 in Atlanta\, Georgia.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R+1
DTSTART;VALUE=DATE:20170227
DTEND;VALUE=DATE:20170304
DTSTAMP:20170104T100241Z
UID:Ocata-R+1
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R+2 (Ocata cycle-trailing Deadline)
DTSTART;VALUE=DATE:20170306
DTEND;VALUE=DATE:20170311
DTSTAMP:20170104T100241Z
UID:Ocata-R+2
DESCRIPTION:Ocata cycle-trailing Deadline\n\nThe deadline for projects usi
 ng the release:cycle-trailing model that follow the main release cycle is 
 9 March.
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-26
DTSTART;VALUE=DATE:20170227
DTEND;VALUE=DATE:20170304
DTSTAMP:20170711T104638Z
UID:Pike-R-26
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-25
DTSTART;VALUE=DATE:20170306
DTEND;VALUE=DATE:20170311
DTSTAMP:20170711T104638Z
UID:Pike-R-25
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-24
DTSTART;VALUE=DATE:20170313
DTEND;VALUE=DATE:20170318
DTSTAMP:20170711T104638Z
UID:Pike-R-24
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-23
DTSTART;VALUE=DATE:20170320
DTEND;VALUE=DATE:20170325
DTSTAMP:20170711T104638Z
UID:Pike-R-23
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-22
DTSTART;VALUE=DATE:20170327
DTEND;VALUE=DATE:20170401
DTSTAMP:20170711T104638Z
UID:Pike-R-22
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-21
DTSTART;VALUE=DATE:20170403
DTEND;VALUE=DATE:20170408
DTSTAMP:20170711T104638Z
UID:Pike-R-21
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-20 (Pike-1 milestone)
DTSTART;VALUE=DATE:20170410
DTEND;VALUE=DATE:20170415
DTSTAMP:20170711T104638Z
UID:Pike-R-20
DESCRIPTION:Pike-1 milestone\n\n13 April 2017 is the Pike-1 milestone wind
 ow for projects following the release:cycle-with-milestones model.\n\n\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-19
DTSTART;VALUE=DATE:20170417
DTEND;VALUE=DATE:20170422
DTSTAMP:20170711T104638Z
UID:Pike-R-19
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-18
DTSTART;VALUE=DATE:20170424
DTEND;VALUE=DATE:20170429
DTSTAMP:20170711T104638Z
UID:Pike-R-18
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-17
DTSTART;VALUE=DATE:20170501
DTEND;VALUE=DATE:20170506
DTSTAMP:20170711T104638Z
UID:Pike-R-17
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-16 (OpenStack Summit)
DTSTART;VALUE=DATE:20170508
DTEND;VALUE=DATE:20170513
DTSTAMP:20170711T104638Z
UID:Pike-R-16
DESCRIPTION:OpenStack Summit\n\nThe OpenStack Summit happens during this w
 eek in Boston\, USA. It will include a “Forum” in which people from al
 l parts of our community will gather to give feedback on the last release 
 (Ocata) and discuss requirements for the next development cycle (Queens).\
 n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-15
DTSTART;VALUE=DATE:20170515
DTEND;VALUE=DATE:20170520
DTSTAMP:20170711T104638Z
UID:Pike-R-15
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-14
DTSTART;VALUE=DATE:20170522
DTEND;VALUE=DATE:20170527
DTSTAMP:20170711T104638Z
UID:Pike-R-14
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-13
DTSTART;VALUE=DATE:20170529
DTEND;VALUE=DATE:20170603
DTSTAMP:20170711T104638Z
UID:Pike-R-13
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-12 (Pike-2 milestone\; Membership Freeze)
DTSTART;VALUE=DATE:20170605
DTEND;VALUE=DATE:20170610
DTSTAMP:20170711T104638Z
UID:Pike-R-12
DESCRIPTION:Pike-2 milestone\n\n8 June 2017 is the Pike-2 milestone window
  for projects following the release:cycle-with-milestones model.\n\n\n\nMe
 mbership Freeze\n\nProjects must participate in at least two milestones in
  order to be considered part of the release. Projects made official after 
 the second milestone\, or which fail to produce milestone releases for at 
 least one of the first and second milestones as well as the third mileston
 e\, are therefore not considered part of the release for the cycle.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-11
DTSTART;VALUE=DATE:20170612
DTEND;VALUE=DATE:20170617
DTSTAMP:20170711T104638Z
UID:Pike-R-11
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-10
DTSTART;VALUE=DATE:20170619
DTEND;VALUE=DATE:20170624
DTSTAMP:20170711T104638Z
UID:Pike-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-9
DTSTART;VALUE=DATE:20170626
DTEND;VALUE=DATE:20170701
DTSTAMP:20170711T104638Z
UID:Pike-R-9
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-8
DTSTART;VALUE=DATE:20170703
DTEND;VALUE=DATE:20170708
DTSTAMP:20170711T104638Z
UID:Pike-R-8
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-7 (Extra-ATCs deadline)
DTSTART;VALUE=DATE:20170710
DTEND;VALUE=DATE:20170715
DTSTAMP:20170711T104638Z
UID:Pike-R-7
DESCRIPTION:Extra-ATCs deadline\n\nProject teams should identify contribut
 ors who have had a significant impact this cycle but who would not qualify
  for ATC status using the regular process because they have not submitted 
 a patch. Those names should be added to the governance repo for considerat
 ion as ATC for the future.\n\nAlthough extra ATCs can be nominated at any 
 point\, there is a deadline to be included in electorate for the next rele
 ase cycle.  The ATC list needs to be approved by the TC by (TBD)\, and in 
 order to appear on the TC agenda to be discussed\, the proposals need to b
 e submitted to the openstack/governance repository by (TBD).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-6 (Final release for non-client libraries)
DTSTART;VALUE=DATE:20170717
DTEND;VALUE=DATE:20170722
DTSTAMP:20170711T104638Z
UID:Pike-R-6
DESCRIPTION:Final release for non-client libraries\n\nLibraries that are n
 ot client libraries (Oslo and others) should issue their final release dur
 ing this week. That allows to give time for last-minute changes before fea
 ture freeze.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-5 (Pike-3 milestone\; Feature freeze\; Final release for cl
 ient libraries\; Soft StringFreeze\; Requirements freeze\; Pike Community 
 Goals Completed)
DTSTART;VALUE=DATE:20170724
DTEND;VALUE=DATE:20170729
DTSTAMP:20170711T104638Z
UID:Pike-R-5
DESCRIPTION:Pike-3 milestone\n\n27 July 2017 is the Pike-3 milestone windo
 w for projects following the release:cycle-with-milestones model.\n\n\n\nF
 eature freeze\n\nThe Pike-3 milestone marks feature freeze for projects fo
 llowing the release:cycle-with-milestones model. No featureful patch shoul
 d be landed after this point. Exceptions may be granted by the project PTL
 .\n\n\n\nFinal release for client libraries\n\nClient libraries should iss
 ue their final release during this week\, to match feature freeze.\n\n\n\n
 Soft StringFreeze\n\nYou are no longer allowed to accept proposed changes 
 containing modifications in user-facing strings. Such changes should be re
 jected by the review team and postponed until the next series development 
 opens (which should happen when RC1 is published).\n\n\n\nRequirements fre
 eze\n\nAfter the Pike-3 milestone\, only critical requirements and constra
 ints changes will be allowed. Freezing our requirements list gives package
 rs downstream an opportunity to catch up and prepare packages for everythi
 ng necessary for distributions of the upcoming release. The requirements r
 emain frozen until the stable branches are created\, with the release cand
 idates.\n\n\n\nPike Community Goals Completed\n\nTeams should prepare thei
 r documentation for completing the community-wide goals for Pike.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-4
DTSTART;VALUE=DATE:20170731
DTEND;VALUE=DATE:20170805
DTSTAMP:20170711T104638Z
UID:Pike-R-4
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-3 (RC1 target week\; Hard StringFreeze\; Pike cycle-trailin
 g feature freeze)
DTSTART;VALUE=DATE:20170807
DTEND;VALUE=DATE:20170812
DTSTAMP:20170711T104638Z
UID:Pike-R-3
DESCRIPTION:RC1 target week\n\nThe week of 7-11 August 2017 is the target 
 date for projects following the release:cycle-with-milestones model to iss
 ue their first release candidate\, with a deadline of 10 August 2017.\n\n\
 n\nHard StringFreeze\n\nThis happens when the RC1 for the project is tagge
 d. At this point\, ideally no strings are changed (or added\, or removed)\
 , to give translator time to finish up their efforts.\n\n\n\nPike cycle-tr
 ailing feature freeze\n\nThe release deadline for projects using the relea
 se:cycle-trailing model that follow the main release cycle.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-2
DTSTART;VALUE=DATE:20170814
DTEND;VALUE=DATE:20170819
DTSTAMP:20170711T104638Z
UID:Pike-R-2
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-1 (Final RCs and intermediary releases)
DTSTART;VALUE=DATE:20170821
DTEND;VALUE=DATE:20170826
DTSTAMP:20170711T104638Z
UID:Pike-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of 21 August 2
 017 is the last week to issue release candidates or intermediary releases 
 before release week. During release week\, only final-release-critical rel
 eases will be accepted (at the discretion of the release team).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R+0 (Pike release\; Pike cycle-trailing RC deadline)
DTSTART;VALUE=DATE:20170828
DTEND;VALUE=DATE:20170902
DTSTAMP:20170711T104638Z
UID:Pike-R+0
DESCRIPTION:Pike release\n\nThe Pike coordinated release will happen on 30
  August 2017.\n\n\n\nPike cycle-trailing RC deadline\n\nThe deadline for p
 ublishing a first release candidate for projects using the release:cycle-t
 railing model that follow the main release cycle.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R+1
DTSTART;VALUE=DATE:20170904
DTEND;VALUE=DATE:20170909
DTSTAMP:20170711T104638Z
UID:Pike-R+1
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R+2 (Pike cycle-trailing release deadline)
DTSTART;VALUE=DATE:20170911
DTEND;VALUE=DATE:20170916
DTSTAMP:20170711T104638Z
UID:Pike-R+2
DESCRIPTION:Pike cycle-trailing release deadline\n\nThe release deadline f
 or projects using the release:cycle-trailing model that follow the main re
 lease cycle.
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-25
DTSTART;VALUE=DATE:20170904
DTEND;VALUE=DATE:20170909
DTSTAMP:20180312T172305Z
UID:Queens-R-25
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-24 (Queens Project Team Gathering (PTG)\; Queens Goals Re
 search)
DTSTART;VALUE=DATE:20170911
DTEND;VALUE=DATE:20170916
DTSTAMP:20180312T172305Z
UID:Queens-R-24
DESCRIPTION:Queens Project Team Gathering (PTG)\n\nProject team gathering 
 for the Queens cycle 11-15 September 2018 in Denver\, Colorado.\n\n\n\nQue
 ens Goals Research\n\nPre-cycle planning and investigation into the commun
 ity-wide goals for Queens.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-23
DTSTART;VALUE=DATE:20170918
DTEND;VALUE=DATE:20170923
DTSTAMP:20180312T172305Z
UID:Queens-R-23
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-22 (Newton library releases)
DTSTART;VALUE=DATE:20170925
DTEND;VALUE=DATE:20170930
DTSTAMP:20180312T172305Z
UID:Queens-R-22
DESCRIPTION:Newton library releases\n\nLast week for libraries to be relea
 sed\, integrated in upper-constraints to be tested before Newton EOL.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-21
DTSTART;VALUE=DATE:20171002
DTEND;VALUE=DATE:20171007
DTSTAMP:20180312T172305Z
UID:Queens-R-21
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-20 (Newton EOL)
DTSTART;VALUE=DATE:20171009
DTEND;VALUE=DATE:20171014
DTSTAMP:20180312T172305Z
UID:Queens-R-20
DESCRIPTION:Newton EOL\n\nNewton projects will be EOL’d this week.
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-19 (Queens-1 milestone)
DTSTART;VALUE=DATE:20171016
DTEND;VALUE=DATE:20171021
DTSTAMP:20180312T172305Z
UID:Queens-R-19
DESCRIPTION:Queens-1 milestone\n\n19 October 2017 is the Queens-1 mileston
 e window for projects following the release:cycle-with-milestones model.\n
 \n\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-18
DTSTART;VALUE=DATE:20171023
DTEND;VALUE=DATE:20171028
DTSTAMP:20180312T172305Z
UID:Queens-R-18
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-17
DTSTART;VALUE=DATE:20171030
DTEND;VALUE=DATE:20171104
DTSTAMP:20180312T172305Z
UID:Queens-R-17
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-16 (OpenStack Summit)
DTSTART;VALUE=DATE:20171106
DTEND;VALUE=DATE:20171111
DTSTAMP:20180312T172305Z
UID:Queens-R-16
DESCRIPTION:OpenStack Summit\n\nThe OpenStack Summit happens during this w
 eek in Sydney\, Australia. It will include a “Forum” in which people f
 rom all parts of our community will gather to give feedback on the last re
 lease (Pike) and discuss requirements for the next development cycle (Rock
 y).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-15
DTSTART;VALUE=DATE:20171113
DTEND;VALUE=DATE:20171118
DTSTAMP:20180312T172305Z
UID:Queens-R-15
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-14
DTSTART;VALUE=DATE:20171120
DTEND;VALUE=DATE:20171125
DTSTAMP:20180312T172305Z
UID:Queens-R-14
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-13
DTSTART;VALUE=DATE:20171127
DTEND;VALUE=DATE:20171202
DTSTAMP:20180312T172305Z
UID:Queens-R-13
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-12 (Queens-2 milestone\; Membership Freeze)
DTSTART;VALUE=DATE:20171204
DTEND;VALUE=DATE:20171209
DTSTAMP:20180312T172305Z
UID:Queens-R-12
DESCRIPTION:Queens-2 milestone\n\n7 December 2017 is the Queens-2 mileston
 e window for projects following the release:cycle-with-milestones model.\n
 \n\n\nMembership Freeze\n\nProjects must participate in at least two miles
 tones in order to be considered part of the release. Projects made officia
 l after the second milestone\, or which fail to produce milestone releases
  for at least one of the first and second milestones as well as the third 
 milestone\, are therefore not considered part of the release for the cycle
 . This does not apply to cycle-trailing packaging / lifecycle management p
 rojects.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-11
DTSTART;VALUE=DATE:20171211
DTEND;VALUE=DATE:20171216
DTSTAMP:20180312T172305Z
UID:Queens-R-11
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-10
DTSTART;VALUE=DATE:20171218
DTEND;VALUE=DATE:20171223
DTSTAMP:20180312T172305Z
UID:Queens-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-9
DTSTART;VALUE=DATE:20171225
DTEND;VALUE=DATE:20171230
DTSTAMP:20180312T172305Z
UID:Queens-R-9
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-8
DTSTART;VALUE=DATE:20180101
DTEND;VALUE=DATE:20180106
DTSTAMP:20180312T172305Z
UID:Queens-R-8
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-7 (Extra-ATCs deadline)
DTSTART;VALUE=DATE:20180108
DTEND;VALUE=DATE:20180113
DTSTAMP:20180312T172305Z
UID:Queens-R-7
DESCRIPTION:Extra-ATCs deadline\n\nProject teams should identify contribut
 ors who have had a significant impact this cycle but who would not qualify
  for ATC status using the regular process because they have not submitted 
 a patch. Those names should be added to the governance repo for considerat
 ion as ATC for the future.\n\nAlthough extra ATCs can be nominated at any 
 point\, there is a deadline to be included in electorate for the next rele
 ase cycle.  The ATC list needs to be approved by the TC by (TBD)\, and in 
 order to appear on the TC agenda to be discussed\, the proposals need to b
 e submitted to the openstack/governance repository by (TBD).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-6 (Final release for non-client libraries)
DTSTART;VALUE=DATE:20180115
DTEND;VALUE=DATE:20180120
DTSTAMP:20180312T172305Z
UID:Queens-R-6
DESCRIPTION:Final release for non-client libraries\n\nLibraries that are n
 ot client libraries (Oslo and others) should issue their final release dur
 ing this week. That allows to give time for last-minute changes before fea
 ture freeze.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-5 (Queens-3 milestone\; Feature freeze\; Final release fo
 r client libraries\; Soft StringFreeze\; Requirements freeze\; Queens Comm
 unity Goals Completed)
DTSTART;VALUE=DATE:20180122
DTEND;VALUE=DATE:20180127
DTSTAMP:20180312T172305Z
UID:Queens-R-5
DESCRIPTION:Queens-3 milestone\n\n25 January 2018 is the Queens-3 mileston
 e window for projects following the release:cycle-with-milestones model.\n
 \n\n\nFeature freeze\n\nThe Queens-3 milestone marks feature freeze for pr
 ojects following the release:cycle-with-milestones model. No featureful pa
 tch should be landed after this point. Exceptions may be granted by the pr
 oject PTL.\n\n\n\nFinal release for client libraries\n\nClient libraries s
 hould issue their final release during this week\, to match feature freeze
 .\n\n\n\nSoft StringFreeze\n\nYou are no longer allowed to accept proposed
  changes containing modifications in user-facing strings. Such changes sho
 uld be rejected by the review team and postponed until the next series dev
 elopment opens (which should happen when RC1 is published).\n\n\n\nRequire
 ments freeze\n\nAfter the Queens-3 milestone\, only critical requirements 
 and constraints changes will be allowed. Freezing our requirements list gi
 ves packagers downstream an opportunity to catch up and prepare packages f
 or everything necessary for distributions of the upcoming release. The req
 uirements remain frozen until the stable branches are created\, with the r
 elease candidates.\n\n\n\nQueens Community Goals Completed\n\nTeams should
  prepare their documentation for completing the community-wide goals for Q
 ueens.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-4
DTSTART;VALUE=DATE:20180129
DTEND;VALUE=DATE:20180203
DTSTAMP:20180312T172305Z
UID:Queens-R-4
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-3 (RC1 target week\; Hard StringFreeze)
DTSTART;VALUE=DATE:20180205
DTEND;VALUE=DATE:20180210
DTSTAMP:20180312T172305Z
UID:Queens-R-3
DESCRIPTION:RC1 target week\n\nThe week of 5 February 2018 is the target d
 ate for projects following the release:cycle-with-milestones model to issu
 e their first release candidate\, with a deadline of 8 February 2018.\n\n\
 n\nHard StringFreeze\n\nThis happens when the RC1 for the project is tagge
 d. At this point\, ideally no strings are changed (or added\, or removed)\
 , to give translator time to finish up their efforts.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-2
DTSTART;VALUE=DATE:20180212
DTEND;VALUE=DATE:20180217
DTSTAMP:20180312T172305Z
UID:Queens-R-2
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R-1 (Final RCs and intermediary releases)
DTSTART;VALUE=DATE:20180219
DTEND;VALUE=DATE:20180224
DTSTAMP:20180312T172305Z
UID:Queens-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of 19 February
  2018 is the last week to issue release candidates or intermediary release
 s before release week. During release week\, only final-release-critical r
 eleases will be accepted (at the discretion of the release team).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Queens R+0 (Queens release)
DTSTART;VALUE=DATE:20180226
DTEND;VALUE=DATE:20180303
DTSTAMP:20180312T172305Z
UID:Queens-R+0
DESCRIPTION:Queens release\n\nThe Queens coordinated release will happen o
 n 28 February 2018.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-25
DTSTART;VALUE=DATE:20180305
DTEND;VALUE=DATE:20180310
DTSTAMP:20180716T150548Z
UID:Rocky-R-25
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-24
DTSTART;VALUE=DATE:20180312
DTEND;VALUE=DATE:20180317
DTSTAMP:20180716T150548Z
UID:Rocky-R-24
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-23
DTSTART;VALUE=DATE:20180319
DTEND;VALUE=DATE:20180324
DTSTAMP:20180716T150548Z
UID:Rocky-R-23
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-22
DTSTART;VALUE=DATE:20180326
DTEND;VALUE=DATE:20180331
DTSTAMP:20180716T150548Z
UID:Rocky-R-22
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-21
DTSTART;VALUE=DATE:20180402
DTEND;VALUE=DATE:20180407
DTSTAMP:20180716T150548Z
UID:Rocky-R-21
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-20 (TC Election Nomination Begins)
DTSTART;VALUE=DATE:20180409
DTEND;VALUE=DATE:20180414
DTSTAMP:20180716T150548Z
UID:Rocky-R-20
DESCRIPTION:TC Election Nomination Begins\n\nTechnical committee candidate
 s interested in serving for the next calendar year should announce their c
 andidacies and platforms during this week.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-19 (Rocky-1 milestone\; TC Election Email Deadline\; TC El
 ection Campaigning Begins)
DTSTART;VALUE=DATE:20180416
DTEND;VALUE=DATE:20180421
DTSTAMP:20180716T150548Z
UID:Rocky-R-19
DESCRIPTION:Rocky-1 milestone\n\n19 April 2018 is the Rocky-1 milestone wi
 ndow for projects following the release:cycle-with-milestones model.\n\n\n
 \n\n\nTC Election Email Deadline\n\nContributors that will be in the elect
 orate for the upcoming election should confirm their gerrit email addresse
 s by this date (April 18th\, 2018 at 00:00 UTC). Electorate rolls are gene
 rated after this date and ballots will be sent to the listed gerrit email 
 address.\n\n\n\nTC Election Campaigning Begins\n\nThe electorate has time 
 to ask candidates questions about their platforms and debate topics before
  polling begins.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-18 (TC Election Polling Begins)
DTSTART;VALUE=DATE:20180423
DTEND;VALUE=DATE:20180428
DTSTAMP:20180716T150548Z
UID:Rocky-R-18
DESCRIPTION:TC Election Polling Begins\n\nElection polling week for open s
 eats on the TC.
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-17
DTSTART;VALUE=DATE:20180430
DTEND;VALUE=DATE:20180505
DTSTAMP:20180716T150548Z
UID:Rocky-R-17
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-16
DTSTART;VALUE=DATE:20180507
DTEND;VALUE=DATE:20180512
DTSTAMP:20180716T150548Z
UID:Rocky-R-16
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-15
DTSTART;VALUE=DATE:20180514
DTEND;VALUE=DATE:20180519
DTSTAMP:20180716T150548Z
UID:Rocky-R-15
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-14 (OpenStack Summit)
DTSTART;VALUE=DATE:20180521
DTEND;VALUE=DATE:20180526
DTSTAMP:20180716T150548Z
UID:Rocky-R-14
DESCRIPTION:OpenStack Summit\n\nThe OpenStack Summit happens during this w
 eek in Vancouver\, BC. It will include a “Forum” in which people from 
 all parts of our community will gather to give feedback on the last releas
 e (Queens) and discuss requirements for the next development cycle (Stein)
 .\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-13
DTSTART;VALUE=DATE:20180528
DTEND;VALUE=DATE:20180602
DTSTAMP:20180716T150548Z
UID:Rocky-R-13
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-12 (Rocky-2 milestone\; Membership Freeze)
DTSTART;VALUE=DATE:20180604
DTEND;VALUE=DATE:20180609
DTSTAMP:20180716T150548Z
UID:Rocky-R-12
DESCRIPTION:Rocky-2 milestone\n\n7 June 2018 is the Rocky-2 milestone wind
 ow for projects following the release:cycle-with-milestones model.\n\n\n\n
 Membership Freeze\n\nProjects must participate in at least two milestones 
 in order to be considered part of the release. Projects made official afte
 r the second milestone\, or which fail to produce milestone releases for a
 t least one of the first and second milestones as well as the third milest
 one\, are therefore not considered part of the release for the cycle. This
  does not apply to cycle-trailing packaging / lifecycle management project
 s.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-11
DTSTART;VALUE=DATE:20180611
DTEND;VALUE=DATE:20180616
DTSTAMP:20180716T150548Z
UID:Rocky-R-11
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-10
DTSTART;VALUE=DATE:20180618
DTEND;VALUE=DATE:20180623
DTSTAMP:20180716T150548Z
UID:Rocky-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-9
DTSTART;VALUE=DATE:20180625
DTEND;VALUE=DATE:20180630
DTSTAMP:20180716T150548Z
UID:Rocky-R-9
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-8
DTSTART;VALUE=DATE:20180702
DTEND;VALUE=DATE:20180707
DTSTAMP:20180716T150548Z
UID:Rocky-R-8
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-7 (Extra-ATCs deadline)
DTSTART;VALUE=DATE:20180709
DTEND;VALUE=DATE:20180714
DTSTAMP:20180716T150548Z
UID:Rocky-R-7
DESCRIPTION:Extra-ATCs deadline\n\nProject teams should identify contribut
 ors who have had a significant impact this cycle but who would not qualify
  for ATC status using the regular process because they have not submitted 
 a patch. Those names should be added to the governance repo for considerat
 ion as ATC for the future.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-6 (Final release for non-client libraries)
DTSTART;VALUE=DATE:20180716
DTEND;VALUE=DATE:20180721
DTSTAMP:20180716T150548Z
UID:Rocky-R-6
DESCRIPTION:Final release for non-client libraries\n\nLibraries that are n
 ot client libraries (Oslo and others) should issue their final release dur
 ing this week. That allows to give time for last-minute changes before fea
 ture freeze.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-5 (Rocky-3 milestone\; Feature freeze\; Final release for 
 client libraries\; Soft StringFreeze\; Requirements freeze\; Rocky Communi
 ty Goals Completed)
DTSTART;VALUE=DATE:20180723
DTEND;VALUE=DATE:20180728
DTSTAMP:20180716T150548Z
UID:Rocky-R-5
DESCRIPTION:Rocky-3 milestone\n\n26 July 2018 is the Rocky-3 milestone win
 dow for projects following the release:cycle-with-milestones model.\n\n\n\
 nFeature freeze\n\nThe Rocky-3 milestone marks feature freeze for projects
  following the release:cycle-with-milestones model. No featureful patch sh
 ould be landed after this point. Exceptions may be granted by the project 
 PTL.\n\n\n\nFinal release for client libraries\n\nClient libraries should 
 issue their final release during this week\, to match feature freeze.\n\n\
 n\nSoft StringFreeze\n\nYou are no longer allowed to accept proposed chang
 es containing modifications in user-facing strings. Such changes should be
  rejected by the review team and postponed until the next series developme
 nt opens (which should happen when RC1 is published).\n\n\n\nRequirements 
 freeze\n\nAfter the Rocky-3 milestone\, only critical requirements and con
 straints changes will be allowed. Freezing our requirements list gives pac
 kagers downstream an opportunity to catch up and prepare packages for ever
 ything necessary for distributions of the upcoming release. The requiremen
 ts remain frozen until the stable branches are created\, with the release 
 candidates.\n\n\n\nRocky Community Goals Completed\n\nTeams should prepare
  their documentation for completing the community-wide goals for Rocky.\n\
 n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-4
DTSTART;VALUE=DATE:20180730
DTEND;VALUE=DATE:20180804
DTSTAMP:20180716T150548Z
UID:Rocky-R-4
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-3 (RC1 target week\; Hard StringFreeze)
DTSTART;VALUE=DATE:20180806
DTEND;VALUE=DATE:20180811
DTSTAMP:20180716T150548Z
UID:Rocky-R-3
DESCRIPTION:RC1 target week\n\nThe week of 6 August 2018 is the target dat
 e for projects following the release:cycle-with-milestones model to issue 
 their first release candidate\, with a deadline of 9 August 2018.\n\n\n\nH
 ard StringFreeze\n\nThis happens when the RC1 for the project is tagged. A
 t this point\, ideally no strings are changed (or added\, or removed)\, to
  give translator time to finish up their efforts.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-2
DTSTART;VALUE=DATE:20180813
DTEND;VALUE=DATE:20180818
DTSTAMP:20180716T150548Z
UID:Rocky-R-2
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-1 (Final RCs and intermediary releases)
DTSTART;VALUE=DATE:20180820
DTEND;VALUE=DATE:20180825
DTSTAMP:20180716T150548Z
UID:Rocky-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of 20 August 2
 018 is the last week to issue release candidates or intermediary releases 
 before release week. During release week\, only final-release-critical rel
 eases will be accepted (at the discretion of the release team).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Rocky R-0 (Rocky release)
DTSTART;VALUE=DATE:20180827
DTEND;VALUE=DATE:20180901
DTSTAMP:20180716T150548Z
UID:Rocky-R-0
DESCRIPTION:Rocky release\n\nThe Rocky coordinated release will happen on 
 30 August 2018.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-31 (Stein TC Election\; Stein TC Election Campaigning Begi
 ns)
DTSTART;VALUE=DATE:20180903
DTEND;VALUE=DATE:20180908
DTSTAMP:20190318T144016Z
UID:Stein-R-31
DESCRIPTION:Stein TC Election\n\nStein TC Election Email Deadline\n\nContr
 ibutors that will be in the electorate for the upcoming election should co
 nfirm their gerrit email addresses by this date (September 9th\, 2018 at 0
 0:00 UTC). Electorate rolls are generated after this date and ballots will
  be sent to the listed gerrit email address.\n\n\n\nStein TC Election Nomi
 nation Begins\n\nTechnical committee candidates interested in serving for 
 the next calendar year should announce their candidacies and platforms dur
 ing this week.  Please see the Election site for specific timing informati
 on.\n\n\n\nStein TC Election Campaigning Begins\n\nThe electorate has time
  to ask candidates questions about their platforms and debate topics befor
 e polling begins.  Please see the Election site for specific timing inform
 ation.\n\n\n\nStein TC Election Polling Begins\n\nElection polling week fo
 r open seats on the TC.  Please see the Election site for specific timing 
 information.\n\nStein TC Election Campaigning Begins\n\nThe electorate has
  time to ask candidates questions about their platforms and debate topics 
 before polling begins.  Please see the Election site for specific timing i
 nformation.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-30 (Stein Project Team Gathering (PTG))
DTSTART;VALUE=DATE:20180910
DTEND;VALUE=DATE:20180915
DTSTAMP:20190318T144016Z
UID:Stein-R-30
DESCRIPTION:Stein Project Team Gathering (PTG)\n\nProject team gathering f
 or the Stein cycle 10 - 14 September in Denver\, Colorado\, USA.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-29 (Stein TC Election Polling Begins)
DTSTART;VALUE=DATE:20180917
DTEND;VALUE=DATE:20180922
DTSTAMP:20190318T144016Z
UID:Stein-R-29
DESCRIPTION:Stein TC Election Polling Begins\n\nElection polling week for 
 open seats on the TC.  Please see the Election site for specific timing in
 formation.
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-28
DTSTART;VALUE=DATE:20180924
DTEND;VALUE=DATE:20180929
DTSTAMP:20190318T144016Z
UID:Stein-R-28
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-27
DTSTART;VALUE=DATE:20181001
DTEND;VALUE=DATE:20181006
DTSTAMP:20190318T144016Z
UID:Stein-R-27
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-26
DTSTART;VALUE=DATE:20181008
DTEND;VALUE=DATE:20181013
DTSTAMP:20190318T144016Z
UID:Stein-R-26
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-25
DTSTART;VALUE=DATE:20181015
DTEND;VALUE=DATE:20181020
DTSTAMP:20190318T144016Z
UID:Stein-R-25
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-24 (Stein-1 milestone)
DTSTART;VALUE=DATE:20181022
DTEND;VALUE=DATE:20181027
DTSTAMP:20190318T144016Z
UID:Stein-R-24
DESCRIPTION:Stein-1 milestone\n\n25 October 2018 is the Stein-1 milestone.
 \n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-23
DTSTART;VALUE=DATE:20181029
DTEND;VALUE=DATE:20181103
DTSTAMP:20190318T144016Z
UID:Stein-R-23
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-22
DTSTART;VALUE=DATE:20181105
DTEND;VALUE=DATE:20181110
DTSTAMP:20190318T144016Z
UID:Stein-R-22
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-21 (OpenStack Summit)
DTSTART;VALUE=DATE:20181112
DTEND;VALUE=DATE:20181117
DTSTAMP:20190318T144016Z
UID:Stein-R-21
DESCRIPTION:OpenStack Summit\n\nThe OpenStack Summit happens during this w
 eek in Berlin\, Germany. It will include a “Forum” in which people fro
 m all parts of our community will gather to give feedback on the last rele
 ase (Rocky) and discuss requirements for the next development cycle (Stein
 ).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-20
DTSTART;VALUE=DATE:20181119
DTEND;VALUE=DATE:20181124
DTSTAMP:20190318T144016Z
UID:Stein-R-20
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-19
DTSTART;VALUE=DATE:20181126
DTEND;VALUE=DATE:20181201
DTSTAMP:20190318T144016Z
UID:Stein-R-19
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-18
DTSTART;VALUE=DATE:20181203
DTEND;VALUE=DATE:20181208
DTSTAMP:20190318T144016Z
UID:Stein-R-18
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-17
DTSTART;VALUE=DATE:20181210
DTEND;VALUE=DATE:20181215
DTSTAMP:20190318T144016Z
UID:Stein-R-17
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-16
DTSTART;VALUE=DATE:20181217
DTEND;VALUE=DATE:20181222
DTSTAMP:20190318T144016Z
UID:Stein-R-16
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-15
DTSTART;VALUE=DATE:20181224
DTEND;VALUE=DATE:20181229
DTSTAMP:20190318T144016Z
UID:Stein-R-15
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-14
DTSTART;VALUE=DATE:20181231
DTEND;VALUE=DATE:20190105
DTSTAMP:20190318T144016Z
UID:Stein-R-14
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-13 (Stein-2 milestone\; Membership Freeze)
DTSTART;VALUE=DATE:20190107
DTEND;VALUE=DATE:20190112
DTSTAMP:20190318T144016Z
UID:Stein-R-13
DESCRIPTION:Stein-2 milestone\n\n10 January 2019 is the Stein-2 milestone.
 \n\n\n\nMembership Freeze\n\nProjects made official after the second miles
 tone\, are not considered part of the release for the cycle. This does not
  apply to cycle-trailing packaging / lifecycle management projects.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-12
DTSTART;VALUE=DATE:20190114
DTEND;VALUE=DATE:20190119
DTSTAMP:20190318T144016Z
UID:Stein-R-12
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-11
DTSTART;VALUE=DATE:20190121
DTEND;VALUE=DATE:20190126
DTSTAMP:20190318T144016Z
UID:Stein-R-11
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-10
DTSTART;VALUE=DATE:20190128
DTEND;VALUE=DATE:20190202
DTSTAMP:20190318T144016Z
UID:Stein-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-9
DTSTART;VALUE=DATE:20190204
DTEND;VALUE=DATE:20190209
DTSTAMP:20190318T144016Z
UID:Stein-R-9
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-8 (Train TC Election Nomination Begins)
DTSTART;VALUE=DATE:20190211
DTEND;VALUE=DATE:20190216
DTSTAMP:20190318T144016Z
UID:Stein-R-8
DESCRIPTION:Train TC Election Nomination Begins\n\nTechnical committee can
 didates interested in serving for the next calendar year should announce t
 heir candidacies and platforms during this week.  Please see the Election 
 site for specific timing information.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-7 (Train Election Email Deadline\; Train TC Election Campa
 igning Begins)
DTSTART;VALUE=DATE:20190218
DTEND;VALUE=DATE:20190223
DTSTAMP:20190318T144016Z
UID:Stein-R-7
DESCRIPTION:Train Election Email Deadline\n\nContributors that will be in 
 the electorate for the upcoming PTL and TC elections should confirm their 
 gerrit email addresses by this date (February 19th\, 2019 at 00:00 UTC). E
 lectorate rolls are generated after this date and ballots will be sent to 
 the listed gerrit email address.\n\n\n\nTrain TC Election Campaigning Begi
 ns\n\nThe electorate has time to ask candidates questions about their plat
 forms and debate topics before polling begins.  Please see the Election si
 te for specific timing information.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-6 (Final release for non-client libraries\; Train TC Elect
 ion Polling Begins)
DTSTART;VALUE=DATE:20190225
DTEND;VALUE=DATE:20190302
DTSTAMP:20190318T144016Z
UID:Stein-R-6
DESCRIPTION:Final release for non-client libraries\n\nLibraries that are n
 ot client libraries (Oslo and others) should issue their final release dur
 ing this week. That allows to give time for last-minute changes before fea
 ture freeze.\n\n\n\nTrain TC Election Polling Begins\n\nElection polling w
 eek for open seats on the TC.  Please see the Election site for specific t
 iming information.
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-5 (Stein-3 milestone\; Feature freeze\; Final release for 
 client libraries\; Soft StringFreeze\; Requirements freeze\; Stein Communi
 ty Goals Completed)
DTSTART;VALUE=DATE:20190304
DTEND;VALUE=DATE:20190309
DTSTAMP:20190318T144016Z
UID:Stein-R-5
DESCRIPTION:Stein-3 milestone\n\n7 March 2019 is the Stein-3 milestone.\n\
 n\n\nFeature freeze\n\nThe Stein-3 milestone marks feature freeze for proj
 ects following the release:cycle-with-rc model. No featureful patch should
  be landed after this point. Exceptions may be granted by the project PTL.
 \n\n\n\nFinal release for client libraries\n\nClient libraries should issu
 e their final release during this week\, to match feature freeze.\n\n\n\nS
 oft StringFreeze\n\nYou are no longer allowed to accept proposed changes c
 ontaining modifications in user-facing strings. Such changes should be rej
 ected by the review team and postponed until the next series development o
 pens (which should happen when RC1 is published).\n\n\n\nRequirements free
 ze\n\nAfter the Stein-3 milestone\, only critical requirements and constra
 ints changes will be allowed. Freezing our requirements list gives package
 rs downstream an opportunity to catch up and prepare packages for everythi
 ng necessary for distributions of the upcoming release. The requirements r
 emain frozen until the stable branches are created\, with the release cand
 idates.\n\n\n\nStein Community Goals Completed\n\nTeams should prepare the
 ir documentation for completing the community-wide goals for Stein.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-4
DTSTART;VALUE=DATE:20190311
DTEND;VALUE=DATE:20190316
DTSTAMP:20190318T144016Z
UID:Stein-R-4
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-3 (RC1 target week\; Hard StringFreeze\; Cycle highlights 
 marketing deadline)
DTSTART;VALUE=DATE:20190318
DTEND;VALUE=DATE:20190323
DTSTAMP:20190318T144016Z
UID:Stein-R-3
DESCRIPTION:RC1 target week\n\nThis week is the target for projects follow
 ing the release:cycle-with-rc model to issue their first release candidate
 \, with a deadline of 21 March 2019.\n\n\n\n\n\nHard StringFreeze\n\nThis 
 happens when the RC1 for the project is tagged. At this point\, ideally no
  strings are changed (or added\, or removed)\, to give translator time to 
 finish up their efforts.\n\n\n\nCycle highlights marketing deadline\n\nCyc
 le highlights need to be added to the release deliverables by this point t
 o be included in any marketing release messaging. Highlights may be added 
 after this point\, but they will likely only be useful for historical purp
 oses.\n\nSee the project team guide for more details and instructions on a
 dding these highlights.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-2
DTSTART;VALUE=DATE:20190325
DTEND;VALUE=DATE:20190330
DTSTAMP:20190318T144016Z
UID:Stein-R-2
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R-1 (Final RCs and intermediary releases)
DTSTART;VALUE=DATE:20190401
DTEND;VALUE=DATE:20190406
DTSTAMP:20190318T144016Z
UID:Stein-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of 1 April 201
 9 is the last week to issue release candidates or intermediary releases be
 fore release week. During release week\, only final-release-critical relea
 ses will be accepted (at the discretion of the release team).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Stein R+0 (Stein release)
DTSTART;VALUE=DATE:20190408
DTEND;VALUE=DATE:20190413
DTSTAMP:20190318T144016Z
UID:Stein-R+0
DESCRIPTION:Stein release\n\nThe Stein coordinated release will happen on 
 10 April 2019.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-26
DTSTART;VALUE=DATE:20190415
DTEND;VALUE=DATE:20190420
DTSTAMP:20190611T223045Z
UID:Train-R-26
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-25
DTSTART;VALUE=DATE:20190422
DTEND;VALUE=DATE:20190427
DTSTAMP:20190611T223045Z
UID:Train-R-25
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-24 (Open Infrastructure Summit)
DTSTART;VALUE=DATE:20190429
DTEND;VALUE=DATE:20190504
DTSTAMP:20190611T223045Z
UID:Train-R-24
DESCRIPTION:Open Infrastructure Summit\n\nThe Open Infrastructure Summit h
 appens during this week in Denver\, CO\, USA. It will include a “Forum
 ” in which people from all parts of our community will gather to give fe
 edback on the last release (Stein) and discuss requirements for the next d
 evelopment cycle (Train).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-23
DTSTART;VALUE=DATE:20190506
DTEND;VALUE=DATE:20190511
DTSTAMP:20190611T223045Z
UID:Train-R-23
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-22
DTSTART;VALUE=DATE:20190513
DTEND;VALUE=DATE:20190518
DTSTAMP:20190611T223045Z
UID:Train-R-22
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-21
DTSTART;VALUE=DATE:20190520
DTEND;VALUE=DATE:20190525
DTSTAMP:20190611T223045Z
UID:Train-R-21
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-20
DTSTART;VALUE=DATE:20190527
DTEND;VALUE=DATE:20190601
DTSTAMP:20190611T223045Z
UID:Train-R-20
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-19 (Train-1 milestone)
DTSTART;VALUE=DATE:20190603
DTEND;VALUE=DATE:20190608
DTSTAMP:20190611T223045Z
UID:Train-R-19
DESCRIPTION:Train-1 milestone\n\n6 June\, 2019 is the Train-1 milestone. S
 ee project-specific notes for relevant deadlines.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-18
DTSTART;VALUE=DATE:20190610
DTEND;VALUE=DATE:20190615
DTSTAMP:20190611T223045Z
UID:Train-R-18
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-17
DTSTART;VALUE=DATE:20190617
DTEND;VALUE=DATE:20190622
DTSTAMP:20190611T223045Z
UID:Train-R-17
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-16
DTSTART;VALUE=DATE:20190624
DTEND;VALUE=DATE:20190629
DTSTAMP:20190611T223045Z
UID:Train-R-16
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-15
DTSTART;VALUE=DATE:20190701
DTEND;VALUE=DATE:20190706
DTSTAMP:20190611T223045Z
UID:Train-R-15
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-14
DTSTART;VALUE=DATE:20190708
DTEND;VALUE=DATE:20190713
DTSTAMP:20190611T223045Z
UID:Train-R-14
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-13
DTSTART;VALUE=DATE:20190715
DTEND;VALUE=DATE:20190720
DTSTAMP:20190611T223045Z
UID:Train-R-13
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-12 (Train-2 milestone\; Membership Freeze)
DTSTART;VALUE=DATE:20190722
DTEND;VALUE=DATE:20190727
DTSTAMP:20190611T223045Z
UID:Train-R-12
DESCRIPTION:Train-2 milestone\n\n25 July\, 2019 is the Train-2 milestone. 
 See project-specific notes for relevant deadlines.\n\n\n\nMembership Freez
 e\n\nProjects must participate in at least two milestones in order to be c
 onsidered part of the release. Projects made official after the second mil
 estone\, or which fail to produce milestone releases for at least one of t
 he first and second milestones as well as the third milestone\, are theref
 ore not considered part of the release for the cycle. This does not apply 
 to cycle-trailing packaging / lifecycle management projects.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-11
DTSTART;VALUE=DATE:20190729
DTEND;VALUE=DATE:20190803
DTSTAMP:20190611T223045Z
UID:Train-R-11
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-10
DTSTART;VALUE=DATE:20190805
DTEND;VALUE=DATE:20190810
DTSTAMP:20190611T223045Z
UID:Train-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-9
DTSTART;VALUE=DATE:20190812
DTEND;VALUE=DATE:20190817
DTSTAMP:20190611T223045Z
UID:Train-R-9
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-8
DTSTART;VALUE=DATE:20190819
DTEND;VALUE=DATE:20190824
DTSTAMP:20190611T223045Z
UID:Train-R-8
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-7 (TC Election Nomination Begins\; Extra-ATCs deadline)
DTSTART;VALUE=DATE:20190826
DTEND;VALUE=DATE:20190831
DTSTAMP:20190611T223045Z
UID:Train-R-7
DESCRIPTION:TC Election Nomination Begins\n\nTechnical committee candidate
 s interested in serving for the next calendar year should announce their c
 andidacies and platforms during this week.  Please see the Election site f
 or specific timing imformation.\n\n\n\nExtra-ATCs deadline\n\nProject team
 s should identify contributors who have had a significant impact this cycl
 e but who would not qualify for ATC status using the regular process becau
 se they have not submitted a patch. Those names should be added to the gov
 ernance repo for consideration as ATC for the future.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-6 (Final release for non-client libraries\; Election Email
  Deadline\; TC Election Campaigning Begins)
DTSTART;VALUE=DATE:20190902
DTEND;VALUE=DATE:20190907
DTSTAMP:20190611T223045Z
UID:Train-R-6
DESCRIPTION:Final release for non-client libraries\n\nLibraries that are n
 ot client libraries (Oslo and others) should issue their final release dur
 ing this week. That allows to give time for last-minute changes before fea
 ture freeze.\n\n\n\nElection Email Deadline\n\nContributors that will be i
 n the electorate for the upcoming elections should confirm their gerrit em
 ail addresses by this date (September 3rd\, 2019 at 00:00 UTC). Electorate
  rolls are generated after this date and ballots will be sent to the liste
 d gerrit email address.\n\nTC Election Campaigning Begins\n\nThe electorat
 e has time to ask candidates questions about their platforms and debate to
 pics before polling begins.  Please see the Election site for specific tim
 ing information.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-5 (Train-3 milestone\; Feature freeze\; Final release for 
 client libraries\; Soft StringFreeze\; Requirements freeze\; Train Communi
 ty Goals Completed\; Cycle highlights marketing deadline\; TC Election Pol
 ling Begins)
DTSTART;VALUE=DATE:20190909
DTEND;VALUE=DATE:20190914
DTSTAMP:20190611T223045Z
UID:Train-R-5
DESCRIPTION:Train-3 milestone\n\n12 September\, 2019 is the Train-3 milest
 one. See project-specific notes for relevant deadlines.\n\n\n\nFeature fre
 eze\n\nThe Train-3 milestone marks feature freeze for projects following t
 he release:cycle-with-rc model. No featureful patch should be landed after
  this point. Exceptions may be granted by the project PTL.\n\n\n\n\n\nFina
 l release for client libraries\n\nClient libraries should issue their fina
 l release during this week\, to match feature freeze.\n\n\n\nSoft StringFr
 eeze\n\nYou are no longer allowed to accept proposed changes containing mo
 difications in user-facing strings. Such changes should be rejected by the
  review team and postponed until the next series development opens (which 
 should happen when RC1 is published).\n\n\n\nRequirements freeze\n\nAfter 
 the Train-3 milestone\, only critical requirements and constraints changes
  will be allowed. Freezing our requirements list gives packagers downstrea
 m an opportunity to catch up and prepare packages for everything necessary
  for distributions of the upcoming release. The requirements remain frozen
  until the stable branches are created\, with the release candidates.\n\n\
 n\nTrain Community Goals Completed\n\nTeams should prepare their documenta
 tion for completing the community-wide goals for Train.\n\n\n\nCycle highl
 ights marketing deadline\n\nCycle highlights need to be added to the relea
 se deliverables by feature freeze to be included in any marketing release 
 messaging. Highlights may be added after this point\, but they will likely
  only be useful for historical purposes.\n\nSee the project team guide for
  more details and instructions on adding these highlights.\n\n\n\nTC Elect
 ion Polling Begins\n\nElection polling week for open seats on the TC.  Ple
 ase see the Election site for specific timing imformation.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-4
DTSTART;VALUE=DATE:20190916
DTEND;VALUE=DATE:20190921
DTSTAMP:20190611T223045Z
UID:Train-R-4
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-3 (RC1 target week\; Hard StringFreeze)
DTSTART;VALUE=DATE:20190923
DTEND;VALUE=DATE:20190928
DTSTAMP:20190611T223045Z
UID:Train-R-3
DESCRIPTION:RC1 target week\n\nThe week of September 23-27 is the target d
 ate for projects following the release:cycle-with-rc model to issue their 
 first release candidate.\n\n\n\nHard StringFreeze\n\nThis happens when the
  RC1 for the project is tagged. At this point\, ideally no strings are cha
 nged (or added\, or removed)\, to give translators time to finish up their
  efforts.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-2
DTSTART;VALUE=DATE:20190930
DTEND;VALUE=DATE:20191005
DTSTAMP:20190611T223045Z
UID:Train-R-2
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-1 (Final RCs and intermediary releases)
DTSTART;VALUE=DATE:20191007
DTEND;VALUE=DATE:20191012
DTSTAMP:20190611T223045Z
UID:Train-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of October 7-1
 1 is the last week to issue release candidates or intermediary releases be
 fore release week. During release week\, only final-release-critical relea
 ses will be accepted (at the discretion of the release team).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R+0 (Train release)
DTSTART;VALUE=DATE:20191014
DTEND;VALUE=DATE:20191019
DTSTAMP:20190611T223045Z
UID:Train-R+0
DESCRIPTION:Train release\n\nThe Train coordinated release will happen on 
 16 October 2019.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-29
DTSTART;VALUE=DATE:20191021
DTEND;VALUE=DATE:20191026
DTSTAMP:20200319T101810Z
UID:Ussuri-R-29
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-28
DTSTART;VALUE=DATE:20191028
DTEND;VALUE=DATE:20191102
DTSTAMP:20200319T101810Z
UID:Ussuri-R-28
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-27 (Open Infrastructure Summit)
DTSTART;VALUE=DATE:20191104
DTEND;VALUE=DATE:20191109
DTSTAMP:20200319T101810Z
UID:Ussuri-R-27
DESCRIPTION:Open Infrastructure Summit\n\nThe Open Infrastructure Summit h
 appens during this week in Shanghai\, China. It will include a “Forum”
  in which people from all parts of our community will gather to give feedb
 ack on the last release (Train) and discuss requirements for future releas
 es.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-26
DTSTART;VALUE=DATE:20191111
DTEND;VALUE=DATE:20191116
DTSTAMP:20200319T101810Z
UID:Ussuri-R-26
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-25
DTSTART;VALUE=DATE:20191118
DTEND;VALUE=DATE:20191123
DTSTAMP:20200319T101810Z
UID:Ussuri-R-25
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-24
DTSTART;VALUE=DATE:20191125
DTEND;VALUE=DATE:20191130
DTSTAMP:20200319T101810Z
UID:Ussuri-R-24
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-23
DTSTART;VALUE=DATE:20191202
DTEND;VALUE=DATE:20191207
DTSTAMP:20200319T101810Z
UID:Ussuri-R-23
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-22 (Ussuri-1 milestone\; Services Drop python 2 Completed
 \; Common libraries & QA Start dropping python 2)
DTSTART;VALUE=DATE:20191209
DTEND;VALUE=DATE:20191214
DTSTAMP:20200319T101810Z
UID:Ussuri-R-22
DESCRIPTION:Ussuri-1 milestone\n\n12 December\, 2019 is the Ussuri-1 miles
 tone. See project-specific notes for relevant deadlines.\n\n\n\nServices D
 rop python 2 Completed\n\nOpenStack Services dropped the python 2.7 suppor
 t and testing. Project needs to coordinate with third party CI or any back
 end drivers.\n\n\n\nCommon libraries & QA Start dropping python 2\n\nCommo
 n libraries & QA start dropping the python 2.7 support and testing. This i
 ncludes Oslo\, QA tools (including Tempest plugins or any other testing to
 ols)\, common lib used among projects (os-brick)\, Client libraries. Tempe
 st will drop the support during Feb as discussed with TripleO.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-21
DTSTART;VALUE=DATE:20191216
DTEND;VALUE=DATE:20191221
DTSTAMP:20200319T101810Z
UID:Ussuri-R-21
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-20
DTSTART;VALUE=DATE:20191223
DTEND;VALUE=DATE:20191228
DTSTAMP:20200319T101810Z
UID:Ussuri-R-20
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-19
DTSTART;VALUE=DATE:20191230
DTEND;VALUE=DATE:20200104
DTSTAMP:20200319T101810Z
UID:Ussuri-R-19
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-18 (Train Cycle-Trailing Release Deadline)
DTSTART;VALUE=DATE:20200106
DTEND;VALUE=DATE:20200111
DTSTAMP:20200319T101810Z
UID:Ussuri-R-18
DESCRIPTION:Train Cycle-Trailing Release Deadline\n\nAll projects followin
 g the cycle-trailing release model must release their Train deliverables b
 y 9 January\, 2020.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-17
DTSTART;VALUE=DATE:20200113
DTEND;VALUE=DATE:20200118
DTSTAMP:20200319T101810Z
UID:Ussuri-R-17
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-16
DTSTART;VALUE=DATE:20200120
DTEND;VALUE=DATE:20200125
DTSTAMP:20200319T101810Z
UID:Ussuri-R-16
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-15
DTSTART;VALUE=DATE:20200127
DTEND;VALUE=DATE:20200201
DTSTAMP:20200319T101810Z
UID:Ussuri-R-15
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-14
DTSTART;VALUE=DATE:20200203
DTEND;VALUE=DATE:20200208
DTSTAMP:20200319T101810Z
UID:Ussuri-R-14
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-13 (Ussuri-2 milestone\; Membership Freeze\; Common libra
 ries & QA Drop python 2 Completed\; Requirement Drop python 2 & Audit)
DTSTART;VALUE=DATE:20200210
DTEND;VALUE=DATE:20200215
DTSTAMP:20200319T101810Z
UID:Ussuri-R-13
DESCRIPTION:Ussuri-2 milestone\n\n13 February\, 2020 is the Ussuri-2 miles
 tone. See project-specific notes for relevant deadlines.\n\n\n\nMembership
  Freeze\n\nProjects must participate in at least two milestones in order t
 o be considered part of the release. Projects made official after the seco
 nd milestone\, or which fail to produce milestone releases for at least on
 e of the first and second milestones as well as the third milestone\, are 
 therefore not considered part of the release for the cycle. This does not 
 apply to cycle-trailing packaging / lifecycle management projects.\n\n\n\n
 Common libraries & QA Drop python 2 Completed\n\nCommon libraries & QA dro
 pped the python 2.7 support and testing.\n\n\n\nRequirement Drop python 2 
 & Audit\n\nRequirement to drop the python 2.7 support and testing. Audit t
 hat every project except Swift have dropped the python 2 support.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-12
DTSTART;VALUE=DATE:20200217
DTEND;VALUE=DATE:20200222
DTSTAMP:20200319T101810Z
UID:Ussuri-R-12
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-11
DTSTART;VALUE=DATE:20200224
DTEND;VALUE=DATE:20200229
DTSTAMP:20200319T101810Z
UID:Ussuri-R-11
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-10
DTSTART;VALUE=DATE:20200302
DTEND;VALUE=DATE:20200307
DTSTAMP:20200319T101810Z
UID:Ussuri-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-9
DTSTART;VALUE=DATE:20200309
DTEND;VALUE=DATE:20200314
DTSTAMP:20200319T101810Z
UID:Ussuri-R-9
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-8
DTSTART;VALUE=DATE:20200316
DTEND;VALUE=DATE:20200321
DTSTAMP:20200319T101810Z
UID:Ussuri-R-8
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-7 (Extra-ATCs deadline\; TC Election Nomination Begins)
DTSTART;VALUE=DATE:20200323
DTEND;VALUE=DATE:20200328
DTSTAMP:20200319T101810Z
UID:Ussuri-R-7
DESCRIPTION:Extra-ATCs deadline\n\nProject teams should identify contribut
 ors who have had a significant impact this cycle but who would not qualify
  for ATC status using the regular process because they have not submitted 
 a patch. Those names should be added to the governance repo for considerat
 ion as ATC for the future.\n\n\n\nTC Election Nomination Begins\n\nTechnic
 al committee candidates interested in serving for the next calendar year s
 hould announce their candidacies and platforms during this week.  Please s
 ee the Election site for specific timing imformation.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-6 (Final release for non-client libraries\; TC Election C
 ampaigning Begins\; Election Email Deadline)
DTSTART;VALUE=DATE:20200330
DTEND;VALUE=DATE:20200404
DTSTAMP:20200319T101810Z
UID:Ussuri-R-6
DESCRIPTION:Final release for non-client libraries\n\nLibraries that are n
 ot client libraries (Oslo and others) should issue their final release dur
 ing this week. That allows to give time for last-minute changes before fea
 ture freeze.\n\n\n\nTC Election Campaigning Begins\n\nThe electorate has t
 ime to ask candidates questions about their platforms and debate topics be
 fore polling begins.  Please see the Election site for specific timing inf
 ormation.\n\n\n\nElection Email Deadline\n\nContributors that will be in t
 he electorate for the upcoming elections should confirm their gerrit email
  addresses by this date (April 7th\, 2020 at 00:00 UTC). Electorate rolls 
 are generated after this date and ballots will be sent to the listed gerri
 t email address.
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-5 (Ussuri-3 milestone\; Feature freeze\; Final release fo
 r client libraries\; Soft StringFreeze\; Requirements freeze\; Ussuri Comm
 unity Goals Completed\; TC Election Polling Begins\; u_cycle-highlights)
DTSTART;VALUE=DATE:20200406
DTEND;VALUE=DATE:20200411
DTSTAMP:20200319T101810Z
UID:Ussuri-R-5
DESCRIPTION:Ussuri-3 milestone\n\n9 April\, 2020 is the Ussuri-3 milestone
 . See project-specific notes for relevant deadlines.\n\n\n\nFeature freeze
 \n\nThe Ussuri-3 milestone marks feature freeze for projects following the
  release:cycle-with-rc model. No featureful patch should be landed after t
 his point. Exceptions may be granted by the project PTL.\n\n\n\n\n\nFinal 
 release for client libraries\n\nClient libraries should issue their final 
 release during this week\, to match feature freeze.\n\n\n\nSoft StringFree
 ze\n\nYou are no longer allowed to accept proposed changes containing modi
 fications in user-facing strings. Such changes should be rejected by the r
 eview team and postponed until the next series development opens (which sh
 ould happen when RC1 is published).\n\n\n\nRequirements freeze\n\nAfter th
 e Ussuri-3 milestone\, only critical requirements and constraints changes 
 will be allowed. Freezing our requirements list gives packagers downstream
  an opportunity to catch up and prepare packages for everything necessary 
 for distributions of the upcoming release. The requirements remain frozen 
 until the stable branches are created\, with the release candidates.\n\n\n
 \nUssuri Community Goals Completed\n\nTeams should prepare their documenta
 tion for completing the community-wide goals for Ussuri.\n\n\n\nTC Electio
 n Polling Begins\n\nElection polling week for open seats on the TC.  Pleas
 e see the Election site for specific timing imformation.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-4
DTSTART;VALUE=DATE:20200413
DTEND;VALUE=DATE:20200418
DTSTAMP:20200319T101810Z
UID:Ussuri-R-4
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-3 (RC1 target week\; Hard StringFreeze)
DTSTART;VALUE=DATE:20200420
DTEND;VALUE=DATE:20200425
DTSTAMP:20200319T101810Z
UID:Ussuri-R-3
DESCRIPTION:RC1 target week\n\nThe week of 20 April is the target date for
  projects following the release:cycle-with-rc model to issue their first r
 elease candidate.\n\n\n\nHard StringFreeze\n\nThis happens when the RC1 fo
 r the project is tagged. At this point\, ideally no strings are changed (o
 r added\, or removed)\, to give translators time to finish up their effort
 s.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-2
DTSTART;VALUE=DATE:20200427
DTEND;VALUE=DATE:20200502
DTSTAMP:20200319T101810Z
UID:Ussuri-R-2
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-1 (Final RCs and intermediary releases)
DTSTART;VALUE=DATE:20200504
DTEND;VALUE=DATE:20200509
DTSTAMP:20200319T101810Z
UID:Ussuri-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of 4 May is th
 e last week to issue release candidates or intermediary releases before re
 lease week. During release week\, only final-release-critical releases wil
 l be accepted (at the discretion of the release team).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-0 (Ussuri release)
DTSTART;VALUE=DATE:20200511
DTEND;VALUE=DATE:20200516
DTSTAMP:20200319T101810Z
UID:Ussuri-R-0
DESCRIPTION:Ussuri release\n\nThe Ussuri coordinated release will happen o
 n Wednesday\, 13 May\, 2020.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-21
DTSTART;VALUE=DATE:20200518
DTEND;VALUE=DATE:20200523
DTSTAMP:20200814T121816Z
UID:Victoria-R-21
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-20
DTSTART;VALUE=DATE:20200525
DTEND;VALUE=DATE:20200530
DTSTAMP:20200814T121816Z
UID:Victoria-R-20
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-19 (Virtual PTG)
DTSTART;VALUE=DATE:20200601
DTEND;VALUE=DATE:20200606
DTSTAMP:20200814T121816Z
UID:Victoria-R-19
DESCRIPTION:Virtual PTG\n\nA virtual PTG will be held during this week. Th
 e Project Teams Gathering provides and opportunity for teams to collaborat
 e and plan\, and discuss requirements for future releases.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-18
DTSTART;VALUE=DATE:20200608
DTEND;VALUE=DATE:20200613
DTSTAMP:20200814T121816Z
UID:Victoria-R-18
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-17 (Victoria-1 milestone)
DTSTART;VALUE=DATE:20200615
DTEND;VALUE=DATE:20200620
DTSTAMP:20200814T121816Z
UID:Victoria-R-17
DESCRIPTION:Victoria-1 milestone\n\n18 June\, 2020 is the Victoria-1 miles
 tone. See project-specific notes for relevant deadlines.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-16
DTSTART;VALUE=DATE:20200622
DTEND;VALUE=DATE:20200627
DTSTAMP:20200814T121816Z
UID:Victoria-R-16
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-15
DTSTART;VALUE=DATE:20200629
DTEND;VALUE=DATE:20200704
DTSTAMP:20200814T121816Z
UID:Victoria-R-15
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-14
DTSTART;VALUE=DATE:20200706
DTEND;VALUE=DATE:20200711
DTSTAMP:20200814T121816Z
UID:Victoria-R-14
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-13
DTSTART;VALUE=DATE:20200713
DTEND;VALUE=DATE:20200718
DTSTAMP:20200814T121816Z
UID:Victoria-R-13
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-12
DTSTART;VALUE=DATE:20200720
DTEND;VALUE=DATE:20200725
DTSTAMP:20200814T121816Z
UID:Victoria-R-12
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-11 (Victoria-2 milestone)
DTSTART;VALUE=DATE:20200727
DTEND;VALUE=DATE:20200801
DTSTAMP:20200814T121816Z
UID:Victoria-R-11
DESCRIPTION:Victoria-2 milestone\n\n30 July\, 2020 is the Victoria-2 miles
 tone. See project-specific notes for relevant deadlines.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-10
DTSTART;VALUE=DATE:20200803
DTEND;VALUE=DATE:20200808
DTSTAMP:20200814T121816Z
UID:Victoria-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-9 (Ussuri Cycle-Trailing Release Deadline)
DTSTART;VALUE=DATE:20200810
DTEND;VALUE=DATE:20200815
DTSTAMP:20200814T121816Z
UID:Victoria-R-9
DESCRIPTION:Ussuri Cycle-Trailing Release Deadline\n\nAll projects followi
 ng the cycle-trailing release model must release their Ussuri deliverables
  by 13 August\, 2020.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-8
DTSTART;VALUE=DATE:20200817
DTEND;VALUE=DATE:20200822
DTSTAMP:20200814T121816Z
UID:Victoria-R-8
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-7
DTSTART;VALUE=DATE:20200824
DTEND;VALUE=DATE:20200829
DTSTAMP:20200814T121816Z
UID:Victoria-R-7
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-6 (Final release for non-client libraries)
DTSTART;VALUE=DATE:20200831
DTEND;VALUE=DATE:20200905
DTSTAMP:20200814T121816Z
UID:Victoria-R-6
DESCRIPTION:Final release for non-client libraries\n\nLibraries that are n
 ot client libraries (Oslo and others) should issue their final release dur
 ing this week. That allows to give time for last-minute changes before fea
 ture freeze.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-5 (Victoria-3 milestone\; Feature freeze\; Final releas
 e for client libraries\; Soft StringFreeze\; Requirements freeze\; Victori
 a Community Goals Completed\; Cycle Highlights)
DTSTART;VALUE=DATE:20200907
DTEND;VALUE=DATE:20200912
DTSTAMP:20200814T121816Z
UID:Victoria-R-5
DESCRIPTION:Victoria-3 milestone\n\n10 September\, 2020 is the Victoria-3 
 milestone. See project-specific notes for relevant deadlines.\n\n\n\nFeatu
 re freeze\n\nThe Victoria-3 milestone marks feature freeze for projects fo
 llowing the release:cycle-with-rc model. No featureful patch should be lan
 ded after this point. Exceptions may be granted by the project PTL.\n\n\n\
 n\n\nFinal release for client libraries\n\nClient libraries should issue t
 heir final release during this week\, to match feature freeze.\n\n\n\nSoft
  StringFreeze\n\nYou are no longer allowed to accept proposed changes cont
 aining modifications in user-facing strings. Such changes should be reject
 ed by the review team and postponed until the next series development open
 s (which should happen when RC1 is published).\n\n\n\nRequirements freeze\
 n\nAfter the Victoria-3 milestone\, only critical requirements and constra
 ints changes will be allowed. Freezing our requirements list gives package
 rs downstream an opportunity to catch up and prepare packages for everythi
 ng necessary for distributions of the upcoming release. The requirements r
 emain frozen until the stable branches are created\, with the release cand
 idates.\n\n\n\nVictoria Community Goals Completed\n\nTeams should prepare 
 their documentation for completing the community-wide goals for Victoria.\
 n\n\n\nCycle Highlights\n\nCycle highlights need to be added to the releas
 e deliverables by feature freeze to be included in any marketing release m
 essaging. Highlights may be added after this point\, but they will likely 
 only be useful for historical purposes.\n\nSee the Project Team Guide for 
 more details and instructions on adding these highlights.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-4
DTSTART;VALUE=DATE:20200914
DTEND;VALUE=DATE:20200919
DTSTAMP:20200814T121816Z
UID:Victoria-R-4
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-3 (RC1 target week\; Hard StringFreeze)
DTSTART;VALUE=DATE:20200921
DTEND;VALUE=DATE:20200926
DTSTAMP:20200814T121816Z
UID:Victoria-R-3
DESCRIPTION:RC1 target week\n\nThe week of 21 September is the target date
  for projects following the release:cycle-with-rc model to issue their fir
 st release candidate.\n\n\n\nHard StringFreeze\n\nThis happens when the RC
 1 for the project is tagged. At this point\, ideally no strings are change
 d (or added\, or removed)\, to give translators time to finish up their ef
 forts.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-2
DTSTART;VALUE=DATE:20200928
DTEND;VALUE=DATE:20201003
DTSTAMP:20200814T121816Z
UID:Victoria-R-2
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-1 (Final RCs and intermediary releases)
DTSTART;VALUE=DATE:20201005
DTEND;VALUE=DATE:20201010
DTSTAMP:20200814T121816Z
UID:Victoria-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of 5 October i
 s the last week to issue release candidates or intermediary releases befor
 e release week. During release week\, only final-release-critical releases
  will be accepted (at the discretion of the release team).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-0 (Victoria release)
DTSTART;VALUE=DATE:20201012
DTEND;VALUE=DATE:20201017
DTSTAMP:20200814T121816Z
UID:Victoria-R-0
DESCRIPTION:Victoria release\n\nThe Victoria coordinated release will happ
 en on Wednesday\, 14 October\, 2020.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R+1 (Open Infrastructure Summit)
DTSTART;VALUE=DATE:20201019
DTEND;VALUE=DATE:20201024
DTSTAMP:20200814T121816Z
UID:Victoria-R+1
DESCRIPTION:Open Infrastructure Summit\n\nThe virtual Open Infrastructure 
 Summit will take place October 19-23.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-25 (v-summit)
DTSTART;VALUE=DATE:20201019
DTEND;VALUE=DATE:20201024
DTSTAMP:20210210T202017Z
UID:Wallaby-R-25
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-24 (Virtual PTG)
DTSTART;VALUE=DATE:20201026
DTEND;VALUE=DATE:20201031
DTSTAMP:20210210T202017Z
UID:Wallaby-R-24
DESCRIPTION:Virtual PTG\n\nA virtual PTG will be held during this week. Th
 e Project Teams Gathering provides and opportunity for teams to collaborat
 e and plan\, and discuss requirements for future releases.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-23
DTSTART;VALUE=DATE:20201102
DTEND;VALUE=DATE:20201107
DTSTAMP:20210210T202017Z
UID:Wallaby-R-23
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-22
DTSTART;VALUE=DATE:20201109
DTEND;VALUE=DATE:20201114
DTSTAMP:20210210T202017Z
UID:Wallaby-R-22
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-21
DTSTART;VALUE=DATE:20201116
DTEND;VALUE=DATE:20201121
DTSTAMP:20210210T202017Z
UID:Wallaby-R-21
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-20
DTSTART;VALUE=DATE:20201123
DTEND;VALUE=DATE:20201128
DTSTAMP:20210210T202017Z
UID:Wallaby-R-20
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-19 (Wallaby-1 milestone)
DTSTART;VALUE=DATE:20201130
DTEND;VALUE=DATE:20201205
DTSTAMP:20210210T202017Z
UID:Wallaby-R-19
DESCRIPTION:Wallaby-1 milestone\n\n3 December\, 2020 is the Wallaby-1 mile
 stone. See project-specific notes for relevant deadlines.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-18
DTSTART;VALUE=DATE:20201207
DTEND;VALUE=DATE:20201212
DTSTAMP:20210210T202017Z
UID:Wallaby-R-18
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-17
DTSTART;VALUE=DATE:20201214
DTEND;VALUE=DATE:20201219
DTSTAMP:20210210T202017Z
UID:Wallaby-R-17
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-16
DTSTART;VALUE=DATE:20201221
DTEND;VALUE=DATE:20201226
DTSTAMP:20210210T202017Z
UID:Wallaby-R-16
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-15
DTSTART;VALUE=DATE:20201228
DTEND;VALUE=DATE:20210102
DTSTAMP:20210210T202017Z
UID:Wallaby-R-15
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-14
DTSTART;VALUE=DATE:20210104
DTEND;VALUE=DATE:20210109
DTSTAMP:20210210T202017Z
UID:Wallaby-R-14
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-13 (Victoria Cycle-Trailing Release Deadline)
DTSTART;VALUE=DATE:20210111
DTEND;VALUE=DATE:20210116
DTSTAMP:20210210T202017Z
UID:Wallaby-R-13
DESCRIPTION:Victoria Cycle-Trailing Release Deadline\n\nAll projects follo
 wing the cycle-trailing release model must release their Victoria delivera
 bles by 14 January\, 2021.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-12 (Wallaby-2 milestone\; Membership Freeze)
DTSTART;VALUE=DATE:20210118
DTEND;VALUE=DATE:20210123
DTSTAMP:20210210T202017Z
UID:Wallaby-R-12
DESCRIPTION:Wallaby-2 milestone\n\n21 January\, 2021 is the Wallaby-2 mile
 stone. See project-specific notes for relevant deadlines.\n\n\n\nMembershi
 p Freeze\n\nProjects must participate in at least two milestones in order 
 to be considered part of the release. Projects made official after the sec
 ond milestone\, or which fail to produce milestone releases for at least o
 ne of the first and second milestones as well as the third milestone\, are
  therefore not considered part of the release for the cycle. This does not
  apply to cycle-trailing packaging / lifecycle management projects.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-11
DTSTART;VALUE=DATE:20210125
DTEND;VALUE=DATE:20210130
DTSTAMP:20210210T202017Z
UID:Wallaby-R-11
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-10
DTSTART;VALUE=DATE:20210201
DTEND;VALUE=DATE:20210206
DTSTAMP:20210210T202017Z
UID:Wallaby-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-9
DTSTART;VALUE=DATE:20210208
DTEND;VALUE=DATE:20210213
DTSTAMP:20210210T202017Z
UID:Wallaby-R-9
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-8
DTSTART;VALUE=DATE:20210215
DTEND;VALUE=DATE:20210220
DTSTAMP:20210210T202017Z
UID:Wallaby-R-8
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-7 (Extra-ATC freeze)
DTSTART;VALUE=DATE:20210222
DTEND;VALUE=DATE:20210227
DTSTAMP:20210210T202017Z
UID:Wallaby-R-7
DESCRIPTION:Extra-ATC freeze\n\nAll contributions to OpenStack are valuabl
 e\, but some are not expressed as Gerrit code changes. That allow teams to
  list active contributors to their projects and who do not have a code con
 tribution this cycle\, and therefore won’t automatically be considered a
 n Active Technical Contributor and allowed to vote. This is done by adding
  extra-atcs to https://opendev.org/openstack/governance/src/branch/master/
 reference/projects.yaml before the Extra-ATC freeze on 25 February\, 2021.
 \n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-6 (Final release for non-client libraries)
DTSTART;VALUE=DATE:20210301
DTEND;VALUE=DATE:20210306
DTSTAMP:20210210T202017Z
UID:Wallaby-R-6
DESCRIPTION:Final release for non-client libraries\n\nLibraries that are n
 ot client libraries (Oslo and others) should issue their final release dur
 ing this week. That allows to give time for last-minute changes before fea
 ture freeze.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-5 (Wallaby-3 milestone\; Feature freeze\; Final release 
 for client libraries\; Soft StringFreeze\; Requirements freeze\; Wallaby C
 ommunity Goals Completed\; Cycle Highlights)
DTSTART;VALUE=DATE:20210308
DTEND;VALUE=DATE:20210313
DTSTAMP:20210210T202017Z
UID:Wallaby-R-5
DESCRIPTION:Wallaby-3 milestone\n\n11 March\, 2021 is the Wallaby-3 milest
 one. See project-specific notes for relevant deadlines.\n\n\n\nFeature fre
 eze\n\nThe Wallaby-3 milestone marks feature freeze for projects following
  the release:cycle-with-rc model. No featureful patch should be landed aft
 er this point. Exceptions may be granted by the project PTL.\n\n\n\n\n\nFi
 nal release for client libraries\n\nClient libraries should issue their fi
 nal release during this week\, to match feature freeze.\n\n\n\nSoft String
 Freeze\n\nYou are no longer allowed to accept proposed changes containing 
 modifications in user-facing strings. Such changes should be rejected by t
 he review team and postponed until the next series development opens (whic
 h should happen when RC1 is published).\n\n\n\nRequirements freeze\n\nAfte
 r the Wallaby-3 milestone\, only critical requirements and constraints cha
 nges will be allowed. Freezing our requirements list gives packagers downs
 tream an opportunity to catch up and prepare packages for everything neces
 sary for distributions of the upcoming release. The requirements remain fr
 ozen until the stable branches are created\, with the release candidates.\
 n\n\n\nWallaby Community Goals Completed\n\nTeams should prepare their doc
 umentation for completing the community-wide goals for Wallaby.\n\n\n\nCyc
 le Highlights\n\nCycle highlights need to be added to the release delivera
 bles by feature freeze to be included in any marketing release messaging. 
 Highlights may be added after this point\, but they will likely only be us
 eful for historical purposes.\n\nSee the Project Team Guide for more detai
 ls and instructions on adding these highlights.\n\nFor examples of previou
 s release highlights: Stein Highlights\, Train Highlights\, Ussuri Highlig
 hts\, Victoria Highlights.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-4
DTSTART;VALUE=DATE:20210315
DTEND;VALUE=DATE:20210320
DTSTAMP:20210210T202017Z
UID:Wallaby-R-4
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-3 (RC1 target week\; Hard StringFreeze)
DTSTART;VALUE=DATE:20210322
DTEND;VALUE=DATE:20210327
DTSTAMP:20210210T202017Z
UID:Wallaby-R-3
DESCRIPTION:RC1 target week\n\nThe week of 22 March\, 2021 is the target d
 ate for projects following the release:cycle-with-rc model to issue their 
 first release candidate.\n\n\n\nHard StringFreeze\n\nThis happens when the
  RC1 for the project is tagged. At this point\, ideally no strings are cha
 nged (or added\, or removed)\, to give translators time to finish up their
  efforts.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-2
DTSTART;VALUE=DATE:20210329
DTEND;VALUE=DATE:20210403
DTSTAMP:20210210T202017Z
UID:Wallaby-R-2
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-1 (Final RCs and intermediary releases)
DTSTART;VALUE=DATE:20210405
DTEND;VALUE=DATE:20210410
DTSTAMP:20210210T202017Z
UID:Wallaby-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of 5 April\, 2
 021 is the last week to issue release candidates or intermediary releases 
 before release week. During release week\, only final-release-critical rel
 eases will be accepted (at the discretion of the release team).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Wallaby R-0 (Wallaby release)
DTSTART;VALUE=DATE:20210412
DTEND;VALUE=DATE:20210417
DTSTAMP:20210210T202017Z
UID:Wallaby-R-0
DESCRIPTION:Wallaby release\n\nThe Wallaby coordinated release will happen
  on Wednesday\, 14 April\, 2021.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-24 (Virtual PTG)
DTSTART;VALUE=DATE:20210419
DTEND;VALUE=DATE:20210424
DTSTAMP:20210820T162644Z
UID:Xena-R-24
DESCRIPTION:Virtual PTG\n\nThis needs to be added to the schedule once we 
 know when the event will be\n\nA virtual PTG will be held during this week
  (Apr 19-23\, 2021). The Project Teams Gathering provides and opportunity 
 for teams to collaborate and plan\, and discuss requirements for future re
 leases.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-23
DTSTART;VALUE=DATE:20210426
DTEND;VALUE=DATE:20210501
DTSTAMP:20210820T162644Z
UID:Xena-R-23
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-22
DTSTART;VALUE=DATE:20210503
DTEND;VALUE=DATE:20210508
DTSTAMP:20210820T162644Z
UID:Xena-R-22
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-21
DTSTART;VALUE=DATE:20210510
DTEND;VALUE=DATE:20210515
DTSTAMP:20210820T162644Z
UID:Xena-R-21
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-20
DTSTART;VALUE=DATE:20210517
DTEND;VALUE=DATE:20210522
DTSTAMP:20210820T162644Z
UID:Xena-R-20
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-19 (Xena-1 milestone)
DTSTART;VALUE=DATE:20210524
DTEND;VALUE=DATE:20210529
DTSTAMP:20210820T162644Z
UID:Xena-R-19
DESCRIPTION:Xena-1 milestone\n\n27 May\, 2021 is the Xena-1 milestone. See
  project-specific notes for relevant deadlines.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-18
DTSTART;VALUE=DATE:20210531
DTEND;VALUE=DATE:20210605
DTSTAMP:20210820T162644Z
UID:Xena-R-18
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-17
DTSTART;VALUE=DATE:20210607
DTEND;VALUE=DATE:20210612
DTSTAMP:20210820T162644Z
UID:Xena-R-17
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-16
DTSTART;VALUE=DATE:20210614
DTEND;VALUE=DATE:20210619
DTSTAMP:20210820T162644Z
UID:Xena-R-16
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-15
DTSTART;VALUE=DATE:20210621
DTEND;VALUE=DATE:20210626
DTSTAMP:20210820T162644Z
UID:Xena-R-15
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-14 (Wallaby Cycle-Trailing Release Deadline)
DTSTART;VALUE=DATE:20210628
DTEND;VALUE=DATE:20210703
DTSTAMP:20210820T162644Z
UID:Xena-R-14
DESCRIPTION:Wallaby Cycle-Trailing Release Deadline\n\nAll projects follow
 ing the cycle-trailing release model must release their Wallaby deliverabl
 es by 02 July\, 2021.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-13
DTSTART;VALUE=DATE:20210705
DTEND;VALUE=DATE:20210710
DTSTAMP:20210820T162644Z
UID:Xena-R-13
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-12 (Xena-2 milestone\; Membership Freeze)
DTSTART;VALUE=DATE:20210712
DTEND;VALUE=DATE:20210717
DTSTAMP:20210820T162644Z
UID:Xena-R-12
DESCRIPTION:Xena-2 milestone\n\n15 July\, 2021 is the Xena-2 milestone. Se
 e project-specific notes for relevant deadlines.\n\n\n\nMembership Freeze\
 n\nProjects must participate in at least two milestones in order to be con
 sidered part of the release. Projects made official after the second miles
 tone\, or which fail to produce milestone releases for at least one of the
  first and second milestones as well as the third milestone\, are therefor
 e not considered part of the release for the cycle. This does not apply to
  cycle-trailing packaging / lifecycle management projects.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-11
DTSTART;VALUE=DATE:20210719
DTEND;VALUE=DATE:20210724
DTSTAMP:20210820T162644Z
UID:Xena-R-11
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-10
DTSTART;VALUE=DATE:20210726
DTEND;VALUE=DATE:20210731
DTSTAMP:20210820T162644Z
UID:Xena-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-9
DTSTART;VALUE=DATE:20210802
DTEND;VALUE=DATE:20210807
DTSTAMP:20210820T162644Z
UID:Xena-R-9
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-8 (Extra-ATC freeze)
DTSTART;VALUE=DATE:20210809
DTEND;VALUE=DATE:20210814
DTSTAMP:20210820T162644Z
UID:Xena-R-8
DESCRIPTION:Extra-ATC freeze\n\nAll contributions to OpenStack are valuabl
 e\, but some are not expressed as Gerrit code changes. That allow teams to
  list active contributors to their projects and who do not have a code con
 tribution this cycle\, and therefore won’t automatically be considered a
 n Active Technical Contributor and allowed to vote. This is done by adding
  extra-atcs to https://opendev.org/openstack/governance/src/branch/master/
 reference/projects.yaml before the Extra-ATC freeze on 13 August\, 2021.\n
 \n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-7
DTSTART;VALUE=DATE:20210816
DTEND;VALUE=DATE:20210821
DTSTAMP:20210820T162644Z
UID:Xena-R-7
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-6 (Final release for non-client libraries)
DTSTART;VALUE=DATE:20210823
DTEND;VALUE=DATE:20210828
DTSTAMP:20210820T162644Z
UID:Xena-R-6
DESCRIPTION:Final release for non-client libraries\n\nLibraries that are n
 ot client libraries (Oslo and others) should issue their final release dur
 ing this week. That allows to give time for last-minute changes before fea
 ture freeze.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-5 (Xena-3 milestone\; Feature freeze\; Final release for cl
 ient libraries\; Soft StringFreeze\; Requirements freeze\; Xena Community 
 Goals Completed\; Cycle Highlights)
DTSTART;VALUE=DATE:20210830
DTEND;VALUE=DATE:20210904
DTSTAMP:20210820T162644Z
UID:Xena-R-5
DESCRIPTION:Xena-3 milestone\n\n02 September\, 2021 is the Xena-3 mileston
 e. See project-specific notes for relevant deadlines.\n\n\n\nFeature freez
 e\n\nThe Xena-3 milestone marks feature freeze for projects following the 
 release:cycle-with-rc model. No featureful patch should be landed after th
 is point. Exceptions may be granted by the project PTL.\n\n\n\n\n\nFinal r
 elease for client libraries\n\nClient libraries should issue their final r
 elease during this week\, to match feature freeze.\n\n\n\nSoft StringFreez
 e\n\nYou are no longer allowed to accept proposed changes containing modif
 ications in user-facing strings. Such changes should be rejected by the re
 view team and postponed until the next series development opens (which sho
 uld happen when RC1 is published).\n\n\n\nRequirements freeze\n\nAfter the
  Xena-3 milestone\, only critical requirements and constraints changes wil
 l be allowed. Freezing our requirements list gives packagers downstream an
  opportunity to catch up and prepare packages for everything necessary for
  distributions of the upcoming release. The requirements remain frozen unt
 il the stable branches are created\, with the release candidates.\n\n\n\nX
 ena Community Goals Completed\n\nTeams should prepare their documentation 
 for completing the community-wide goals for Xena.\n\n\n\nCycle Highlights\
 n\nCycle highlights need to be added to the release deliverables by featur
 e freeze to be included in any marketing release messaging. Highlights may
  be added after this point\, but they will likely only be useful for histo
 rical purposes.\n\nSee the Project Team Guide for more details and instruc
 tions on adding these highlights.\n\nFor examples of previous release high
 lights: Stein Highlights\, Train Highlights\, Ussuri Highlights\, Victoria
  Highlights. Wallaby Highlights.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-4
DTSTART;VALUE=DATE:20210906
DTEND;VALUE=DATE:20210911
DTSTAMP:20210820T162644Z
UID:Xena-R-4
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-3 (RC1 target week\; Hard StringFreeze)
DTSTART;VALUE=DATE:20210913
DTEND;VALUE=DATE:20210918
DTSTAMP:20210820T162644Z
UID:Xena-R-3
DESCRIPTION:RC1 target week\n\nThe week of 13 September\, 2021 is the targ
 et date for projects following the release:cycle-with-rc model to issue th
 eir first release candidate.\n\n\n\nHard StringFreeze\n\nThis happens when
  the RC1 for the project is tagged. At this point\, ideally no strings are
  changed (or added\, or removed)\, to give translators time to finish up t
 heir efforts.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-2
DTSTART;VALUE=DATE:20210920
DTEND;VALUE=DATE:20210925
DTSTAMP:20210820T162644Z
UID:Xena-R-2
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-1 (Final RCs and intermediary releases)
DTSTART;VALUE=DATE:20210927
DTEND;VALUE=DATE:20211002
DTSTAMP:20210820T162644Z
UID:Xena-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of 27 Septembe
 r\, 2021 is the last week to issue release candidates or intermediary rele
 ases before release week. During release week\, only final-release-critica
 l releases will be accepted (at the discretion of the release team).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Xena R-0 (Xena release)
DTSTART;VALUE=DATE:20211004
DTEND;VALUE=DATE:20211009
DTSTAMP:20210820T162644Z
UID:Xena-R-0
DESCRIPTION:Xena release\n\nThe Xena coordinated release will happen on We
 dnesday\, 06 October\, 2021.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R-24
DTSTART;VALUE=DATE:20211011
DTEND;VALUE=DATE:20211016
DTSTAMP:20220315T154304Z
UID:Yoga-R-24
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R-23 (Virtual PTG)
DTSTART;VALUE=DATE:20211018
DTEND;VALUE=DATE:20211023
DTSTAMP:20220315T154304Z
UID:Yoga-R-23
DESCRIPTION:Virtual PTG\n\nThis needs to be added to the schedule once we 
 know when the event will be\n\nA virtual PTG will be held during this week
  (October 18-22\, 2021). The Project Teams Gathering provides and opportun
 ity for teams to collaborate and plan\, and discuss requirements for futur
 e releases.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R-22
DTSTART;VALUE=DATE:20211025
DTEND;VALUE=DATE:20211030
DTSTAMP:20220315T154304Z
UID:Yoga-R-22
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R-21
DTSTART;VALUE=DATE:20211101
DTEND;VALUE=DATE:20211106
DTSTAMP:20220315T154304Z
UID:Yoga-R-21
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R-20
DTSTART;VALUE=DATE:20211108
DTEND;VALUE=DATE:20211113
DTSTAMP:20220315T154304Z
UID:Yoga-R-20
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R-19 (Yoga-1 milestone)
DTSTART;VALUE=DATE:20211115
DTEND;VALUE=DATE:20211120
DTSTAMP:20220315T154304Z
UID:Yoga-R-19
DESCRIPTION:Yoga-1 milestone\n\n18 November\, 2021 is the Yoga-1 milestone
 . See project-specific notes for relevant deadlines.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R-18
DTSTART;VALUE=DATE:20211122
DTEND;VALUE=DATE:20211127
DTSTAMP:20220315T154304Z
UID:Yoga-R-18
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R-17
DTSTART;VALUE=DATE:20211129
DTEND;VALUE=DATE:20211204
DTSTAMP:20220315T154304Z
UID:Yoga-R-17
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R-16
DTSTART;VALUE=DATE:20211206
DTEND;VALUE=DATE:20211211
DTSTAMP:20220315T154304Z
UID:Yoga-R-16
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R-15 (Xena Cycle-Trailing Release Deadline)
DTSTART;VALUE=DATE:20211213
DTEND;VALUE=DATE:20211218
DTSTAMP:20220315T154304Z
UID:Yoga-R-15
DESCRIPTION:Xena Cycle-Trailing Release Deadline\n\nAll projects following
  the cycle-trailing release model must release their Xena deliverables by 
 16 December\, 2021.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R-14
DTSTART;VALUE=DATE:20211220
DTEND;VALUE=DATE:20211225
DTSTAMP:20220315T154304Z
UID:Yoga-R-14
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R-13
DTSTART;VALUE=DATE:20211227
DTEND;VALUE=DATE:20220101
DTSTAMP:20220315T154304Z
UID:Yoga-R-13
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R-12 (Yoga-2 milestone\; Membership Freeze)
DTSTART;VALUE=DATE:20220103
DTEND;VALUE=DATE:20220108
DTSTAMP:20220315T154304Z
UID:Yoga-R-12
DESCRIPTION:Yoga-2 milestone\n\n06 January\, 2022 is the Yoga-2 milestone.
  See project-specific notes for relevant deadlines.\n\n\n\nMembership Free
 ze\n\nProjects must participate in at least two milestones in order to be 
 considered part of the release. Projects made official after the second mi
 lestone\, or which fail to produce milestone releases for at least one of 
 the first and second milestones as well as the third milestone\, are there
 fore not considered part of the release for the cycle. This does not apply
  to cycle-trailing packaging / lifecycle management projects.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R-11
DTSTART;VALUE=DATE:20220110
DTEND;VALUE=DATE:20220115
DTSTAMP:20220315T154304Z
UID:Yoga-R-11
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R-10
DTSTART;VALUE=DATE:20220117
DTEND;VALUE=DATE:20220122
DTSTAMP:20220315T154304Z
UID:Yoga-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R-9
DTSTART;VALUE=DATE:20220124
DTEND;VALUE=DATE:20220129
DTSTAMP:20220315T154304Z
UID:Yoga-R-9
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R-8
DTSTART;VALUE=DATE:20220131
DTEND;VALUE=DATE:20220205
DTSTAMP:20220315T154304Z
UID:Yoga-R-8
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R-7 (Extra-ATC freeze)
DTSTART;VALUE=DATE:20220207
DTEND;VALUE=DATE:20220212
DTSTAMP:20220315T154304Z
UID:Yoga-R-7
DESCRIPTION:Extra-ATC freeze\n\nAll contributions to OpenStack are valuabl
 e\, but some are not expressed as Gerrit code changes. That allow teams to
  list active contributors to their projects and who do not have a code con
 tribution this cycle\, and therefore won’t automatically be considered a
 n Active Technical Contributor and allowed to vote. This is done by adding
  extra-atcs to https://opendev.org/openstack/governance/src/branch/master/
 reference/projects.yaml before the Extra-ATC freeze on 10 February\, 2022.
 \n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R-6 (Final release for non-client libraries)
DTSTART;VALUE=DATE:20220214
DTEND;VALUE=DATE:20220219
DTSTAMP:20220315T154304Z
UID:Yoga-R-6
DESCRIPTION:Final release for non-client libraries\n\nLibraries that are n
 ot client libraries (Oslo and others) should issue their final release dur
 ing this week. That allows to give time for last-minute changes before fea
 ture freeze.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R-5 (Yoga-3 milestone\; Feature freeze\; Final release for cl
 ient libraries\; Soft StringFreeze\; Requirements freeze\; Yoga Community 
 Goals Completed\; Cycle Highlights)
DTSTART;VALUE=DATE:20220221
DTEND;VALUE=DATE:20220226
DTSTAMP:20220315T154304Z
UID:Yoga-R-5
DESCRIPTION:Yoga-3 milestone\n\n24 February\, 2022 is the Yoga-3 milestone
 . See project-specific notes for relevant deadlines.\n\n\n\nFeature freeze
 \n\nThe Yoga-3 milestone marks feature freeze for projects following the r
 elease:cycle-with-rc model. No featureful patch should be landed after thi
 s point. Exceptions may be granted by the project PTL.\n\n\n\n\n\nFinal re
 lease for client libraries\n\nClient libraries should issue their final re
 lease during this week\, to match feature freeze.\n\n\n\nSoft StringFreeze
 \n\nYou are no longer allowed to accept proposed changes containing modifi
 cations in user-facing strings. Such changes should be rejected by the rev
 iew team and postponed until the next series development opens (which shou
 ld happen when RC1 is published).\n\n\n\nRequirements freeze\n\nAfter the 
 Yoga-3 milestone\, only critical requirements and constraints changes will
  be allowed. Freezing our requirements list gives packagers downstream an 
 opportunity to catch up and prepare packages for everything necessary for 
 distributions of the upcoming release. The requirements remain frozen unti
 l the stable branches are created\, with the release candidates.\n\n\n\nYo
 ga Community Goals Completed\n\nTeams should prepare their documentation f
 or completing the community-wide goals for Yoga.\n\n\n\nCycle Highlights\n
 \nCycle highlights need to be added to the release deliverables by feature
  freeze to be included in any marketing release messaging. Highlights may 
 be added after this point\, but they will likely only be useful for histor
 ical purposes.\n\nSee the Project Team Guide for more details and instruct
 ions on adding these highlights.\n\nFor examples of previous release highl
 ights: Stein Highlights\, Train Highlights\, Ussuri Highlights\, Victoria 
 Highlights. Wallaby Highlights. Xena Highlights.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R-4
DTSTART;VALUE=DATE:20220228
DTEND;VALUE=DATE:20220305
DTSTAMP:20220315T154304Z
UID:Yoga-R-4
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R-3 (RC1 target week\; Hard StringFreeze)
DTSTART;VALUE=DATE:20220307
DTEND;VALUE=DATE:20220312
DTSTAMP:20220315T154304Z
UID:Yoga-R-3
DESCRIPTION:RC1 target week\n\nThe week of 07 March\, 2022 is the target d
 ate for projects following the release:cycle-with-rc model to issue their 
 first release candidate.\n\n\n\nHard StringFreeze\n\nThis happens when the
  RC1 for the project is tagged. At this point\, ideally no strings are cha
 nged (or added\, or removed)\, to give translators time to finish up their
  efforts.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R-2
DTSTART;VALUE=DATE:20220314
DTEND;VALUE=DATE:20220319
DTSTAMP:20220315T154304Z
UID:Yoga-R-2
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R-1 (Final RCs and intermediary releases)
DTSTART;VALUE=DATE:20220321
DTEND;VALUE=DATE:20220326
DTSTAMP:20220315T154304Z
UID:Yoga-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of 21st-25th M
 arch\, 2022 is the last week to issue release candidates or intermediary r
 eleases before release week. During release week\, only final-release-crit
 ical releases will be accepted (at the discretion of the release team).\n\
 n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Yoga R+0 (Yoga release)
DTSTART;VALUE=DATE:20220328
DTEND;VALUE=DATE:20220331
DTSTAMP:20220315T154304Z
UID:Yoga-R+0
DESCRIPTION:Yoga release\n\nThe Yoga coordinated release will happen on We
 dnesday\, 30 March\, 2022.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-26 (Virtual PTG)
DTSTART;VALUE=DATE:20220404
DTEND;VALUE=DATE:20220409
DTSTAMP:20220624T141439Z
UID:Zed-R-26
DESCRIPTION:Virtual PTG\n\nThis needs to be added to the schedule once we 
 know when the event will be\n\nA virtual PTG will be held during this week
  (April 04-08\, 2022). The Project Teams Gathering provides an opportunity
  for teams to collaborate and plan\, and discuss requirements for future r
 eleases.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-25
DTSTART;VALUE=DATE:20220411
DTEND;VALUE=DATE:20220416
DTSTAMP:20220624T141439Z
UID:Zed-R-25
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-24
DTSTART;VALUE=DATE:20220418
DTEND;VALUE=DATE:20220423
DTSTAMP:20220624T141439Z
UID:Zed-R-24
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-23
DTSTART;VALUE=DATE:20220425
DTEND;VALUE=DATE:20220430
DTSTAMP:20220624T141439Z
UID:Zed-R-23
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-22
DTSTART;VALUE=DATE:20220502
DTEND;VALUE=DATE:20220507
DTSTAMP:20220624T141439Z
UID:Zed-R-22
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-21
DTSTART;VALUE=DATE:20220509
DTEND;VALUE=DATE:20220514
DTSTAMP:20220624T141439Z
UID:Zed-R-21
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-20 (Zed-1 milestone)
DTSTART;VALUE=DATE:20220516
DTEND;VALUE=DATE:20220521
DTSTAMP:20220624T141439Z
UID:Zed-R-20
DESCRIPTION:Zed-1 milestone\n\n19 May\, 2022 is the Zed-1 milestone. See p
 roject-specific notes for relevant deadlines.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-19
DTSTART;VALUE=DATE:20220523
DTEND;VALUE=DATE:20220528
DTSTAMP:20220624T141439Z
UID:Zed-R-19
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-18
DTSTART;VALUE=DATE:20220530
DTEND;VALUE=DATE:20220604
DTSTAMP:20220624T141439Z
UID:Zed-R-18
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-17 (Open Infrastructure Summit)
DTSTART;VALUE=DATE:20220606
DTEND;VALUE=DATE:20220611
DTSTAMP:20220624T141439Z
UID:Zed-R-17
DESCRIPTION:Open Infrastructure Summit\n\nThe Open Infrastructure Summit h
 appens in this week\, 7th - 9th June\, 2022 in Berlin\, Germany. See detai
 ls at the official OpenInfra Summit Page.\n\n\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-16
DTSTART;VALUE=DATE:20220613
DTEND;VALUE=DATE:20220618
DTSTAMP:20220624T141439Z
UID:Zed-R-16
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-15 (Yoga Cycle-Trailing Release Deadline)
DTSTART;VALUE=DATE:20220620
DTEND;VALUE=DATE:20220625
DTSTAMP:20220624T141439Z
UID:Zed-R-15
DESCRIPTION:Yoga Cycle-Trailing Release Deadline\n\nAll projects following
  the cycle-trailing release model must release their Yoga deliverables by 
 23 June\, 2022.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-14
DTSTART;VALUE=DATE:20220627
DTEND;VALUE=DATE:20220702
DTSTAMP:20220624T141439Z
UID:Zed-R-14
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-13
DTSTART;VALUE=DATE:20220704
DTEND;VALUE=DATE:20220709
DTSTAMP:20220624T141439Z
UID:Zed-R-13
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-12 (Zed-2 milestone\; Membership Freeze)
DTSTART;VALUE=DATE:20220711
DTEND;VALUE=DATE:20220716
DTSTAMP:20220624T141439Z
UID:Zed-R-12
DESCRIPTION:Zed-2 milestone\n\n14 July\, 2022 is the Zed-2 milestone. See 
 project-specific notes for relevant deadlines.\n\n\n\nMembership Freeze\n\
 nProjects must participate in at least two milestones in order to be consi
 dered part of the release. Projects made official after the second milesto
 ne\, or which fail to produce milestone releases for at least one of the f
 irst and second milestones as well as the third milestone\, are therefore 
 not considered part of the release for the cycle. This does not apply to c
 ycle-trailing packaging / lifecycle management projects.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-11
DTSTART;VALUE=DATE:20220718
DTEND;VALUE=DATE:20220723
DTSTAMP:20220624T141439Z
UID:Zed-R-11
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-10
DTSTART;VALUE=DATE:20220725
DTEND;VALUE=DATE:20220730
DTSTAMP:20220624T141439Z
UID:Zed-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-9
DTSTART;VALUE=DATE:20220801
DTEND;VALUE=DATE:20220806
DTSTAMP:20220624T141439Z
UID:Zed-R-9
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-8
DTSTART;VALUE=DATE:20220808
DTEND;VALUE=DATE:20220813
DTSTAMP:20220624T141439Z
UID:Zed-R-8
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-7 (Extra-ATC freeze)
DTSTART;VALUE=DATE:20220815
DTEND;VALUE=DATE:20220820
DTSTAMP:20220624T141439Z
UID:Zed-R-7
DESCRIPTION:Extra-ATC freeze\n\nAll contributions to OpenStack are valuabl
 e\, but some are not expressed as Gerrit code changes. That allow teams to
  list active contributors to their projects and who do not have a code con
 tribution this cycle\, and therefore won’t automatically be considered a
 n Active Technical Contributor and allowed to vote. This is done by adding
  extra-atcs to https://opendev.org/openstack/governance/src/branch/master/
 reference/projects.yaml before the Extra-ATC freeze on 18 August\, 2022.\n
 \n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-6 (Final release for non-client libraries)
DTSTART;VALUE=DATE:20220822
DTEND;VALUE=DATE:20220827
DTSTAMP:20220624T141439Z
UID:Zed-R-6
DESCRIPTION:Final release for non-client libraries\n\nLibraries that are n
 ot client libraries (Oslo and others) should issue their final release dur
 ing this week. That allows to give time for last-minute changes before fea
 ture freeze.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-5 (Zed-3 milestone\; Feature freeze\; Final release for clie
 nt libraries\; Soft StringFreeze\; Requirements freeze\; Cycle Highlights)
DTSTART;VALUE=DATE:20220829
DTEND;VALUE=DATE:20220903
DTSTAMP:20220624T141439Z
UID:Zed-R-5
DESCRIPTION:Zed-3 milestone\n\n01 September\, 2022 is the Zed-3 milestone.
  See project-specific notes for relevant deadlines.\n\n\n\nFeature freeze\
 n\nThe Zed-3 milestone marks feature freeze for projects following the rel
 ease:cycle-with-rc model. No featureful patch should be landed after this 
 point. Exceptions may be granted by the project PTL.\n\n\n\n\n\nFinal rele
 ase for client libraries\n\nClient libraries should issue their final rele
 ase during this week\, to match feature freeze.\n\n\n\nSoft StringFreeze\n
 \nYou are no longer allowed to accept proposed changes containing modifica
 tions in user-facing strings. Such changes should be rejected by the revie
 w team and postponed until the next series development opens (which should
  happen when RC1 is published).\n\n\n\nRequirements freeze\n\nAfter the Ze
 d-3 milestone\, only critical requirements and constraints changes will be
  allowed. Freezing our requirements list gives packagers downstream an opp
 ortunity to catch up and prepare packages for everything necessary for dis
 tributions of the upcoming release. The requirements remain frozen until t
 he stable branches are created\, with the release candidates.\n\n\n\nCycle
  Highlights\n\nCycle highlights need to be added to the release deliverabl
 es by feature freeze to be included in any marketing release messaging. Hi
 ghlights may be added after this point\, but they will likely only be usef
 ul for historical purposes.\n\nSee the Project Team Guide for more details
  and instructions on adding these highlights.\n\nFor examples of previous 
 release highlights: Stein Highlights\, Train Highlights\, Ussuri Highlight
 s\, Victoria Highlights. Wallaby Highlights. Xena Highlights. Yoga Highlig
 hts.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-4
DTSTART;VALUE=DATE:20220905
DTEND;VALUE=DATE:20220910
DTSTAMP:20220624T141439Z
UID:Zed-R-4
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-3 (RC1 target week\; Hard StringFreeze)
DTSTART;VALUE=DATE:20220912
DTEND;VALUE=DATE:20220917
DTSTAMP:20220624T141439Z
UID:Zed-R-3
DESCRIPTION:RC1 target week\n\nThe week of 12 September\, 2022 is the targ
 et date for projects following the release:cycle-with-rc model to issue th
 eir first release candidate.\n\n\n\nHard StringFreeze\n\nThis happens when
  the RC1 for the project is tagged. At this point\, ideally no strings are
  changed (or added\, or removed)\, to give translators time to finish up t
 heir efforts.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-2
DTSTART;VALUE=DATE:20220919
DTEND;VALUE=DATE:20220924
DTSTAMP:20220624T141439Z
UID:Zed-R-2
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R-1 (Final RCs and intermediary releases)
DTSTART;VALUE=DATE:20220926
DTEND;VALUE=DATE:20221001
DTSTAMP:20220624T141439Z
UID:Zed-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of 26th - 30th
  September\, 2022 is the last week to issue release candidates or intermed
 iary releases before release week. During release week\, only final-releas
 e-critical releases will be accepted (at the discretion of the release tea
 m).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Zed R+0 (Zed release)
DTSTART;VALUE=DATE:20221003
DTEND;VALUE=DATE:20221008
DTSTAMP:20220624T141439Z
UID:Zed-R+0
DESCRIPTION:Zed release\n\nThe Zed coordinated release will happen on Wedn
 esday\, 05 October\, 2022.\n\n
END:VEVENT
END:VCALENDAR