"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "doc/source/process.rst" between
masakari-8.0.0.tar.gz and masakari-9.0.0.tar.gz

About: OpenStack Masakari provides "Instances High Availability Service" for OpenStack clouds by automatically recovering failed Instances (currently for KVM-based Virtual Machine(VM)s).
The "Ussuri" series (latest release).

process.rst  (masakari-8.0.0):process.rst  (masakari-9.0.0)
skipping to change at line 22 skipping to change at line 22
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
License for the specific language governing permissions and limitations License for the specific language governing permissions and limitations
under the License. under the License.
.. _process: .. _process:
===================== =====================
Masakari team process Masakari team process
===================== =====================
Masakari is always evolving its processes, but it's important to explain why we Masakari is always evolving its processes to ensure productive communication
have them: so we can all work to ensure that the interactions we need to between all members of our community easily.
happen do happen. The process exists to make productive communication between
all members of our community easier.
OpenStack Wide Patterns OpenStack Wide Patterns
======================= =======================
Masakari follows most of the generally adopted norms for OpenStack projects. Masakari follows most of the generally adopted norms for OpenStack projects.
You can get more details here: You can get more details here:
* https://docs.openstack.org/infra/manual/developers.html * https://docs.openstack.org/infra/manual/developers.html
* https://docs.openstack.org/project-team-guide/ * https://docs.openstack.org/project-team-guide/
skipping to change at line 53 skipping to change at line 51
You can get most of your questions answered here: You can get most of your questions answered here:
- https://docs.openstack.org/infra/manual/developers.html - https://docs.openstack.org/infra/manual/developers.html
But let's put a Masakari specific twist on things... But let's put a Masakari specific twist on things...
Overview Overview
~~~~~~~~ ~~~~~~~~
.. image:: ./images/Masakari_spec_process.svg .. image:: /_static/Masakari_spec_process.svg
:alt: Flow chart showing the Masakari bug/feature process :alt: Flow chart showing the Masakari bug/feature process
Where do you track bugs? Where do you track bugs?
~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~
We track bugs here: We track bugs here:
- https://bugs.launchpad.net/masakari - https://bugs.launchpad.net/masakari
If you fix an issue, please raise a bug so others who spot that issue If you fix an issue, please raise a bug so others who spot that issue
can find the fix you kindly created for them. can find the fix you kindly created for them.
Also before submitting your patch it's worth checking to see if someone Also before submitting your patch it's worth checking to see if someone
has already fixed it for you (Launchpad helps you with that, at little, has already fixed it for you (Launchpad helps you with that, at little,
when you create the bug report). when you create the bug report).
When do I need a blueprint vs. a spec? When do I need a blueprint vs. a spec?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To understand this question, we need to understand why blueprints and To understand this question, we need to understand why blueprints and
specs are useful. specs are useful.
But here is the rough idea: But here is the rough idea:
- if it needs a spec, it will need a blueprint. - if it needs a spec, it will need a blueprint.
- if it's an API change, it needs a spec. - if it's an API change, it needs a spec.
- if it's a single small patch that touches a small amount of code, - if it's a single small patch that touches a small amount of code,
with limited deployer and doc impact, it probably doesn't need a with limited deployer and doc impact, it probably doesn't need a
 End of changes. 3 change blocks. 
6 lines changed or deleted 4 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)