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