<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Nice!<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 13, 2015, at 1:03 AM, Boris Pavlovic <<a href="mailto:boris@pavlovic.me" class="">boris@pavlovic.me</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi stackers, <div class=""><br class=""></div><div class="">For those who doesn't know Rally team started making releases. </div><div class=""><br class=""></div><div class="">There are 3 major reasons why we started doing releases: </div><div class=""><br class=""></div><div class=""> * A lot of people started using Rally in their CI/CD. </div><div class=""><br class=""></div><div class=""> Usually they don't like to depend on something that is from master.</div><div class=""> And would like to have smooth testable upgrades between versions </div><div class=""><br class=""></div><div class=""> * Rally is used in gates of many projects. </div><div class=""><br class=""></div><div class=""> As far as you know in Rally everything is plugable. These plugins can be</div><div class=""> put in project tree. This is nice flexibility for all projects. But it blocks a lot</div><div class=""> development of Rally. To resolve this issue we are going to allow projects t</div><div class=""> specify which version of Rally to run in their trees. This resolves 2 issues:</div><div class=""> 1) projects gates won't depend on Rally master </div><div class=""> 2) projects have smooth, no downtime, testable way to switch to newer</div><div class=""> version of Rally </div><div class=""><br class=""></div><div class=""> * Release notes - as a simple way to track project changes. </div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Release stats: </div><div class=""><div class=""><font face="monospace, monospace" class="">+------------------+-----------------+</font></div><div class=""><font face="monospace, monospace" class="">| Commits | **100** |</font></div><div class=""><font face="monospace, monospace" class="">+------------------+-----------------+</font></div><div class=""><font face="monospace, monospace" class="">| Bug fixes | **18** |</font></div><div class=""><font face="monospace, monospace" class="">+------------------+-----------------+</font></div><div class=""><font face="monospace, monospace" class="">| Dev cycle | **45 days** |</font></div><div class=""><font face="monospace, monospace" class="">+------------------+-----------------+</font></div><div class=""><font face="monospace, monospace" class="">| Release date | **12/Mar/2015** |</font></div><div class=""><font face="monospace, monospace" class="">+------------------+-----------------+</font></div></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Release notes: </div><div class=""><br class=""></div><div class=""><a href="https://rally.readthedocs.org/en/latest/release_notes/v0.0.2.html" class="">https://rally.readthedocs.org/en/latest/release_notes/v0.0.2.html</a><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Pypi:</div><div class=""><br class=""></div><div class=""><a href="https://pypi.python.org/pypi/rally/0.0.2" class="">https://pypi.python.org/pypi/rally/0.0.2</a><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Future goals: </div><div class=""><br class=""></div><div class="">Our goal is to cut releases ever 2 weeks. As far as project is quite bugless and stable we don't need feature freeze at all, so I don't think that it will be hard to achieve this goal. </div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Best regards,</div><div class="">Boris Pavlovic </div></div>
__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></blockquote></div><br class=""></div></body></html>