BEGIN:VCALENDAR
PRODID:-//releases.openstack.org//EN
X-WR-CALNAME:Pike schedule
BEGIN:VEVENT
SUMMARY:Pike R-26
DTSTART;VALUE=DATE:20170227
DTEND;VALUE=DATE:20170304
DTSTAMP:20170711T104638Z
UID:Pike-R-26
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-25
DTSTART;VALUE=DATE:20170306
DTEND;VALUE=DATE:20170311
DTSTAMP:20170711T104638Z
UID:Pike-R-25
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-24
DTSTART;VALUE=DATE:20170313
DTEND;VALUE=DATE:20170318
DTSTAMP:20170711T104638Z
UID:Pike-R-24
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-23
DTSTART;VALUE=DATE:20170320
DTEND;VALUE=DATE:20170325
DTSTAMP:20170711T104638Z
UID:Pike-R-23
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-22
DTSTART;VALUE=DATE:20170327
DTEND;VALUE=DATE:20170401
DTSTAMP:20170711T104638Z
UID:Pike-R-22
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-21
DTSTART;VALUE=DATE:20170403
DTEND;VALUE=DATE:20170408
DTSTAMP:20170711T104638Z
UID:Pike-R-21
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-20 (Pike-1 milestone)
DTSTART;VALUE=DATE:20170410
DTEND;VALUE=DATE:20170415
DTSTAMP:20170711T104638Z
UID:Pike-R-20
DESCRIPTION:Pike-1 milestone\n\n13 April 2017 is the Pike-1 milestone wind
 ow for projects following the release:cycle-with-milestones model.\n\n\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-19
DTSTART;VALUE=DATE:20170417
DTEND;VALUE=DATE:20170422
DTSTAMP:20170711T104638Z
UID:Pike-R-19
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-18
DTSTART;VALUE=DATE:20170424
DTEND;VALUE=DATE:20170429
DTSTAMP:20170711T104638Z
UID:Pike-R-18
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-17
DTSTART;VALUE=DATE:20170501
DTEND;VALUE=DATE:20170506
DTSTAMP:20170711T104638Z
UID:Pike-R-17
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-16 (OpenStack Summit)
DTSTART;VALUE=DATE:20170508
DTEND;VALUE=DATE:20170513
DTSTAMP:20170711T104638Z
UID:Pike-R-16
DESCRIPTION:OpenStack Summit\n\nThe OpenStack Summit happens during this w
 eek in Boston\, USA. It will include a “Forum” in which people from al
 l parts of our community will gather to give feedback on the last release 
 (Ocata) and discuss requirements for the next development cycle (Queens).\
 n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-15
DTSTART;VALUE=DATE:20170515
DTEND;VALUE=DATE:20170520
DTSTAMP:20170711T104638Z
UID:Pike-R-15
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-14
DTSTART;VALUE=DATE:20170522
DTEND;VALUE=DATE:20170527
DTSTAMP:20170711T104638Z
UID:Pike-R-14
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-13
DTSTART;VALUE=DATE:20170529
DTEND;VALUE=DATE:20170603
DTSTAMP:20170711T104638Z
UID:Pike-R-13
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-12 (Pike-2 milestone\; Membership Freeze)
DTSTART;VALUE=DATE:20170605
DTEND;VALUE=DATE:20170610
DTSTAMP:20170711T104638Z
UID:Pike-R-12
DESCRIPTION:Pike-2 milestone\n\n8 June 2017 is the Pike-2 milestone window
  for projects following the release:cycle-with-milestones model.\n\n\n\nMe
 mbership Freeze\n\nProjects must participate in at least two milestones in
  order to be considered part of the release. Projects made official after 
 the second milestone\, or which fail to produce milestone releases for at 
 least one of the first and second milestones as well as the third mileston
 e\, are therefore not considered part of the release for the cycle.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-11
DTSTART;VALUE=DATE:20170612
DTEND;VALUE=DATE:20170617
DTSTAMP:20170711T104638Z
UID:Pike-R-11
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-10
DTSTART;VALUE=DATE:20170619
DTEND;VALUE=DATE:20170624
DTSTAMP:20170711T104638Z
UID:Pike-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-9
DTSTART;VALUE=DATE:20170626
DTEND;VALUE=DATE:20170701
DTSTAMP:20170711T104638Z
UID:Pike-R-9
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-8
DTSTART;VALUE=DATE:20170703
DTEND;VALUE=DATE:20170708
DTSTAMP:20170711T104638Z
UID:Pike-R-8
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-7 (Extra-ATCs deadline)
DTSTART;VALUE=DATE:20170710
DTEND;VALUE=DATE:20170715
DTSTAMP:20170711T104638Z
UID:Pike-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:Pike R-6 (Final release for non-client libraries)
DTSTART;VALUE=DATE:20170717
DTEND;VALUE=DATE:20170722
DTSTAMP:20170711T104638Z
UID:Pike-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:Pike R-5 (Pike-3 milestone\; Feature freeze\; Final release for cl
 ient libraries\; Soft StringFreeze\; Requirements freeze\; Pike Community 
 Goals Completed)
DTSTART;VALUE=DATE:20170724
DTEND;VALUE=DATE:20170729
DTSTAMP:20170711T104638Z
UID:Pike-R-5
DESCRIPTION:Pike-3 milestone\n\n27 July 2017 is the Pike-3 milestone windo
 w for projects following the release:cycle-with-milestones model.\n\n\n\nF
 eature freeze\n\nThe Pike-3 milestone marks feature freeze for projects fo
 llowing the release:cycle-with-milestones model. No featureful patch shoul
 d be landed after this point. Exceptions may be granted by the project PTL
 .\n\n\n\nFinal release for client libraries\n\nClient libraries should iss
 ue their final release during this week\, to match feature freeze.\n\n\n\n
 Soft StringFreeze\n\nYou are no longer allowed to accept proposed changes 
 containing modifications in user-facing strings. Such changes should be re
 jected by the review team and postponed until the next series development 
 opens (which should happen when RC1 is published).\n\n\n\nRequirements fre
 eze\n\nAfter the Pike-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\nPike Community Goals Completed\n\nTeams should prepare thei
 r documentation for completing the community-wide goals for Pike.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-4
DTSTART;VALUE=DATE:20170731
DTEND;VALUE=DATE:20170805
DTSTAMP:20170711T104638Z
UID:Pike-R-4
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-3 (RC1 target week\; Hard StringFreeze\; Pike cycle-trailin
 g feature freeze)
DTSTART;VALUE=DATE:20170807
DTEND;VALUE=DATE:20170812
DTSTAMP:20170711T104638Z
UID:Pike-R-3
DESCRIPTION:RC1 target week\n\nThe week of 7-11 August 2017 is the target 
 date for projects following the release:cycle-with-milestones model to iss
 ue their first release candidate\, with a deadline of 10 August 2017.\n\n\
 n\nHard StringFreeze\n\nThis happens when the RC1 for the project is tagge
 d. At this point\, ideally no strings are changed (or added\, or removed)\
 , to give translator time to finish up their efforts.\n\n\n\nPike cycle-tr
 ailing feature freeze\n\nThe release deadline for projects using the relea
 se:cycle-trailing model that follow the main release cycle.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-2
DTSTART;VALUE=DATE:20170814
DTEND;VALUE=DATE:20170819
DTSTAMP:20170711T104638Z
UID:Pike-R-2
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R-1 (Final RCs and intermediary releases)
DTSTART;VALUE=DATE:20170821
DTEND;VALUE=DATE:20170826
DTSTAMP:20170711T104638Z
UID:Pike-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of 21 August 2
 017 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:Pike R+0 (Pike release\; Pike cycle-trailing RC deadline)
DTSTART;VALUE=DATE:20170828
DTEND;VALUE=DATE:20170902
DTSTAMP:20170711T104638Z
UID:Pike-R+0
DESCRIPTION:Pike release\n\nThe Pike coordinated release will happen on 30
  August 2017.\n\n\n\nPike cycle-trailing RC deadline\n\nThe deadline for p
 ublishing a first release candidate for projects using the release:cycle-t
 railing model that follow the main release cycle.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R+1
DTSTART;VALUE=DATE:20170904
DTEND;VALUE=DATE:20170909
DTSTAMP:20170711T104638Z
UID:Pike-R+1
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pike R+2 (Pike cycle-trailing release deadline)
DTSTART;VALUE=DATE:20170911
DTEND;VALUE=DATE:20170916
DTSTAMP:20170711T104638Z
UID:Pike-R+2
DESCRIPTION:Pike cycle-trailing release deadline\n\nThe release deadline f
 or projects using the release:cycle-trailing model that follow the main re
 lease cycle.
END:VEVENT
END:VCALENDAR