Newton is EOL, but we have not updated the release table, so it still
shows up as active. This updates the release to show its final state.
Change-Id: Iceb608eb962d98d51ed11184f7450feb9101dc0f
Assuming we will stay with a 6 month release cycle for Rocky,
this is a proposed schedule for the Rocky cycle.
One thing to note is the date for the S PTG has not been finalized
yet, so we may need or want to push out the window between one of
the milestones so there is not too long of a gap between Rocky
being released and the next PTG being held.
Change-Id: I0e26b443b7d4cf64f834b9726342cdfab54d36e7
Since the Pike cycle releases are behind us, document that the
pending key for the Queens cycle is now in place as of 2017-09-15
and the Pike key is retired from use beyond that date.
Change-Id: I3c64ad3aaf10452ab6fb1b03014a5e2f571215d0
Set the default series for commands to 'queens'.
Change-Id: I120b80868191055861485d0b9a7588f97612e549
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Here is the proposed release schedule for the Queens cycle.
Do not approve just yet, we need to check it first, then
propose it to the ML, then finally approve it.
Change-Id: Iee53a60549156466ea7005f906fb25b6d86408e0
In an effort to avoid confusing some users into thinking the Pike
release date has not been set, instead of "TBD" for the initial
release value use "scheduled" as a hyperlink to the schedule
subsection for the release date.
Change-Id: I2d4973280e3c02649973af22f1b264f5369f36e4
Fixed the phase II support date for the Newton
release since we rollover phases on six month
intervals from the given branch's release date,
not the next releases date.
Change-Id: Id9249d665502cdd6402b16bc41e22510ce870b98
We switched to https for docs.openstack.org, adjust most URLs.
This change updates documentation etc files, but not any deliverable files.
Change-Id: Ia8b0524025ab1c685ec6f57246f8b34231f52632
Since the Ocata cycle releases are behind us, document that the
pending key for the Pike cycle is now in place as of 2017-03-24 and
the Ocata key is retired from use beyond that date.
Change-Id: Ief302e29769da1de8c6bc18afc1ac1b38fd17d19
With Ocata being a short cycle there is some confusion about when
various releases transition from Phase I -> Phase II etc. This change
adds a column to the main table on releases.o.o to show what the next
phase is and approximately when it will happen.
Mitaka:
Phase I: 2016-04-07 Release date
Phase II: 2016-10-06 Newton Release date
EOL : 2017-04-10 ~1 year after release
Newton:
Phase I: 2016-10-06 (Release date)
Phase II: 2017-02-22 Ocata Release date[1]
Phase III: 2017-08-28 ~6months after Phase II
EOL : 2017-10-11 ~1 year after release
Ocata:
Phase I: 2017-02-22 (Release date)
Phase II: 2017-08-28 ~Pike release date[2]
EOL : 2018-02-26 ~1 year after release
[1] We only have a single 'Latest Release'
[2] https://releases.openstack.org/pike/schedule.html
Change-Id: Ic48feb9c29273be2fb82ebe723684c56f01d1f67
The newton EOL date was discussed in Barcelona, Occta is bascially the
releasedate +1y rounded to the next Monday.
Change-Id: I04173865885ad795e4663c1431646aba145745fd
PTG2 is now 99% sure to happen on Sept 11-15 week. Here is the
proposed schedule for the Pike cycle.
Change-Id: Id022410613a851d7f0da1f78ec583d21f30c7e55
The descriptions of stable branch phases here and in the project team
guide do not match. This change links the status information for
actively maintained releases to the project team guide section
describing what each stable support phase means.
Depends-On: I92b1a80fcd8cd38d7e450269fe56ecc8ab6ba98f
Change-Id: I2e49335f80d36d52a806dbefa70e895dd5eced47
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
The stable/liberty branches of official deliverables have been EOL
for a month, make sure the releases documentation reflects that.
Change-Id: I1f3420b796586f7244ac1db7f4ef80cfcb7d81b0
In addition to each series-specific calendar, prepare a single global
ICS file with all calendar events in it.
Change-Id: I3b66a343d1d0eac19c212c26957cc98ecbc062de
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Provide some explanatory prose about handling of OpenPGP signatures
for Git tags and similar release artifacts. Also provide a copy of
the corresponding public keys, for improved provenance. New keys
should be added each cycle as they're rotated into use.
Change-Id: I083bc8acf8d95e938afb5446d786eedf4fc43751
Because release models change from series to series, we want to track
the data in the releases repository instead of in the governance
repository. This change adds a new 'release-model' field to the
deliverable files to hold the new value.
The valid release models are documented as part of a new reference
section for the published documentation for the site.
The validator looks only at the deliverable file for the release model,
and no longer looks at the projects.yaml file in the governance
repository. For files in the _independent directory, the release model
is inferred from the filename to avoid having to set it redundantly.
Change-Id: I81198a86da98436dc2f65806aafc5f241340c57f
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Based on feedback during the fishbowl session held at the Ocata summit
in Barcelona, downstream consumers of the final release would like the
release to happen earlier in the week to give them time to create
packages before the weekend. This change moves the final release date
forward one day from Thursday 23 Feb to Wednesday 22 Feb to accommodate
this request. Impact on project teams is expected to be minimal, because
the release team creates the final tag based on existing release
candidates.
Change-Id: I91834e6b89827f928588932d3ea74f938f5d32a4
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
the only doc under the schedules directory mentioned that it has
been moved. delete it and the only reference in the index file
sine its not shown in the html rendering.
Change-Id: I06ced0aea9d89f0f44948f45cffbca34badef138
Mitaka was released on 2016-04-07 Set the EOL date to release date + 12
months then round to the next Monday.
Change-Id: I97e23a5c072dba9e2dab1870639f648e5ef8403e
Turn "_Independent" to "Independent" on the team pages.
Move the independent section on the main page above the team list to
make it easier to find.
Change-Id: I670643a791c7618a5c1febb7ec63e9540d4f206d
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Add pages to show the work each team has produced. For now, only
official teams using cycle-based release models are included. In a later
phase we will add deliverables that are currently listed as indepdent.
Change-Id: Ieb54aa7a4d2f58f462692e295c8f19978d5baa73
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Update the release series table to show the initial release date and the
EOL date, where I could find them.
Change-Id: I6b66573919f38f3b2abe4bea34b04ac9aa58a95b
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
The pbr feature for invoking sphinx doesn't let us treat warnings as
errors because of a bug in pbr. Switch to invoking sphinx directly,
including removing the setup.cfg instructions for sphinx, so we can use
the flag to treat warnings as errors. Doing this also requires fixing a
few existing warnings, so those changes are included in this patch.
Change-Id: I2aa0d844855d5a18646d0bc3907620544ae71be2
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Mark Mitaka as a stable release and Newton as under active development.
Change-Id: Ia8ad7141cd6c83b2bbee8f2fc02fdc4441d5066d
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Remove the data we added for testing the release tools.
Change-Id: Ia27ea77e59059d374a930befe7087c12de2df69a
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
The releases website is primarily targeted to downstream consumers
of the releases, not to the upstream producers of the releases.
Instructions on "how to use this repository" are therefore
confusing, especially in the front page. Move them to the repository
README.rst instead.
Change-Id: Iaf980f7ba3a04107e23ef952d898cac0ce880662
Set up the pages for the next known release series names.
Change-Id: Iadc0ccf33f0d54808b59e2a17b463fc0f5e40e9e
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Annotate the releases that are no longer supported with their
end-of-life dates.
Change-Id: I3fd9aaea3179d0a3423853ccef74b09fc021ed48
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
We want to remove the redundant 'releases' directory in the URLs for
release pages, so create one directory for each series and move the
existing file there. Sphinx doesn't have an easy way to handle
redirects, so just add a stub page with a link to the root document for
folks to find the thing that moved. We will delete these pages after we
start publishing to releases.openstack.org instead of
docs.openstack.org.
Change-Id: I970bdd20e23c748a7e8a456808c73d74570eb066
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Add Mitaka release schedule to this repository, allowing
review of changes and project-specific deadlines to be added.
Change-Id: Iab88060507834779c441f31fc7f880057985d5a5
There are various discussions about the fact that Juno is EOL in
November, but there is no hard documented date when such a thing is
expected to happen. Document when Juno was released and when it will EOL
- as well as the same for kilo, liberty and mitaka.
Change-Id: Iada72d966e93b8ff1f0febb4473a92fdd0532e51
Add the mitaka page as the first item in the toctree so it is the "next"
page after the index page in the navigation structure.
Change-Id: I360a8fe91580f12e2ec4e11385bc5c9d38b16fbc
Show all of the release:independent projects release histories on a
separate page, now that they have moved out of the release series
directories.
Change-Id: I3fddbca590b1a8fcacc180a2730f0463dbcc0100