Over the winter there was a Quality Improvement Initiative that was looking at how to make contribution to CloudStack easier and improve quality of the product. Basically it was a lot of discussion [2] about CI and how to use GIT,...
It also look like github pull request as became quite popular, we almost have too much ressource into our jenkins system. So, why not leverage this for the next coming release, ACS460? During the QA period of 4.4.0 Daan, was doing the Release manager and enforce the use of merge request from branches instead of direct commit into 4.4 branch, I think it worked well and help knowing what endup into hotfixe releases (4.4.1,4.4.2). So, I'd like to propose to change few things on how we contribute for 4.6 releases. 1. emphasis github pull request, merge request, no direct commit into 4.6 branch unless it's minor changes. 2. improve CI, start using the fastsimulator [1] on pull request, maybe some kind of gated commit [3]. 3. test this workflow. Since master branch already contain a lot of new features ready to be tested and used, I'm wondering if we could also speedup the release process. Instead of waiting for all features to be ready to do RC of 4.6.0, release 4.6.0 without incomplete features, and as they are ready adding them into 4.6.1, 4.6.2. Please comment :-) [1] http://markmail.org/search/list:org.apache.incubator.cloudstack-*?q=CI+improvment+part+1 [2] http://markmail.org/search/list:org.apache.incubator.cloudstack-*?q=Quality+Improvement [3] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Quality+and+Process+Improvement+Initiative
