BEGIN:VCALENDAR
PRODID:-//releases.openstack.org//EN
X-WR-CALNAME:Ussuri schedule
BEGIN:VEVENT
SUMMARY:Ussuri R-29
DTSTART:20191021
DTEND:20191026
DTSTAMP:20200319T101810Z
UID:Ussuri-R-29
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-28
DTSTART:20191028
DTEND:20191102
DTSTAMP:20200319T101810Z
UID:Ussuri-R-28
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-27 (Open Infrastructure Summit)
DTSTART:20191104
DTEND:20191109
DTSTAMP:20200319T101810Z
UID:Ussuri-R-27
DESCRIPTION:Open Infrastructure Summit\n\nThe Open Infrastructure Summit h
 appens during this week in Shanghai\, China. It will include a “Forum”
  in which people from all parts of our community will gather to give feedb
 ack on the last release (Train) and discuss requirements for future releas
 es.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-26
DTSTART:20191111
DTEND:20191116
DTSTAMP:20200319T101810Z
UID:Ussuri-R-26
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-25
DTSTART:20191118
DTEND:20191123
DTSTAMP:20200319T101810Z
UID:Ussuri-R-25
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-24
DTSTART:20191125
DTEND:20191130
DTSTAMP:20200319T101810Z
UID:Ussuri-R-24
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-23
DTSTART:20191202
DTEND:20191207
DTSTAMP:20200319T101810Z
UID:Ussuri-R-23
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-22 (Ussuri-1 milestone\; Services Drop python 2 Completed
 \; Common libraries & QA Start dropping python 2)
DTSTART:20191209
DTEND:20191214
DTSTAMP:20200319T101810Z
UID:Ussuri-R-22
DESCRIPTION:Ussuri-1 milestone\n\n12 December\, 2019 is the Ussuri-1 miles
 tone. See project-specific notes for relevant deadlines.\n\n\n\nServices D
 rop python 2 Completed\n\nOpenStack Services dropped the python 2.7 suppor
 t and testing. Project needs to coordinate with third party CI or any back
 end drivers.\n\n\n\nCommon libraries & QA Start dropping python 2\n\nCommo
 n libraries & QA start dropping the python 2.7 support and testing. This i
 ncludes Oslo\, QA tools (including Tempest plugins or any other testing to
 ols)\, common lib used among projects (os-brick)\, Client libraries. Tempe
 st will drop the support during Feb as discussed with TripleO.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-21
DTSTART:20191216
DTEND:20191221
DTSTAMP:20200319T101810Z
UID:Ussuri-R-21
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-20
DTSTART:20191223
DTEND:20191228
DTSTAMP:20200319T101810Z
UID:Ussuri-R-20
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-19
DTSTART:20191230
DTEND:20200104
DTSTAMP:20200319T101810Z
UID:Ussuri-R-19
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-18 (Train Cycle-Trailing Release Deadline)
DTSTART:20200106
DTEND:20200111
DTSTAMP:20200319T101810Z
UID:Ussuri-R-18
DESCRIPTION:Train Cycle-Trailing Release Deadline\n\nAll projects followin
 g the cycle-trailing release model must release their Train deliverables b
 y 9 January\, 2020.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-17
DTSTART:20200113
DTEND:20200118
DTSTAMP:20200319T101810Z
UID:Ussuri-R-17
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-16
DTSTART:20200120
DTEND:20200125
DTSTAMP:20200319T101810Z
UID:Ussuri-R-16
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-15
DTSTART:20200127
DTEND:20200201
DTSTAMP:20200319T101810Z
UID:Ussuri-R-15
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-14
DTSTART:20200203
DTEND:20200208
DTSTAMP:20200319T101810Z
UID:Ussuri-R-14
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-13 (Ussuri-2 milestone\; Membership Freeze\; Common libra
 ries & QA Drop python 2 Completed\; Requirement Drop python 2 & Audit)
DTSTART:20200210
DTEND:20200215
DTSTAMP:20200319T101810Z
UID:Ussuri-R-13
DESCRIPTION:Ussuri-2 milestone\n\n13 February\, 2020 is the Ussuri-2 miles
 tone. See project-specific notes for relevant deadlines.\n\n\n\nMembership
  Freeze\n\nProjects must participate in at least two milestones in order t
 o be considered part of the release. Projects made official after the seco
 nd milestone\, or which fail to produce milestone releases for at least on
 e 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\n\n
 Common libraries & QA Drop python 2 Completed\n\nCommon libraries & QA dro
 pped the python 2.7 support and testing.\n\n\n\nRequirement Drop python 2 
 & Audit\n\nRequirement to drop the python 2.7 support and testing. Audit t
 hat every project except Swift have dropped the python 2 support.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-12
DTSTART:20200217
DTEND:20200222
DTSTAMP:20200319T101810Z
UID:Ussuri-R-12
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-11
DTSTART:20200224
DTEND:20200229
DTSTAMP:20200319T101810Z
UID:Ussuri-R-11
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-10
DTSTART:20200302
DTEND:20200307
DTSTAMP:20200319T101810Z
UID:Ussuri-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-9
DTSTART:20200309
DTEND:20200314
DTSTAMP:20200319T101810Z
UID:Ussuri-R-9
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-8
DTSTART:20200316
DTEND:20200321
DTSTAMP:20200319T101810Z
UID:Ussuri-R-8
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-7 (Extra-ATCs deadline\; TC Election Nomination Begins)
DTSTART:20200323
DTEND:20200328
DTSTAMP:20200319T101810Z
UID:Ussuri-R-7
DESCRIPTION:Extra-ATCs deadline\n\nProject teams should identify contribut
 ors who have had a significant impact this cycle but who would not qualify
  for ATC status using the regular process because they have not submitted 
 a patch. Those names should be added to the governance repo for considerat
 ion as ATC for the future.\n\n\n\nTC Election Nomination Begins\n\nTechnic
 al committee candidates interested in serving for the next calendar year s
 hould announce their candidacies and platforms during this week.  Please s
 ee the Election site for specific timing imformation.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-6 (Final release for non-client libraries\; TC Election C
 ampaigning Begins\; Election Email Deadline)
DTSTART:20200330
DTEND:20200404
DTSTAMP:20200319T101810Z
UID:Ussuri-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\n\nTC Election Campaigning Begins\n\nThe electorate has t
 ime to ask candidates questions about their platforms and debate topics be
 fore polling begins.  Please see the Election site for specific timing inf
 ormation.\n\n\n\nElection Email Deadline\n\nContributors that will be in t
 he electorate for the upcoming elections should confirm their gerrit email
  addresses by this date (April 7th\, 2020 at 00:00 UTC). Electorate rolls 
 are generated after this date and ballots will be sent to the listed gerri
 t email address.
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-5 (Ussuri-3 milestone\; Feature freeze\; Final release fo
 r client libraries\; Soft StringFreeze\; Requirements freeze\; Ussuri Comm
 unity Goals Completed\; TC Election Polling Begins\; u_cycle-highlights)
DTSTART:20200406
DTEND:20200411
DTSTAMP:20200319T101810Z
UID:Ussuri-R-5
DESCRIPTION:Ussuri-3 milestone\n\n9 April\, 2020 is the Ussuri-3 milestone
 . See project-specific notes for relevant deadlines.\n\n\n\nFeature freeze
 \n\nThe Ussuri-3 milestone marks feature freeze for projects following the
  release:cycle-with-rc model. No featureful patch should be landed after t
 his point. Exceptions may be granted by the project PTL.\n\n\n\n\n\nFinal 
 release for client libraries\n\nClient libraries should issue their final 
 release during this week\, to match feature freeze.\n\n\n\nSoft StringFree
 ze\n\nYou are no longer allowed to accept proposed changes containing modi
 fications in user-facing strings. Such changes should be rejected by the r
 eview team and postponed until the next series development opens (which sh
 ould happen when RC1 is published).\n\n\n\nRequirements freeze\n\nAfter th
 e Ussuri-3 milestone\, only critical requirements and constraints 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 remain frozen 
 until the stable branches are created\, with the release candidates.\n\n\n
 \nUssuri Community Goals Completed\n\nTeams should prepare their documenta
 tion for completing the community-wide goals for Ussuri.\n\n\n\nTC Electio
 n Polling Begins\n\nElection polling week for open seats on the TC.  Pleas
 e see the Election site for specific timing imformation.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-4
DTSTART:20200413
DTEND:20200418
DTSTAMP:20200319T101810Z
UID:Ussuri-R-4
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-3 (RC1 target week\; Hard StringFreeze)
DTSTART:20200420
DTEND:20200425
DTSTAMP:20200319T101810Z
UID:Ussuri-R-3
DESCRIPTION:RC1 target week\n\nThe week of 20 April is the target date for
  projects following the release:cycle-with-rc model to issue their first r
 elease candidate.\n\n\n\nHard StringFreeze\n\nThis happens when the RC1 fo
 r the project is tagged. At this point\, ideally no strings are changed (o
 r added\, or removed)\, to give translators time to finish up their effort
 s.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-2
DTSTART:20200427
DTEND:20200502
DTSTAMP:20200319T101810Z
UID:Ussuri-R-2
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-1 (Final RCs and intermediary releases)
DTSTART:20200504
DTEND:20200509
DTSTAMP:20200319T101810Z
UID:Ussuri-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of 4 May is th
 e last week to issue release candidates or intermediary releases before re
 lease week. During release week\, only final-release-critical releases wil
 l be accepted (at the discretion of the release team).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ussuri R-0 (Ussuri release)
DTSTART:20200511
DTEND:20200516
DTSTAMP:20200319T101810Z
UID:Ussuri-R-0
DESCRIPTION:Ussuri release\n\nThe Ussuri coordinated release will happen o
 n Wednesday\, 13 May\, 2020.\n\n
END:VEVENT
END:VCALENDAR