cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giles Sirett <giles.sir...@shapeblue.com>
Subject RE: [PROPOSE] RM for 4.11
Date Thu, 30 Nov 2017 11:29:18 GMT
We built said statue at collab in Miami this year..........
https://twitter.com/shapeblue/status/936194768589254656


Kind regards
Giles

giles.sirett@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 


-----Original Message-----
From: Nux! [mailto:nux@li.nux.ro] 
Sent: 29 November 2017 16:25
To: dev <dev@cloudstack.apache.org>
Subject: Re: [PROPOSE] RM for 4.11

That's great, Rohit!

I'm in talks with some folks to build you a statue. ;-) (Hope it'll turn out better than Ronaldo's..)

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

----- Original Message -----
> From: "Rohit Yadav" <bhaisaab@apache.org>
> To: "dev" <dev@cloudstack.apache.org>
> Sent: Wednesday, 29 November, 2017 10:14:54
> Subject: [PROPOSE] RM for 4.11

> Hi All,
> 
> I’d like to put myself forward as release manager for 4.11. The 4.11 
> releases will be the next major version LTS release since 4.9 and will 
> be supported for 20 months per the LTS manifesto [2] until 1 July 2019.
> 
> Daan Hoogland and Paul Angus will assist during the process and all of 
> us will be the gatekeepers for reviewing/testing/merging the PRs, 
> others will be welcome to support as well.
> 
> As a community member, I will try to help get PRs reviewed, tested and 
> merged (as would everyone else I hope) but with an RM hat on I would 
> like to see if we can make that role less inherently life-consuming 
> and put the onus back on the community to get stuff done.
> 
> Here the plan:
> 1. As RM I put forward the freeze date of the 8th of January 2018, 
> hoping for community approval.
> 2. After the freeze date (8th Jan) until GA release, features will not 
> be allowed and fixes only as long as there are blocker issues outstanding.
> Fixes for other issues will be individually judged on their merit and risk.
> 3. RM will triage/report critical and blocker bugs for 4.11 [4] and 
> encourage people to get them fixed.
> 4. RM will create RCs and start voting once blocker bugs are cleared 
> and baseline smoke test results are on par with previous 
> 4.9.3.0/4.10.0.0 smoke test results.
> 5. RM will allocate at least a week for branch stabilization and testing.
> At the earliest, on 15th January, RM will put 4.11.0.0-rc1 for voting 
> from the 4.11 branch, and master will be open to accepting new features.
> 6. RM will repeat 3-5 as required. Voting/testing of -rc2, -rc3 and so 
> on will be created as required.
> 7. Once vote passes - RM will continue with the release procedures [1].
> 
> In conjunction with that, I also propose and put forward the date of 
> 4.12 cut-off as 4 months [3] after GA release of 4.11 (so everyone 
> knows when the next one is coming hopefully giving peace of mind to 
> those who have features which would not make the proposed 4.11 cut off).
> 
> I’d like the community (including myself and colleagues) to:
> - Up to 8th January, community members try to review, test and merge 
> as many fixes as possible, while super-diligent to not de-stabilize 
> the master branch.
> - Engage with gatekeepers to get your PRs reviewed, tested and merged 
> (currently myself, Daan and Paul, others are welcome to engage as 
> well). Do not merge the PRs
> - A pull request may be reverted where the author(s) are not 
> responding and authors may be asked to re-submit their changes after 
> taking suitable remedies.
> - Find automated method to show (at a glance) statuses of PRs with 
> respect
> to:
>  · Number of LGTMs
>  · Smoke tests
>  · Functional tests
>  · Travis tests passing
>  · Mergeability
> - Perform a weekly run of a component-test matrix against the master 
> branch before Jan 8th cut off (based on current hypervisors including 
> basic (KVM) and advanced networking).
> - Continue to fix broken tests.
> 
> Thoughts, feedback, comments?
> 
> [1] 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+Procedu
> re [2] https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS
> [3] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Releases
> [4] The current list of blocker and critical bugs currently stands as 
> per the following list:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20CLOUDSTACK%
> 20AND%20issuetype%20%3D%20Bug%20AND%20status%20in%20(Open%2C%20%22In%2
> 0Progress%22%2C%20Reopened)%20AND%20priority%20in%20(Blocker%2C%20Crit
> ical)%20AND%20affectedVersion%20in%20(4.10.0.0%2C%204.10.1.0%2C%204.11
> .0.0%2C%20Future)%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
> 
> Regards,
> Rohit Yadav
Mime
View raw message