oslo-specs/specs/policy
Joshua Harlow 1ad2d8fda4 Add a new library policy and process proposal
Quite often Oslo is requested to create (or adopt) new libraries
for various purposes and it would be good to (as a group) have a
stance on new libraries and the process they need to go through
to either become a new library in Oslo or to become a new library
that is independently maintained on pypi.

Co-Authored-By: ChangBo Guo(gcb) <eric.guo@easystack.cn>
Change-Id: Ib1ed8aad4859ca8313ac841fb9a57db1d08a2f10
2017-10-19 08:32:04 +00:00
..
feature-freeze.rst Add feature freeze policy 2015-02-25 14:16:05 -06:00
incubator.rst Add adoption timeline to incubator policy 2015-02-17 18:13:55 -05:00
liaisons.rst Add revision history sections 2015-02-17 18:13:55 -05:00
naming-libraries.rst Add revision history sections 2015-02-17 18:13:55 -05:00
new-libraries.rst Add a new library policy and process proposal 2017-10-19 08:32:04 +00:00
policy-merge.rst Fix typos in oslo-specs 2016-11-04 01:12:16 +00:00
private-symbols.rst Add revision history sections 2015-02-17 18:13:55 -05:00
release-note-management.rst add a policy documenting how we manage release notes 2016-02-23 17:57:46 -05:00
spec-approval.rst add references to spec approval policy 2015-02-19 16:46:46 -05:00
test-tools.rst Refactor oslotest base class into fixtures 2015-04-27 15:39:20 +00:00
versioning.rst Add revision history sections 2015-02-17 18:13:55 -05:00