Previous release does not work with Sphinx 2.0.
Change-Id: Idd2754b050e901bd6e9adf8fe2d4154e866840e6
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Simplify the instructions by providing a special script and then
update the instructions to refer to it.
Change-Id: Ibbcd422c06dc4aeb3df503f3c0f084b39d3bf0f7
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
With a large number of deliverables and different deliverable types, the
documentation output for a release series can get very long and it's not
always obvious that there are different groups of types if you scroll
all the way down.
This updates our deliverable extension to include a table of contents at
the top of the output to add convenient links to the different groups of
deliverables.
Change-Id: I3c55057320661f7167d44138941a07fd38c3c81f
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This adds instructions to our process document on how to prepare for the
next release cycle once the current one is complete.
Change-Id: I6f958facbfd7043a565ca5c2c0dcbfd6b3d54ad5
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
In order to give the marketing team enough time, and to match what
directions exist in process.rst, we are moving the due date for cycle
highlights to be RC1.
Change-Id: If99a825f1614d02662948e3eebe4aba0aff73ea7
In Ib5d35169e68cd92b666a35705d8e36942bd28b89 (Use a template to generate
the 'whereto' testing data) I did the simple copy'n'paste instead of
factoring the common code into a helper function.
Fix that
Change-Id: I3f0b93dd57db4811ed5c04a5a01a7ecca7ff539c
Once we have the nest series in series_status.yaml we can add
redirections for those constraints too. This allows us, should we want
to, to have branches refer to the series by name, instead of 'master'.
Change-Id: I0035190d11bf0c0bb43119fde18b5dc22d2cc1a0
For RC1 week the steps are roughly in chronological order.
In order to get cycle-highlights in time for the deadline,
move that point up.
Change-Id: I40fd38599b0851dd596f9669edd8d26ccedd8c2a
As we add more branches and tags we don't want to manually add tests for
them (and we'd need to or the docs build will fail with an 'Untested
Rule'.
Use the redirections data that we use to generate the htaccess file to
also generate the tests.
Also I removed the debug output as it it's assertion is incorrect we can
actually get the .htaccess file from the docs job \o/
Change-Id: Ib5d35169e68cd92b666a35705d8e36942bd28b89
Instead of statically listing the redirections move to a dynamic model.
We move the existing _extras/.htaccess to _templates/htaccess so we have
some control and safety of what goes in there. Connect 'build-finished'
from _exts.deliverables.py to trigger generating the redirects. Doing
so here avoids re-reading the data as deliverables.py ahas already done
that for us.
Change-Id: If6bd59fd478593a84ebcedc3a50af3720d620d3c
We have static URLs redirecting /constraints/upper/series to the
appropriate git interface. In the next change in this series we move to
a data-driven model so let's supply the data :)
Even though we have tag history that goes back to Folsom only import
Juno and later because that's when we first added constraints support
This means as the create and delete branches for requirements, like
other projects, we have a central source of truth (other than git) from
which to update the htaccess redirects.
I had update deliverables.py to account for the fact most of the
requirements branches don't have a release. This does make the table
look a little funny (as the earliest release is the series eol tag :()
but I'm not sure how we can do better there.
Change-Id: Ie8e60dc865ab301539c0bb085a52dd25f3f62edf
This is the first step to complete the process which doesn't hold
the whole series of tools available at our disposition in the repo.
Change-Id: I6468fb176d85d0b79cccf6746b8af7a127217b00
This is a proposed schedule for the Train release.
Change-Id: Id2b50afa05a2b94da9d92520ba7f49a153973276
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Ultimately we'll do this dynamically but as a POC lets use the existing
.htaccess file[1] to add them statically. This allows us to test the
end results while we work out how to do this correctly *and* preserve
the current redirect for shade.
[1] This isn't working ATM as until https://review.openstack.org/#/c/638527/
has merged and puppet has been run we don't allow allow any options
in .htaccess.
Change-Id: I3a7d8f8af3d0f1301cbdbcaa5a46e9eb5672a151
Cycle highlights are now a regular part of a release and should
be included in the process document so we can promote and
collect them in a routine manner.
Change-Id: I025c029469e3fae85485b87351da9ec487ff5c89
Introduce the flag `--url` who allow user to generate urls
for the given result.
Introduce the option `--distgit` to allow user to specify
the base url to use to generate urls.
Change-Id: I10d4f92f64a68f283c70c2c880c27a069f123762
This script will compute a list of deliverables present in
governance but unknown to release management, for manual
processing.
Change-Id: Ibebf777911416d978ecea5ba8d7b25b211e7ae52
Add both TC and PTL elections to the schedule. Due to this cycle being
slight different because of the scheduling of the summit, forum and PTG
at essentially the same time we'll have only a single email deadline and
the confirmation of the TC election dates implies the PTL election
dates.
Depends-On: https://review.openstack.org/629693
Change-Id: Ia5ec78a123fbe73e544cc5557f7ae1ebd7a7197d
Due to the timing of the Spring summit during the 'Stein' Release we
will hold 2 TC elections. This change add the release name to the
headings.
Also the TC election is a Cross-project event so move it into that
section. As there will be more than one election demote the style
Change-Id: If25ca22a336d8675ee8126bb1de2821e40f81551
Remove the governance code in this repository and use the new
openstack_governance library instead.
Depends-On: https://review.openstack.org/614605
Change-Id: Ia7ffff3945462f4b568b55287dfdf45fe73a35d9
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
We had sphinx extensions in multiple locations. This centralized them
under the doc/source tree.
Change-Id: Ieda73fb4b51ed78409423c41eaddacda199abddc
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Following the discussion at the Denver PTG about simplifying the
process for feature-complete, superstable OpenStack libraries,
update the documentation to mention the possibility of transitioning
to an independent model.
http://lists.openstack.org/pipermail/openstack-dev/2018-September/135206.html
Change-Id: I66ee74a1c57abadd5f759a95a5a643378dd79a4a
Task: 26444
Adds descriptions and references to the cycle-with-rc model.
Change-Id: I734a9344ce6b2456611708e59bbdd32c0403400e
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
