BEGIN:VCALENDAR
PRODID:-//releases.openstack.org//EN
X-WR-CALNAME:Victoria schedule
BEGIN:VEVENT
SUMMARY:Victoria R-21
DTSTART;VALUE=DATE:20200518
DTEND;VALUE=DATE:20200523
DTSTAMP:20200814T121816Z
UID:Victoria-R-21
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-20
DTSTART;VALUE=DATE:20200525
DTEND;VALUE=DATE:20200530
DTSTAMP:20200814T121816Z
UID:Victoria-R-20
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-19 (Virtual PTG)
DTSTART;VALUE=DATE:20200601
DTEND;VALUE=DATE:20200606
DTSTAMP:20200814T121816Z
UID:Victoria-R-19
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:Victoria R-18
DTSTART;VALUE=DATE:20200608
DTEND;VALUE=DATE:20200613
DTSTAMP:20200814T121816Z
UID:Victoria-R-18
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-17 (Victoria-1 milestone)
DTSTART;VALUE=DATE:20200615
DTEND;VALUE=DATE:20200620
DTSTAMP:20200814T121816Z
UID:Victoria-R-17
DESCRIPTION:Victoria-1 milestone\n\n18 June\, 2020 is the Victoria-1 miles
 tone. See project-specific notes for relevant deadlines.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-16
DTSTART;VALUE=DATE:20200622
DTEND;VALUE=DATE:20200627
DTSTAMP:20200814T121816Z
UID:Victoria-R-16
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-15
DTSTART;VALUE=DATE:20200629
DTEND;VALUE=DATE:20200704
DTSTAMP:20200814T121816Z
UID:Victoria-R-15
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-14
DTSTART;VALUE=DATE:20200706
DTEND;VALUE=DATE:20200711
DTSTAMP:20200814T121816Z
UID:Victoria-R-14
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-13
DTSTART;VALUE=DATE:20200713
DTEND;VALUE=DATE:20200718
DTSTAMP:20200814T121816Z
UID:Victoria-R-13
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-12
DTSTART;VALUE=DATE:20200720
DTEND;VALUE=DATE:20200725
DTSTAMP:20200814T121816Z
UID:Victoria-R-12
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-11 (Victoria-2 milestone)
DTSTART;VALUE=DATE:20200727
DTEND;VALUE=DATE:20200801
DTSTAMP:20200814T121816Z
UID:Victoria-R-11
DESCRIPTION:Victoria-2 milestone\n\n30 July\, 2020 is the Victoria-2 miles
 tone. See project-specific notes for relevant deadlines.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-10
DTSTART;VALUE=DATE:20200803
DTEND;VALUE=DATE:20200808
DTSTAMP:20200814T121816Z
UID:Victoria-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-9 (Ussuri Cycle-Trailing Release Deadline)
DTSTART;VALUE=DATE:20200810
DTEND;VALUE=DATE:20200815
DTSTAMP:20200814T121816Z
UID:Victoria-R-9
DESCRIPTION:Ussuri Cycle-Trailing Release Deadline\n\nAll projects followi
 ng the cycle-trailing release model must release their Ussuri deliverables
  by 13 August\, 2020.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-8
DTSTART;VALUE=DATE:20200817
DTEND;VALUE=DATE:20200822
DTSTAMP:20200814T121816Z
UID:Victoria-R-8
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-7
DTSTART;VALUE=DATE:20200824
DTEND;VALUE=DATE:20200829
DTSTAMP:20200814T121816Z
UID:Victoria-R-7
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-6 (Final release for non-client libraries)
DTSTART;VALUE=DATE:20200831
DTEND;VALUE=DATE:20200905
DTSTAMP:20200814T121816Z
UID:Victoria-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:Victoria R-5 (Victoria-3 milestone\; Feature freeze\; Final releas
 e for client libraries\; Soft StringFreeze\; Requirements freeze\; Victori
 a Community Goals Completed\; Cycle Highlights)
DTSTART;VALUE=DATE:20200907
DTEND;VALUE=DATE:20200912
DTSTAMP:20200814T121816Z
UID:Victoria-R-5
DESCRIPTION:Victoria-3 milestone\n\n10 September\, 2020 is the Victoria-3 
 milestone. See project-specific notes for relevant deadlines.\n\n\n\nFeatu
 re freeze\n\nThe Victoria-3 milestone marks feature freeze for projects fo
 llowing the release:cycle-with-rc model. No featureful patch should be lan
 ded 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 t
 heir final release during this week\, to match feature freeze.\n\n\n\nSoft
  StringFreeze\n\nYou are no longer allowed to accept proposed changes cont
 aining modifications in user-facing strings. Such changes should be reject
 ed by the review team and postponed until the next series development open
 s (which should happen when RC1 is published).\n\n\n\nRequirements freeze\
 n\nAfter the Victoria-3 milestone\, only critical requirements and constra
 ints changes will be allowed. Freezing our requirements list gives package
 rs downstream an opportunity to catch up and prepare packages for everythi
 ng necessary for distributions of the upcoming release. The requirements r
 emain frozen until the stable branches are created\, with the release cand
 idates.\n\n\n\nVictoria Community Goals Completed\n\nTeams should prepare 
 their documentation for completing the community-wide goals for Victoria.\
 n\n\n\nCycle Highlights\n\nCycle highlights need to be added to the releas
 e deliverables by feature freeze to be included in any marketing release m
 essaging. Highlights may be added after this point\, but they will likely 
 only be useful for historical purposes.\n\nSee the Project Team Guide for 
 more details and instructions on adding these highlights.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-4
DTSTART;VALUE=DATE:20200914
DTEND;VALUE=DATE:20200919
DTSTAMP:20200814T121816Z
UID:Victoria-R-4
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-3 (RC1 target week\; Hard StringFreeze)
DTSTART;VALUE=DATE:20200921
DTEND;VALUE=DATE:20200926
DTSTAMP:20200814T121816Z
UID:Victoria-R-3
DESCRIPTION:RC1 target week\n\nThe week of 21 September is the target date
  for projects following the release:cycle-with-rc model to issue their fir
 st release candidate.\n\n\n\nHard StringFreeze\n\nThis happens when the RC
 1 for the project is tagged. At this point\, ideally no strings are change
 d (or added\, or removed)\, to give translators time to finish up their ef
 forts.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-2
DTSTART;VALUE=DATE:20200928
DTEND;VALUE=DATE:20201003
DTSTAMP:20200814T121816Z
UID:Victoria-R-2
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-1 (Final RCs and intermediary releases)
DTSTART;VALUE=DATE:20201005
DTEND;VALUE=DATE:20201010
DTSTAMP:20200814T121816Z
UID:Victoria-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of 5 October i
 s the last week to issue release candidates or intermediary releases befor
 e release week. During release week\, only final-release-critical releases
  will be accepted (at the discretion of the release team).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R-0 (Victoria release)
DTSTART;VALUE=DATE:20201012
DTEND;VALUE=DATE:20201017
DTSTAMP:20200814T121816Z
UID:Victoria-R-0
DESCRIPTION:Victoria release\n\nThe Victoria coordinated release will happ
 en on Wednesday\, 14 October\, 2020.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Victoria R+1 (Open Infrastructure Summit)
DTSTART;VALUE=DATE:20201019
DTEND;VALUE=DATE:20201024
DTSTAMP:20200814T121816Z
UID:Victoria-R+1
DESCRIPTION:Open Infrastructure Summit\n\nThe virtual Open Infrastructure 
 Summit will take place October 19-23.\n\n
END:VEVENT
END:VCALENDAR