[openstack-dev] [searchlight] Liberty release finalization
Tripp, Travis S
travis.tripp at hpe.com
Tue Oct 6 16:19:52 UTC 2015
On 10/6/15, 2:28 AM, "Thierry Carrez" <thierry at openstack.org> wrote:
>The "intermediary" model requires the project following it to be mature
>enough (and the project team following it to be disciplined enough) to
>internalize the QA process.
>In the "with-milestones" model, you produce development milestones and
>release candidates to get the features out early and progressively get
>more and more outside testing on proposed artifacts. It's "ok" if a
>development milestone is revealed to be unusable: that shows lack of
>proper testing coverage, and there is still time to fix things before
>the "real" release.
>In the "intermediary" model, you deliver fully-usable releases that you
>recommend production deployments to upgrade to. There is no alpha, beta
>or RC. You directly tag a release. That means you need to be confident
>enough in your own testing and testing coverage. Mistakes can still
>happen (in which case we rush a subsequent point release) but should
>really be exceptional, otherwise nobody will trust your deliverables.
>This is why we recommend the "intermediary" model to mature projects and
>project teams -- that model requires excellent test coverage and
>discipline inside the team to slow down development as you get closer to
>a release tag and spend time on testing.
>Thierry Carrez (ttx)
Thanks again for the information. After quite a bit of discussion in our IRC channel this morning, we think it does make sense to start with the milestones as recommended. So, I’ve gone ahead and applied the rc1 tag and will follow up with you in the openstack-relmgr-office for next steps!
More information about the OpenStack-dev