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
Some placeholders were left over in the comments for the Pike
milestones. This updates them now that we know the specific weeks for
each one.
Change-Id: I1e39a46796b3f3045e9e61f28716ca6551644772
Following a very similar release template as the Ocata release,
set project specific dates for keystone. The only thing different
between the proposed schedule for Pike and Ocata is that the
deadline for feature proposal freeze is one week earlier from what
it was in Ocata. This was done to allow for more time between feature
proposal freeze and feature freeze.
Change-Id: Idb2a3b925a4fdf92afef81d1360ffd87a8192d17
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
Nova is going to have spec freeze on the p-1 milestone.
Nova will not be doing a non-priority feature freeze in
Pike and will follow the same feature freeze date as the
rest of the community.
Change-Id: Ic1ca3dbf797fa966123a7998b02d1ec39156a8ec
(Also corrected two too-short underlines in the rst file that were
making my docs build fail locally.)
Change-Id: I90439f0e1052a7793a119c4e30e049de02440f3a
Add specific feature freeze and RC1 deadlines for deliverables
following the cycle-trailing model. In particular, cycle-trailing
feature freeze aligns with normal projects RC1 deadline, so that
cycle-trailing things can catch on late features dropped into
regular deliverables.
Change-Id: I0c301bfcae4f619a8f86c94510289a3e33bca2ad
The newton EOL date was discussed in Barcelona, Occta is bascially the
releasedate +1y rounded to the next Monday.
Change-Id: I04173865885ad795e4663c1431646aba145745fd
I noticed that these are getting blocked for mixed active content on
the secure page
https://releases.openstack.org/newton/index.html
Use https to get these
Change-Id: I73a1c688aa2eca93eff8984b7d1c9d826abf04b9
PTG2 is now 99% sure to happen on Sept 11-15 week. Here is the
proposed schedule for the Pike cycle.
Change-Id: Id022410613a851d7f0da1f78ec583d21f30c7e55
We can't fill out the entire Pike schedule yet, but add information
and links to the Pike PTG and Summit pages, modeled after the
entries in the Ocata schedule page, so that if a hapless Google
searcher stumbles upon this, they aren't misled into thinking the
Pike PTG is still TBD.
Change-Id: I0a87fdb60c7739fe7e23f12739486f44b671f53e
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
Remove line breaks within a paragraph to allow calendar software to
handle the text formatting.
Change-Id: Ic4c335b9bff7f0213f22c821059d9e0a842b859b
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
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>
Make the margins in the table cells a little bigger to make the layout
look nicer.
Change-Id: Icc155c707bf1e53c354b7d233fee62c57d05ff08
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Use some color in the tables to make them easier to read.
Change-Id: Idc89db1fb7e7b7ee83ee04031df6c57c5e9067b5
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Make it easier to tell what is going on when lines wrap by using lists
instead of simple formatted text.
Change-Id: I3024edb58394d68452561788836faeaab19abb26
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Put the titles of the cross-project events in the summary of the
calendar event so they show up in the main calendar view.
Add the full descriptions of the cross-project events to the calendar
event description so any extra notes (such as specific dates for
deadlines) or details about the event are visible to calendar users.
Change-Id: I6eebcdd827241f008522065a40b765b2089e2856
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This change converts the Ocata schedule to a YAML file and introduces
the templates needed to render it to a table in the restructuredtext
file so it can be published to HTML again. This is a prerequisite for
also generating an ICS file for the schedule.
Change-Id: I905b47b5b98b6d442c197e0291c44746aaf52bbb
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
As part of the "neutral governance website" effort, TC-related
governance content is moved under governance.openstack.org/tc.
While those links are preserved through redirects, it doesn't
hurt to give the right examples (and avoid redirection) wherever
we can.
Change-Id: I85160e0c9bdf3d1f3fbf372162415e80dfc41187
