Open Stack

Hi stackers,

As far as you probably know Rally is using independent release model.

We are doing this to do releases as fast as possible.
Our goal is to have release at least 1 times per 2 week.

The major reason why we have to have separated release model is that we
should ship plugins as soon as possible and plugins are in the same repo
with tool, framework and docs.

Previous model was quite simple, we were planing changes for next release,
reviewing and merging those changes and cutting new versions.

This model worked well until we started doing things that are not fully
backward compatible and requires migrations.

Like 0.1.0 release will take us more then 100 days, which is terrible long
for people who is waiting new plugins.

I would like to propose the new release model that will allow us to do 2
things:
* Do the regular, fast releases with new plugins
* Have a months for developing new features and changes that are not fully
backward compatible

The main idea is next:
*) Master branch will be used for new major Rally versions development e.g.
0.x.y -> 0.x+1.0 switch
   that can include not backward compatible changes.
*) Latest version - we will port plugins, bug fixes and part of features to
it
*) Stable version - we will port only high & critical bug fixes if it is
possible

Here is the diagram that explains the release cycle:

[image: Inline image 1]

Thoughts?

Best regards,
Boris Pavlovic
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150920/4c69d849/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Rally Release Cycles.png
Type: image/png
Size: 15481 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150920/4c69d849/attachment.png>