Add some technical graduation requirements
A first cut at some things which are obvious and others which are worth discussing: 1) REST API - we say only server projects go through incubation 2) API stability - think we want a commitment to this 3) Python client library - seems to be an unstated requirement 4) Heat integration - most controversial, but is it that different from the client lib requirement? Do we want Heat to end up with support for only some projects? 5) Horizon integration - same here too, why is it so different from the client library requirement? Change-Id: Ifce4262fcec22a2cbe9880a984b46f3c082830b1
This commit is contained in:
parent
5227c72a45
commit
fd1389a51d
|
@ -77,6 +77,15 @@ requirements, including (but not limited to):
|
|||
name
|
||||
** Project must use OpenStack task, defect and design tracker(s)
|
||||
|
||||
* Technical
|
||||
** Project must have a REST API with at least a JSON entity representation
|
||||
** The REST API must be declared stable and the project must commit to
|
||||
maintaining backwards compatibility
|
||||
** Project must have a Python client library for its REST API
|
||||
** Project must have Heat integration such that its resource can be provisioned
|
||||
via a Heat template
|
||||
** Project must be usable via the Horizon dashboard
|
||||
|
||||
* QA
|
||||
** Project must be part of the integrated gate
|
||||
** Project must have decent unit test and functional tests coverage
|
||||
|
|
Loading…
Reference in New Issue