BEGIN:VCALENDAR
PRODID:-//releases.openstack.org//EN
X-WR-CALNAME:Train schedule
BEGIN:VEVENT
SUMMARY:Train R-26
DTSTART;VALUE=DATE:20190415
DTEND;VALUE=DATE:20190420
DTSTAMP:20190611T223045Z
UID:Train-R-26
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-25
DTSTART;VALUE=DATE:20190422
DTEND;VALUE=DATE:20190427
DTSTAMP:20190611T223045Z
UID:Train-R-25
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-24 (Open Infrastructure Summit)
DTSTART;VALUE=DATE:20190429
DTEND;VALUE=DATE:20190504
DTSTAMP:20190611T223045Z
UID:Train-R-24
DESCRIPTION:Open Infrastructure Summit\n\nThe Open Infrastructure Summit h
 appens during this week in Denver\, CO\, USA. It will include a “Forum
 ” in which people from all parts of our community will gather to give fe
 edback on the last release (Stein) and discuss requirements for the next d
 evelopment cycle (Train).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-23
DTSTART;VALUE=DATE:20190506
DTEND;VALUE=DATE:20190511
DTSTAMP:20190611T223045Z
UID:Train-R-23
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-22
DTSTART;VALUE=DATE:20190513
DTEND;VALUE=DATE:20190518
DTSTAMP:20190611T223045Z
UID:Train-R-22
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-21
DTSTART;VALUE=DATE:20190520
DTEND;VALUE=DATE:20190525
DTSTAMP:20190611T223045Z
UID:Train-R-21
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-20
DTSTART;VALUE=DATE:20190527
DTEND;VALUE=DATE:20190601
DTSTAMP:20190611T223045Z
UID:Train-R-20
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-19 (Train-1 milestone)
DTSTART;VALUE=DATE:20190603
DTEND;VALUE=DATE:20190608
DTSTAMP:20190611T223045Z
UID:Train-R-19
DESCRIPTION:Train-1 milestone\n\n6 June\, 2019 is the Train-1 milestone. S
 ee project-specific notes for relevant deadlines.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-18
DTSTART;VALUE=DATE:20190610
DTEND;VALUE=DATE:20190615
DTSTAMP:20190611T223045Z
UID:Train-R-18
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-17
DTSTART;VALUE=DATE:20190617
DTEND;VALUE=DATE:20190622
DTSTAMP:20190611T223045Z
UID:Train-R-17
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-16
DTSTART;VALUE=DATE:20190624
DTEND;VALUE=DATE:20190629
DTSTAMP:20190611T223045Z
UID:Train-R-16
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-15
DTSTART;VALUE=DATE:20190701
DTEND;VALUE=DATE:20190706
DTSTAMP:20190611T223045Z
UID:Train-R-15
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-14
DTSTART;VALUE=DATE:20190708
DTEND;VALUE=DATE:20190713
DTSTAMP:20190611T223045Z
UID:Train-R-14
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-13
DTSTART;VALUE=DATE:20190715
DTEND;VALUE=DATE:20190720
DTSTAMP:20190611T223045Z
UID:Train-R-13
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-12 (Train-2 milestone\; Membership Freeze)
DTSTART;VALUE=DATE:20190722
DTEND;VALUE=DATE:20190727
DTSTAMP:20190611T223045Z
UID:Train-R-12
DESCRIPTION:Train-2 milestone\n\n25 July\, 2019 is the Train-2 milestone. 
 See project-specific notes for relevant deadlines.\n\n\n\nMembership Freez
 e\n\nProjects must participate in at least two milestones in order to be c
 onsidered part of the release. Projects made official after the second mil
 estone\, or which fail to produce milestone releases for at least one of t
 he first and second milestones as well as the third milestone\, are theref
 ore 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:Train R-11
DTSTART;VALUE=DATE:20190729
DTEND;VALUE=DATE:20190803
DTSTAMP:20190611T223045Z
UID:Train-R-11
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-10
DTSTART;VALUE=DATE:20190805
DTEND;VALUE=DATE:20190810
DTSTAMP:20190611T223045Z
UID:Train-R-10
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-9
DTSTART;VALUE=DATE:20190812
DTEND;VALUE=DATE:20190817
DTSTAMP:20190611T223045Z
UID:Train-R-9
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-8
DTSTART;VALUE=DATE:20190819
DTEND;VALUE=DATE:20190824
DTSTAMP:20190611T223045Z
UID:Train-R-8
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-7 (TC Election Nomination Begins\; Extra-ATCs deadline)
DTSTART;VALUE=DATE:20190826
DTEND;VALUE=DATE:20190831
DTSTAMP:20190611T223045Z
UID:Train-R-7
DESCRIPTION:TC Election Nomination Begins\n\nTechnical committee candidate
 s interested in serving for the next calendar year should announce their c
 andidacies and platforms during this week.  Please see the Election site f
 or specific timing imformation.\n\n\n\nExtra-ATCs deadline\n\nProject team
 s should identify contributors who have had a significant impact this cycl
 e but who would not qualify for ATC status using the regular process becau
 se they have not submitted a patch. Those names should be added to the gov
 ernance repo for consideration as ATC for the future.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-6 (Final release for non-client libraries\; Election Email
  Deadline\; TC Election Campaigning Begins)
DTSTART;VALUE=DATE:20190902
DTEND;VALUE=DATE:20190907
DTSTAMP:20190611T223045Z
UID:Train-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\nElection Email Deadline\n\nContributors that will be i
 n the electorate for the upcoming elections should confirm their gerrit em
 ail addresses by this date (September 3rd\, 2019 at 00:00 UTC). Electorate
  rolls are generated after this date and ballots will be sent to the liste
 d gerrit email address.\n\nTC Election Campaigning Begins\n\nThe electorat
 e has time to ask candidates questions about their platforms and debate to
 pics before polling begins.  Please see the Election site for specific tim
 ing information.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-5 (Train-3 milestone\; Feature freeze\; Final release for 
 client libraries\; Soft StringFreeze\; Requirements freeze\; Train Communi
 ty Goals Completed\; Cycle highlights marketing deadline\; TC Election Pol
 ling Begins)
DTSTART;VALUE=DATE:20190909
DTEND;VALUE=DATE:20190914
DTSTAMP:20190611T223045Z
UID:Train-R-5
DESCRIPTION:Train-3 milestone\n\n12 September\, 2019 is the Train-3 milest
 one. See project-specific notes for relevant deadlines.\n\n\n\nFeature fre
 eze\n\nThe Train-3 milestone marks feature freeze for projects following t
 he release:cycle-with-rc model. No featureful patch should be landed after
  this point. Exceptions may be granted by the project PTL.\n\n\n\n\n\nFina
 l release for client libraries\n\nClient libraries should issue their fina
 l release during this week\, to match feature freeze.\n\n\n\nSoft StringFr
 eeze\n\nYou are no longer allowed to accept proposed changes containing mo
 difications in user-facing strings. Such changes should be rejected by the
  review team and postponed until the next series development opens (which 
 should happen when RC1 is published).\n\n\n\nRequirements freeze\n\nAfter 
 the Train-3 milestone\, only critical requirements and constraints changes
  will be allowed. Freezing our requirements list gives packagers downstrea
 m 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\nTrain Community Goals Completed\n\nTeams should prepare their documenta
 tion for completing the community-wide goals for Train.\n\n\n\nCycle highl
 ights marketing deadline\n\nCycle highlights need to be added to the relea
 se deliverables by feature freeze to be included in any marketing release 
 messaging. 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\n\nTC Elect
 ion Polling Begins\n\nElection polling week for open seats on the TC.  Ple
 ase see the Election site for specific timing imformation.\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-4
DTSTART;VALUE=DATE:20190916
DTEND;VALUE=DATE:20190921
DTSTAMP:20190611T223045Z
UID:Train-R-4
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-3 (RC1 target week\; Hard StringFreeze)
DTSTART;VALUE=DATE:20190923
DTEND;VALUE=DATE:20190928
DTSTAMP:20190611T223045Z
UID:Train-R-3
DESCRIPTION:RC1 target week\n\nThe week of September 23-27 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:Train R-2
DTSTART;VALUE=DATE:20190930
DTEND;VALUE=DATE:20191005
DTSTAMP:20190611T223045Z
UID:Train-R-2
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R-1 (Final RCs and intermediary releases)
DTSTART;VALUE=DATE:20191007
DTEND;VALUE=DATE:20191012
DTSTAMP:20190611T223045Z
UID:Train-R-1
DESCRIPTION:Final RCs and intermediary releases\n\nThe week of October 7-1
 1 is the last week to issue release candidates or intermediary releases be
 fore release week. During release week\, only final-release-critical relea
 ses will be accepted (at the discretion of the release team).\n\n
END:VEVENT
BEGIN:VEVENT
SUMMARY:Train R+0 (Train release)
DTSTART;VALUE=DATE:20191014
DTEND;VALUE=DATE:20191019
DTSTAMP:20190611T223045Z
UID:Train-R+0
DESCRIPTION:Train release\n\nThe Train coordinated release will happen on 
 16 October 2019.\n\n
END:VEVENT
END:VCALENDAR