openstack/nova-specs - nova-specs - OpenDev: Free Software Needs Free Tools

We have previously published the kilo template here:
http://specs.openstack.org/openstack/nova-specs/specs/kilo-template.html
and have since updated it. But because we removed it from the toctree
it is not being updated on the website.
This change adds just the kilo template back into the toctree.
Change-Id: I8bdaef79439bf2f49a979c16de22c7aa6d7e2fcb

Change-Id: I7ff35e7910896fb46c43ec39d22a130e58faaf49

We don't want the templates to show up in the RSS feed, so exclude them
from being converted to HTML and listed in the toctree.
Change-Id: I1d50944fc37f27b5fc67316270cb281e3635b762

Remove intersphinx from the docs build as it triggers network calls that
occasionally fail, and we don't really use intersphinx (links other
sphinx documents out on the internet)
This also removes the requirement for internet access during docs build.
This can cause docs jobs to fail if the project errors out on
warnings.
Change-Id: I71e941e2a639641a662a163c682eb86d51de42fb
Related-Bug: #1368910 

Note that this change includes an addition to the doc
index which is needed to bootstrap the approved directory
for Kilo. Without the change a sphinx warning about
the new spec rst file not being included anywhere causes the
build to fail. And applying the change with an empty approved
directory the pattern match fails and the build fails
Previously-approved: juno
Part of blueprint v2-on-v3-api
Change-Id: Ib8b259f69c9072520acecba167b7b31707bcadaa

Change-Id: Ia44ed986502be7252068f6bf2301e87ff75d1283

As discussed at our nova meetings, reorganize the juno specs into
three directories:
 - proposed: things proposed which weren't approved
 - approved: things we approved but didn't implement
 - implemented: things approved and implemented
The first I suspect is the most controversial. I've done this
because I worry about the case where a future developer wants to
pick up something dropped by a previous developer, but has trouble
finding previous proposed specifications on the topic. Note that
the actual proposed specs for Juno are adding in a later commit.
Change-Id: Idcf55ca37a83d7098dcb7c2971240c4e8fd23dc8

* Add section in kilo-template about project priorities (with a link to
 the kilo priorities document)
* Add in kilo priorities page. Currently this list is empty and we hope
 to fill it out at the summit
* Add the yaml file of priority blueprints that are ready for review.
 This is where we will track which priority blueprints need review.
Change-Id: I339e88f8055a63a9a9423d997da6581f977428c9

Publish an RSS feed of the changes to the specs repository to make the
specs more discoverable.
Change-Id: Ib4f84efab8b3af3ddd47d38d63a91362612bd655

Now that we are publishing the docs from this repo at
http://specs.openstack.org/openstack/nova-specs/ add the README to set
of published documents.
Also cleanup README's rst formatting.
Change-Id: If8bf22bb025611b09269a5e4c1a3e49008f1e713

Just as we did at the beginning of the Havana and Icehouse dev cycles,
we need to reserve a range of DB migrations as the first DB change in
Juno. This will allow a range to be used for migration backports to
Icehouse if needed.
This is a straight forward blueprint that has been implemented for the
last two releases (Havana and Icehouse), so we can use this as a trial
run for our new blueprint review process before we open up all other
spec reviews.
Since this is the first Juno spec, re-add the Juno specs directory to
index.rst.
Related to blueprint backportable-db-migrations-juno.
Change-Id: I791c22b54ac8cd533d6fdc03ea93f12d4a907b23

Comment out specs/juno/* until a spec merges so that the docs can
build without errors.
There is still one warning about man pages with this change in place,
but I believe it will require a change to pbr to suppress.
Change-Id: Id63da83ce6e60c444322072e68c17c97cf983846

* Remove reference to _static, as we don't have that directory doesn't
 exist
* Don't generate a man page
Change-Id: I28710aa35a919d6eb79d1e667f65328db5abd1f0

* Update to reflect new directory structure
* Drop maxdepth to 1, to make the page smaller, otherwise the index will
 include links to each section of each blueprint. And since each
 section will have the same name across bluepints this is useless.
Change-Id: I2a5d94ae26002a884033d27881394a795592fe3f

Update the nova-specs project to use sphinx. This will allow us to
still write our specs using rst, but also have a nice framework for
rendering and publishing the specs if we choose to.
Change-Id: Ib92231acb28bba44abafb7dd554404f542da13a7