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>
Tidy up Newton schedule by translating 'XXX' placeholders to
their respective dates and adding the missing link for finalrc.
Also add projected release date on the main newton page and
align style for schedule link with Mitaka page.
Change-Id: Idf495a0e8c4c6a23d2195e45199a14c623be6210
Mark Mitaka as a stable release and Newton as under active development.
Change-Id: Ia8ad7141cd6c83b2bbee8f2fc02fdc4441d5066d
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Proposed Newton schedule has two 'Oct 10-14' weeks (at R+0 and R+1)
so we need to fix this.
Ideal Summit date is at R+3, and Ocata is likely to be a short cycle
already, so moving the release date to October 6 (instead of October
13) sounds like our best bet.
Change-Id: I0b246ba6bf7341500756068689eea4ee33bb0fcb
Add a link to the Mitaka-specific documentation as an easy entry point
for users exploring the new release.
Change-Id: I71106a4dbbe86204c462b5e93d74e1cb07fbf64d
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>
Pointing it to / means that we can't use it in draft builds when
reviewing changes, because we end up at the root of the draft docs build
server instead of the root of the documentation set being reviewed.
Change-Id: Ib57d2a8936431c8accfb132d0502472cfd176f1e
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
The releases website does not rely too much on prev/next
navigation and the top navigation arrow take up valuable
visual estate. Furthermore, we still have the prev/next
arrows at the bottom of the document.
Change-Id: I28fae1a58ab1a2496c3b17ddccbfc2ee73756000
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