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