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