Difference between revisions of "Barbican/Integration"
< Barbican
Lisa Clark (talk | contribs) (→Barbican Integration) |
(→Release Management / Security) |
||
Line 19: | Line 19: | ||
== Release Management / Security == | == Release Management / Security == | ||
* Provide a 2+ person team that will handle the Barbican Vulnerability Process. See https://wiki.openstack.org/wiki/Vulnerability_Management for more information. | * Provide a 2+ person team that will handle the Barbican Vulnerability Process. See https://wiki.openstack.org/wiki/Vulnerability_Management for more information. | ||
+ | |||
+ | ** Douglas Mendizabal (redrobot) | ||
+ | ** (hyakuhei) |
Revision as of 20:26, 11 August 2014
Contents
Barbican Integration
As we approach the end of the Juno cycle, the TC will be reviewing the maturity of Barbican for graduation to the Integrated release. Below are some requirements that need attention before the Integration Review. For a full list of requirements see http://git.openstack.org/cgit/openstack/governance/tree/reference/incubation-integration-requirements.rst#n79
Maturity
- Integration with other projects including Dashboard
QA
- "Decent" unit and functional test coverage. - This is an area where we could use more work
Documentation / User Support
- End-user documentation
- API use
- CLI use
- Dashboard use
- Installation/Deployment
- User Support
- Proven history of support both in openstack@ mailing list and Ask OpenStack. - Note that we should confirm with TC whether QA in Launchpad meets this requirement, or if we should be focusing on ask.openstack.org. It seems the two sites are unrelated.
Release Management / Security
- Provide a 2+ person team that will handle the Barbican Vulnerability Process. See https://wiki.openstack.org/wiki/Vulnerability_Management for more information.
- Douglas Mendizabal (redrobot)
- (hyakuhei)