Thierry Carrez 75595d6ce4 Move preversion check into validate ...

Pre-versions are only OK if you're using a release model
that allows for them (like cycle-with-milestones). Now that we
have the information in the releases file, move the warning
in list-changes to a proper validation failure.

Change-Id: Ifb91bd2446b6d37dc9bb4601cad28f29c065c2e8

2016-11-16 17:31:46 +01:00

..

cmds

Move preversion check into validate

2016-11-16 17:31:46 +01:00

__init__.py

Refactor validation script

2015-07-23 17:33:03 +00:00

defaults.py

update the default series to ocata

2016-09-28 15:15:45 -04:00

deliverable.py

maintain team ownership info in the deliverable files

2016-06-09 14:34:21 -04:00

flags.py

add a "retired" flag for repositories

2016-06-09 14:17:51 -04:00

gitutils.py

add check-diff-start command

2016-10-05 11:19:00 -04:00

governance.py

move deliverable type into deliverable files

2016-11-09 17:09:03 -05:00

project_config.py

add a separate release type for fuel

2016-10-13 20:10:48 +00:00

sphinxext.py

use local type and model data for releases.openstack.org

2016-11-09 17:09:03 -05:00

versionutils.py

Move preversion check into validate

2016-11-16 17:31:46 +01:00

yamlutils.py

Don't try to re-wrap things that already have newlines

2016-06-13 11:41:53 -07:00