BEGIN:VCALENDAR
PRODID:-//releases.openstack.org//EN
X-WR-CALNAME:Caracal schedule
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
END:VCALENDAR