BEGIN:VCALENDAR
PRODID:-//releases.openstack.org//EN
X-WR-CALNAME:Hibiscus schedule
BEGIN:VEVENT
SUMMARY:Hibiscus R-25
DTSTART;VALUE=DATE:20260406
DTEND;VALUE=DATE:20260411
DTSTAMP:20260114T140209Z
UID:Hibiscus-R-25
END:VEVENT
BEGIN:VEVENT
SUMMARY:Hibiscus R-24
DTSTART;VALUE=DATE:20260413
DTEND;VALUE=DATE:20260418
DTSTAMP:20260114T140209Z
UID:Hibiscus-R-24
END:VEVENT
BEGIN:VEVENT
SUMMARY:Hibiscus R-23
DTSTART;VALUE=DATE:20260420
DTEND;VALUE=DATE:20260425
DTSTAMP:20260114T140209Z
UID:Hibiscus-R-23
END:VEVENT
BEGIN:VEVENT
SUMMARY:Hibiscus R-22
DTSTART;VALUE=DATE:20260427
DTEND;VALUE=DATE:20260502
DTSTAMP:20260114T140209Z
UID:Hibiscus-R-22
END:VEVENT
BEGIN:VEVENT
SUMMARY:Hibiscus R-21
DTSTART;VALUE=DATE:20260504
DTEND;VALUE=DATE:20260509
DTSTAMP:20260114T140209Z
UID:Hibiscus-R-21
END:VEVENT
BEGIN:VEVENT
SUMMARY:Hibiscus R-20 (Hibiscus-1 milestone)
DTSTART;VALUE=DATE:20260511
DTEND;VALUE=DATE:20260516
DTSTAMP:20260114T140209Z
UID:Hibiscus-R-20
DESCRIPTION:Hibiscus-1 milestone\n\nMay 14\, 2026 is the Hibiscus-1 milest
 one. See project-specific notes for relevant deadlines.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Hibiscus R-19
DTSTART;VALUE=DATE:20260518
DTEND;VALUE=DATE:20260523
DTSTAMP:20260114T140209Z
UID:Hibiscus-R-19
END:VEVENT
BEGIN:VEVENT
SUMMARY:Hibiscus R-18
DTSTART;VALUE=DATE:20260525
DTEND;VALUE=DATE:20260530
DTSTAMP:20260114T140209Z
UID:Hibiscus-R-18
END:VEVENT
BEGIN:VEVENT
SUMMARY:Hibiscus R-17 (2026.1 Gazpacho Cycle-Trailing Release Deadline)
DTSTART;VALUE=DATE:20260601
DTEND;VALUE=DATE:20260606
DTSTAMP:20260114T140209Z
UID:Hibiscus-R-17
DESCRIPTION:2026.1 Gazpacho Cycle-Trailing Release Deadline\n\nAll project
 s following the cycle-trailing release model must release their 2026.1 Gaz
 pacho deliverables by June 4\, 2026.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Hibiscus R-16
DTSTART;VALUE=DATE:20260608
DTEND;VALUE=DATE:20260613
DTSTAMP:20260114T140209Z
UID:Hibiscus-R-16
END:VEVENT
BEGIN:VEVENT
SUMMARY:Hibiscus R-15
DTSTART;VALUE=DATE:20260615
DTEND;VALUE=DATE:20260620
DTSTAMP:20260114T140209Z
UID:Hibiscus-R-15
END:VEVENT
BEGIN:VEVENT
SUMMARY:Hibiscus R-14
DTSTART;VALUE=DATE:20260622
DTEND;VALUE=DATE:20260627
DTSTAMP:20260114T140209Z
UID:Hibiscus-R-14
END:VEVENT
BEGIN:VEVENT
SUMMARY:Hibiscus R-13 (Hibiscus-2 milestone\; Membership Freeze)
DTSTART;VALUE=DATE:20260629
DTEND;VALUE=DATE:20260704
DTSTAMP:20260114T140209Z
UID:Hibiscus-R-13
DESCRIPTION:Hibiscus-2 milestone\n\nJuly 2\, 2026 is the Hibiscus-2 milest
 one. 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 considered part of the release. Projects made official after the secon
 d 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 t
 herefore not considered part of the release for the cycle. This does not a
 pply to cycle-trailing packaging / lifecycle management projects.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Hibiscus R-12
DTSTART;VALUE=DATE:20260706
DTEND;VALUE=DATE:20260711
DTSTAMP:20260114T140209Z
UID:Hibiscus-R-12
END:VEVENT
BEGIN:VEVENT
SUMMARY:Hibiscus R-11
DTSTART;VALUE=DATE:20260713
DTEND;VALUE=DATE:20260718
DTSTAMP:20260114T140209Z
UID:Hibiscus-R-11
END:VEVENT
BEGIN:VEVENT
SUMMARY:Hibiscus R-10
DTSTART;VALUE=DATE:20260720
DTEND;VALUE=DATE:20260725
DTSTAMP:20260114T140209Z
UID:Hibiscus-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Hibiscus R-9
DTSTART;VALUE=DATE:20260727
DTEND;VALUE=DATE:20260801
DTSTAMP:20260114T140209Z
UID:Hibiscus-R-9
END:VEVENT
BEGIN:VEVENT
SUMMARY:Hibiscus R-8
DTSTART;VALUE=DATE:20260803
DTEND;VALUE=DATE:20260808
DTSTAMP:20260114T140209Z
UID:Hibiscus-R-8
END:VEVENT
BEGIN:VEVENT
SUMMARY:Hibiscus R-7 (Extra-AC freeze)
DTSTART;VALUE=DATE:20260810
DTEND;VALUE=DATE:20260815
DTSTAMP:20260114T140209Z
UID:Hibiscus-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:Hibiscus R-6 (Final release for non-client libraries)
DTSTART;VALUE=DATE:20260817
DTEND;VALUE=DATE:20260822
DTSTAMP:20260114T140209Z
UID:Hibiscus-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:Hibiscus R-5 (Hibiscus-3 milestone\; Feature freeze\; Final releas
 e for client libraries\; Soft StringFreeze\; Requirements freeze)
DTSTART;VALUE=DATE:20260824
DTEND;VALUE=DATE:20260829
DTSTAMP:20260114T140209Z
UID:Hibiscus-R-5
DESCRIPTION:Hibiscus-3 milestone\n\nAugust 27\, 2026 is the Hibiscus-3 mil
 estone. See project-specific notes for relevant deadlines.\n\n\n\nFeature 
 freeze\n\nThe Hibiscus-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 Hibiscus-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:Hibiscus R-4 (Cycle Highlights)
DTSTART;VALUE=DATE:20260831
DTEND;VALUE=DATE:20260905
DTSTAMP:20260114T140209Z
UID:Hibiscus-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: 2025.1 Epoxy Highlights. 2025.
 2 Flamingo Highlights.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Hibiscus R-3 (RC1 target week\; Hard StringFreeze)
DTSTART;VALUE=DATE:20260907
DTEND;VALUE=DATE:20260912
DTSTAMP:20260114T140209Z
UID:Hibiscus-R-3
DESCRIPTION:RC1 target week\n\nThe week of September 7\, 2026 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:Hibiscus R-2
DTSTART;VALUE=DATE:20260914
DTEND;VALUE=DATE:20260919
DTSTAMP:20260114T140209Z
UID:Hibiscus-R-2
END:VEVENT
BEGIN:VEVENT
SUMMARY:Hibiscus R-1 (Final RCs and intermediary releases)
DTSTART;VALUE=DATE:20260921
DTEND;VALUE=DATE:20260926
DTSTAMP:20260114T140209Z
UID:Hibiscus-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of September 2
 1\, 2026 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:Hibiscus R+0 (2026.2 Hibiscus release)
DTSTART;VALUE=DATE:20260928
DTEND;VALUE=DATE:20261003
DTSTAMP:20260114T140209Z
UID:Hibiscus-R+0
DESCRIPTION:2026.2 Hibiscus release\n\nThe 2026.2 Hibiscus coordinated rel
 ease will happen on Wednesday\, September 30\, 2026.\n\n
END:VEVENT
END:VCALENDAR