Monasca Project Plans¶
At the beginning of each release cycle we agree what the whole community wants to focus on for the upcoming release. This is the output of those discussions:
Here you can find the specs, and spec template, for each release:
There are also some approved backlog specifications that are looking for owners:
The lifecycle of a specification¶
Developers proposing a specification should propose a new file in the
approved directory. monasca-specs-core will review the change in the usual
manner for the OpenStack project and eventually it will get merged if a
consensus is reached. As the developer of an approved specification, it is your
responsibility to assign tasks to your story. Developers are then free to
propose code reviews to implement their specification. These reviews should be
sure to reference the Storyboard story and task in their commit message for
Once all code for the feature is merged into Monasca, the Storyboard story is marked complete.
Periodically, someone from monasca-specs-core will move implemented
specifications from the
approved directory to the
directory. Whilst individual developers are welcome to propose this move for
their implemented specifications, we have generally just done this in a batch
at the end of the release cycle. It is important to create redirects when this
is done so that existing links to the approved specification are not broken.
Redirects aren’t symbolic links, they are defined in a file which sphinx
This directory structure allows you to see what we thought about doing,
decided to do and actually got done. Users interested in functionality in a
given release should only refer to the
You can find an example spec in
Additionally, we allow the proposal of specifications that do not have a developer assigned to them. These are proposed for review in the same manner as above, but are added to:
Specifications in this directory indicate the original author has either become unavailable or has indicated that they are not going to implement the specification. The specifications found here are available as projects for people looking to get involved with Monasca. If you are interested in claiming a spec, start by posting a review for the specification that moves it from this directory to the next active release. Please set yourself as the new primary assignee and maintain the original author in the other contributors list.
Working with gerrit and specification unit tests¶
For more information about working with gerrit, see http://docs.openstack.org/infra/manual/developers.html#development-workflow
To validate that the specification is syntactically correct (i.e. get more confidence in the Jenkins result), please execute the following command:
tox, the documentation will be available for viewing in HTML
format in the
Specification review policies¶
There are a number of review policies which monasca-specs-core will apply when reviewing proposed specifications. They are:
Proposed changes which are trivial (very small amounts of code) and don’t change any of our public APIs are sometimes not required to provide a specification. In these cases a Storyboard story is considered sufficient. These proposals are approved during the Open Discussion portion of the weekly Monasca IRC meeting. If you think your proposed feature is trivial and meets these requirements, we recommend you bring it up for discussion there before writing a full specification.
Previously approved specifications¶
Specifications are only approved for a single release. If your specification was previously approved but not implemented (or not completely implemented), then you must seek re-approval for the specification. You can re-propose your specification by doing the following:
Copy (not move) your specification to the right directory for the current release.
Update the document to comply with the new template.
If there are no functional changes to the specification (only template changes) then add the Previously-approved: <release> tag to your commit message.
Send for review.
monasca-specs-core will merge specifications which meet these requirements with a single +2.
Specifications which depend on merging code in other OpenStack projects¶
For specifications that depend on code in other OpenStack projects merging we will not approve the Monasca specification until the code in that other project has merged. To indicate your specification is in this state, please use the Depends-On git commit message tag. The correct format is Depends-On: <change id of other work>. monasca-specs-core can approve the specification at any time, but it won’t merge until the code we need to land in the other project has merged as well.