3edd778613
The idea of policies is to document something related to the project that isn't tied to a specific release and often isn't related to code. For example, a policy could be related to how we organise or how we agree to do code reviews. This process is inspired by the policies used in TripleO and the policy template is a direct copy of the one used in TripleO. Change-Id: I05f5076a1559790bf6d0f7b68d528748a2acd20b
1.5 KiB
1.5 KiB
OpenStack Mistral Project Plans
Approved specifications
These specifications have been approved but have not been completely implemented. Approved specifications are grouped in the development cycles. If a specification has been approved but not completed within one or more releases since the approval, it may be re-reviewed to make sure it still makes sense as written. So, a specification may be seen in different groups:
Mitaka
specs/mitaka/approved/*
Newton
specs/newton/approved/*
Ocata
specs/ocata/approved/*
Implemented specifications
These specifications have been implemented and are grouped by the development cycles in which they were completed.
Mitaka
specs/mitaka/implemented/*
Newton
specs/newton/implemented/*
Ocata
specs/ocata/implemented/*
Mistral Project Policies
Team decisions and policies that are not limited to a specific release.
specs/policy/*
Indices and tables
search