BEGIN:VCALENDAR
PRODID:-//releases.openstack.org//EN
X-WR-CALNAME:Ocata schedule
BEGIN:VEVENT
SUMMARY:Ocata R-15
DTSTART;VALUE=DATE:20161107
DTEND;VALUE=DATE:20161112
DTSTAMP:20170104T100241Z
UID:Ocata-R-15
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-14 (Ocata-1 milestone\; Ocata Community Goals Acknowledgem
 ent)
DTSTART;VALUE=DATE:20161114
DTEND;VALUE=DATE:20161119
DTSTAMP:20170104T100241Z
UID:Ocata-R-14
DESCRIPTION:Ocata-1 milestone\n\n17 November is the ocata-1 milestone wind
 ow for projects following the cycle-with-milestones model.\n\n\n\nOcata Co
 mmunity Goals Acknowledgement\n\nTeams should prepare their acknowledgemen
 t of the community-wide goals for Ocata.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-13
DTSTART;VALUE=DATE:20161121
DTEND;VALUE=DATE:20161126
DTSTAMP:20170104T100241Z
UID:Ocata-R-13
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-12
DTSTART;VALUE=DATE:20161128
DTEND;VALUE=DATE:20161203
DTSTAMP:20170104T100241Z
UID:Ocata-R-12
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-11 (Ocata-2 milestone\; Membership Freeze)
DTSTART;VALUE=DATE:20161205
DTEND;VALUE=DATE:20161210
DTSTAMP:20170104T100241Z
UID:Ocata-R-11
DESCRIPTION:Ocata-2 milestone\n\n15 December is the ocata-2 milestone wind
 ow for projects following the cycle-with-milestones model.\n\n\n\nMembersh
 ip Freeze\n\nProjects must participate in at least two milestones in order
  to be considered part of the release. Projects made official after the se
 cond milestone\, or which fail to produce milestone releases for at least 
 one of the first and second milestones as well as the third milestone\, ar
 e therefore not considered part of the release for the cycle.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-10
DTSTART;VALUE=DATE:20161212
DTEND;VALUE=DATE:20161217
DTSTAMP:20170104T100241Z
UID:Ocata-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-9
DTSTART;VALUE=DATE:20161219
DTEND;VALUE=DATE:20161224
DTSTAMP:20170104T100241Z
UID:Ocata-R-9
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-8
DTSTART;VALUE=DATE:20161226
DTEND;VALUE=DATE:20161231
DTSTAMP:20170104T100241Z
UID:Ocata-R-8
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-7 (Extra-ATCs deadline)
DTSTART;VALUE=DATE:20170102
DTEND;VALUE=DATE:20170107
DTSTAMP:20170104T100241Z
UID:Ocata-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\nAlthough extra ATCs can be nominated at any 
 point\, there is a deadline to be included in electorate for the next rele
 ase cycle.  The ATC list needs to be approved by the TC by (TBD)\, and in 
 order to appear on the TC agenda to be discussed\, the proposals need to b
 e submitted to the openstack/governance repository by (TBD).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-6
DTSTART;VALUE=DATE:20170109
DTEND;VALUE=DATE:20170114
DTSTAMP:20170104T100241Z
UID:Ocata-R-6
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-5 (Final release for non-client libraries)
DTSTART;VALUE=DATE:20170116
DTEND;VALUE=DATE:20170121
DTSTAMP:20170104T100241Z
UID:Ocata-R-5
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:Ocata R-4 (Ocata-3 milestone\; Feature freeze\; Final release for 
 client libraries\; Soft StringFreeze\; Requirements freeze\; Ocata Communi
 ty Goals Completed)
DTSTART;VALUE=DATE:20170123
DTEND;VALUE=DATE:20170128
DTSTAMP:20170104T100241Z
UID:Ocata-R-4
DESCRIPTION:Ocata-3 milestone\n\n26 January is the ocata-3 milestone windo
 w for projects following the cycle-with-milestones model.\n\n\n\nFeature f
 reeze\n\nThe ocata-3 milestone marks feature freeze for projects following
  the cycle-with-milestones model. No featureful patch should be landed aft
 er this point. Exceptions may be granted by the project PTL.\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 ocata-3 milestone\, only critical requirements and constraints changes w
 ill be allowed. Freezing our requirements list gives packagers downstream 
 an opportunity to catch up and prepare packages for everything necessary f
 or distributions of the upcoming release. The requirements remain frozen u
 ntil the stable branches are created\, with the release candidates.\n\n\n\
 nOcata Community Goals Completed\n\nTeams should prepare their documentati
 on for completing the community-wide goals for Ocata.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-3 (RC1 target week\; Hard StringFreeze)
DTSTART;VALUE=DATE:20170130
DTEND;VALUE=DATE:20170204
DTSTAMP:20170104T100241Z
UID:Ocata-R-3
DESCRIPTION:RC1 target week\n\nThe week of 30 January - 3 February is the 
 target date for projects following the cycle-with-milestones model to issu
 e their first release candidate\, with a deadline of 2 February.\n\n\n\nHa
 rd 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 translator time to finish up their efforts.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-2
DTSTART;VALUE=DATE:20170206
DTEND;VALUE=DATE:20170211
DTSTAMP:20170104T100241Z
UID:Ocata-R-2
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R-1 (Final RCs and intermediary releases)
DTSTART;VALUE=DATE:20170213
DTEND;VALUE=DATE:20170218
DTSTAMP:20170104T100241Z
UID:Ocata-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of 13-17 Febru
 ary 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:Ocata R+0 (Ocata release\; Pike Project Team Gathering (PTG))
DTSTART;VALUE=DATE:20170220
DTEND;VALUE=DATE:20170225
DTSTAMP:20170104T100241Z
UID:Ocata-R+0
DESCRIPTION:Ocata release\n\nThe Ocata coordinated release will happen on 
 22 February.\n\n\n\nPike Project Team Gathering (PTG)\n\nProject team gath
 ering for the Pike release 20-24 February 2017 in Atlanta\, Georgia.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R+1
DTSTART;VALUE=DATE:20170227
DTEND;VALUE=DATE:20170304
DTSTAMP:20170104T100241Z
UID:Ocata-R+1
END:VEVENT
BEGIN:VEVENT
SUMMARY:Ocata R+2 (Ocata cycle-trailing Deadline)
DTSTART;VALUE=DATE:20170306
DTEND;VALUE=DATE:20170311
DTSTAMP:20170104T100241Z
UID:Ocata-R+2
DESCRIPTION:Ocata cycle-trailing Deadline\n\nThe deadline for projects usi
 ng the release:cycle-trailing model that follow the main release cycle is 
 9 March.
END:VEVENT
END:VCALENDAR