Commit Graph

14 Commits

Author SHA1 Message Date
Slawek Kaplonski d531e274d5 Fix py27 job in specs repo
In py27 job index.rst file was checked as any other file if it
contains required headers and sections.
But index.rst file has different format so this file should be
skipped in this test.

After that there was also issue with unexpected "Footnotes"
section in neutron-inter.rst specs so this was also fixed.

Change-Id: If2baf887c49025a5481e97b2fb3500736b8668b6
2018-05-30 10:28:57 +02:00
Armando Migliaccio 2ba99041c6 Add Stadium project scorecard
This template will be used to assess Neutron Stadium projects.

Change-Id: I146a3e32d2b72b28b407c08fdab6218697bf6a98
2016-10-13 16:06:30 -07:00
Armando Migliaccio cab59cc0b2 Provide a release postmortem
This patch introduces a postmortem template for the
Neutron project, and brings a draft for the Mitaka
release that would need to be filled with the help
of the Mitaka contributors before Mitaka is released.

Change-Id: I30aac4e8adf57ab891f47cb7c4841d55c1422e00
2016-04-14 22:06:45 +00:00
armando-migliaccio 415f1eaf5b Revisit the structure of the specs repo
Instead of having a per-release backlog directory, create
a top level one that holds the last release backlog. In
a healthy project this directory is really meant to be
empty or only temporary filled.

For specs that are two releases older, the content will
be moved to an 'archive' directory, purely for the record.
Hopefully this one too will be empty.

API and Juno incubator were moved to a miscellanea
directory to finish off the cleanup.

Finally, some blueprints completed and therefore were
moved to the Liberty directory.

Change-Id: I972a9a56c038864d9c91ead6944c6b9355916668
2015-10-28 21:55:08 +00:00
Doug Wiegley 81ceb74eb5 Shorten the spec template greatly.
Since neutron is moving to using RFE's for features, only the larger
or contentious features will require specs. This change removes many
of the spec sections that will become redundant with the information
included in the RFE itself and the devref developer docs that are now
expected with the code.

Also, tweak the py27 test to accept both old and new spec formats

Change-Id: I5aeb2cb39740ac85e0485f4e26d6fb380bd4d271
2015-05-27 17:39:26 -06:00
Russell Bryant 9a16333a93 Refactor test against template
test_titles originated in nova-specs.  The version in nova-specs has
received several improvements that would be worth bringing over.  This
started when I was writing a spec and the test code wouldn't let me
add any additional sections on top of the required ones.

Here's a list of key differences in the new version:

* Instead of hard coding the list of required sections, dynamically
  discover the sections by reading the template.

* Ensure all sections from the template are present, but allow
  additional sections to be included.

* Include the code for ensuring lines are wrapped, but disable it for
  now since it doesn't pass.

* Make sure the spec doesn't have \r in it.

* Make sure the spec doesn't have trailing whitespace.

Also include a one line spec change to remove trailing whitespace so
the tests pass.

Change-Id: I15576e46ab34bf95ec8e0fc8066baad78460ceef
2014-12-15 12:49:49 -05:00
Kyle Mestery c3afb3147e Add an "IPv6 Impact" section to the template
This change adds a requirement for an "IPv6 Impact" section. In the review for
Kilo priorities [1], the issue was raised around IPv6 being a priority. One
outcome was the thought to ensure new features are IPv6 ready from the start.
This change ensures specs have a section detailing how they affect IPv6.

I've also updated approved specs with what I perceive to be their IPv6
readiness. I hope the original authors can view these to confirm what I've
put in there.

[1] https://review.openstack.org/#/c/136514/

Change-Id: I6b12615d5d650ea55b8e78fd43c702af8f87b3f7
2014-11-24 08:40:43 +00:00
Kyle Mestery 8a524f54c7 Reformat template.rst.
Change the layout of this file to move the formatting examples to the bottom
to move clearly highlight the operator requirements section at the top. Also
update the test infrastructure to reflect the changes, and also only run
unit tests on the kilo specs.

Change-Id: Ie5e0c2779e69585c1800d6ecaf9062f3d2d81cbb
2014-09-25 13:44:48 +00:00
Kevin Benton c645491454 Move title length check after name check
Don't check the number of titles in the spec until
after the individual sections are checked for. This
makes it easier to find which section is missing
by having an assertIn failure for the name instead
of an assertEqual failure on the length.

Change-Id: I0761c0a2f70d53c7be204ef76d7256902f900caa
2014-07-10 22:12:43 -07:00
Sean M. Collins 5807aa1d1c Ensure skeleton.rst is tested
Change-Id: I07bb43de6145efa45f9027ef2f0d1856c658033c
2014-05-21 16:45:21 -04:00
Jenkins 03ec632b72 Merge "Added Sphinx diagram tools" 2014-04-18 19:50:06 +00:00
Nachi Ueno 9ae6b365f3 Added Sphinx diagram tools
Added some tools and example
- blockdiag for block diagram
- nwdiag for network diagram
- actdiag for act diagram
- seqdiag for sequence diagram

Change-Id: Idc709dca40f756a66beca5ab5da2a377b04338d2
2014-04-17 21:11:15 +00:00
Carl Baldwin d76bec4015 Allow adding sub-headings under Proposed change header
This changes the titles test under the "Proposed change" heading so
that it checks that *at least* the required 9 headings exist instead
of checking that *exactly* the required 9 headings exist.

This will allow writers like me to add some structure to the first
section under this heading before getting to the required sections.

Change-Id: I507d32cb2568d9c65b7a460196fdd873c4c5c445
2014-04-17 12:16:10 -06:00
Kyle Mestery 4f354e9fd2 Add base neutron-specs framework
Build the base framework for the neutron-specs repository. This was taken
from the nova-specs repository and has been slightly tweaked for neutron.

Change-Id: I1f3ce2f1992491e1420a2f35e97a06b6b604f9e0
2014-04-14 03:08:02 +00:00