You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Remi Bergsma <RB...@schubergphilis.com> on 2016/01/27 14:08:45 UTC
New release manager wanted
Hi all,
After picking up the RM role last summer, I've had an interesting ride with awesome results. First the release principles [1], then stabilizing master and finally 3 releases in a row: 4.6 in November, 4.7 in December and 4.8 in January (and as a bonus 3 more patch releases in between). As Seb pointed out, we could start a new vote at any time and release it. Given that we keep master stable, of course.
Hundreds of Pull Requests got merged and each one has had a series of integration tests executed [2] before merge. That drove quality and velocity.
I’m proud of the results we achieved and I’m also proud of the people who helped make it happen!
The other side of the story, is that it took me a GREAT amount of time to do this. Schuberg Philis allowed me to work on it during the day, and next to that I also spent many many evenings and weekends working on it. Right now, I feel it’s time to scale that down again to normal proportions. I will continue to contribute, but I just won't take the lead for now.
Long story short, please step up if you want to take over the RM role. I'd be happy to provide some guide lines and help.
Regards,
Remi
[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+principles+for+Apache+CloudStack+4.6+and+up
[2] https://github.com/schubergphilis/MCT-shared
Re: New release manager wanted
Posted by Wei ZHOU <us...@gmail.com>.
Thanks a lot for your hard work, Remi !
2016-01-27 14:08 GMT+01:00 Remi Bergsma <RB...@schubergphilis.com>:
> Hi all,
>
>
> After picking up the RM role last summer, I've had an interesting ride
> with awesome results. First the release principles [1], then stabilizing
> master and finally 3 releases in a row: 4.6 in November, 4.7 in December
> and 4.8 in January (and as a bonus 3 more patch releases in between). As
> Seb pointed out, we could start a new vote at any time and release it.
> Given that we keep master stable, of course.
>
>
> Hundreds of Pull Requests got merged and each one has had a series of
> integration tests executed [2] before merge. That drove quality and
> velocity.
>
>
> I’m proud of the results we achieved and I’m also proud of the people who
> helped make it happen!
>
>
> The other side of the story, is that it took me a GREAT amount of time to
> do this. Schuberg Philis allowed me to work on it during the day, and next
> to that I also spent many many evenings and weekends working on it. Right
> now, I feel it’s time to scale that down again to normal proportions. I
> will continue to contribute, but I just won't take the lead for now.
>
>
> Long story short, please step up if you want to take over the RM role. I'd
> be happy to provide some guide lines and help.
>
>
> Regards,
>
> Remi
>
>
> [1]
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+principles+for+Apache+CloudStack+4.6+and+up
>
> [2] https://github.com/schubergphilis/MCT-shared
>
>
>
Re: New release manager wanted
Posted by Nux! <nu...@li.nux.ro>.
Thanks a lot for your work Remi, it has been a great run and the quality of ACS is the highest it has ever been.
It was an excellent year with you as RM and Sebastien as VP, let's hope we can continue to live up to this standard.
And let's keep master stable, of course! :)
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
----- Original Message -----
> From: "Wilder Rodrigues" <WR...@schubergphilis.com>
> To: dev@cloudstack.apache.org
> Sent: Wednesday, 27 January, 2016 18:18:51
> Subject: Re: New release manager wanted
> Thanks for ll the hard work and support, Remi! We worked quite some weekends
> testing PRs in order to get them merged properly, following the guidelines: 2
> LGTM (1 being code review; 1 being integration tests)
>
> I hope that the same principle will now be taken as a standard.
>
> Thanks again!
>
> Cheers,
> Wilder
>
>
>
>> On 27 Jan 2016, at 14:08, Remi Bergsma <RB...@schubergphilis.com> wrote:
>>
>> Hi all,
>>
>>
>> After picking up the RM role last summer, I've had an interesting ride with
>> awesome results. First the release principles [1], then stabilizing master and
>> finally 3 releases in a row: 4.6 in November, 4.7 in December and 4.8 in
>> January (and as a bonus 3 more patch releases in between). As Seb pointed out,
>> we could start a new vote at any time and release it. Given that we keep master
>> stable, of course.
>>
>>
>> Hundreds of Pull Requests got merged and each one has had a series of
>> integration tests executed [2] before merge. That drove quality and velocity.
>>
>>
>> I’m proud of the results we achieved and I’m also proud of the people who helped
>> make it happen!
>>
>>
>> The other side of the story, is that it took me a GREAT amount of time to do
>> this. Schuberg Philis allowed me to work on it during the day, and next to that
>> I also spent many many evenings and weekends working on it. Right now, I feel
>> it’s time to scale that down again to normal proportions. I will continue to
>> contribute, but I just won't take the lead for now.
>>
>>
>> Long story short, please step up if you want to take over the RM role. I'd be
>> happy to provide some guide lines and help.
>>
>>
>> Regards,
>>
>> Remi
>>
>>
>> [1]
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+principles+for+Apache+CloudStack+4.6+and+up
>>
>> [2] https://github.com/schubergphilis/MCT-shared
>>
Re: New release manager wanted
Posted by Wei ZHOU <us...@gmail.com>.
Totally agree.
-Wei
2016-01-27 19:18 GMT+01:00 Wilder Rodrigues <WR...@schubergphilis.com>:
> Thanks for ll the hard work and support, Remi! We worked quite some
> weekends testing PRs in order to get them merged properly, following the
> guidelines: 2 LGTM (1 being code review; 1 being integration tests)
>
> I hope that the same principle will now be taken as a standard.
>
> Thanks again!
>
> Cheers,
> Wilder
>
>
>
> > On 27 Jan 2016, at 14:08, Remi Bergsma <RB...@schubergphilis.com>
> wrote:
> >
> > Hi all,
> >
> >
> > After picking up the RM role last summer, I've had an interesting ride
> with awesome results. First the release principles [1], then stabilizing
> master and finally 3 releases in a row: 4.6 in November, 4.7 in December
> and 4.8 in January (and as a bonus 3 more patch releases in between). As
> Seb pointed out, we could start a new vote at any time and release it.
> Given that we keep master stable, of course.
> >
> >
> > Hundreds of Pull Requests got merged and each one has had a series of
> integration tests executed [2] before merge. That drove quality and
> velocity.
> >
> >
> > I’m proud of the results we achieved and I’m also proud of the people
> who helped make it happen!
> >
> >
> > The other side of the story, is that it took me a GREAT amount of time
> to do this. Schuberg Philis allowed me to work on it during the day, and
> next to that I also spent many many evenings and weekends working on it.
> Right now, I feel it’s time to scale that down again to normal proportions.
> I will continue to contribute, but I just won't take the lead for now.
> >
> >
> > Long story short, please step up if you want to take over the RM role.
> I'd be happy to provide some guide lines and help.
> >
> >
> > Regards,
> >
> > Remi
> >
> >
> > [1]
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+principles+for+Apache+CloudStack+4.6+and+up
> >
> > [2] https://github.com/schubergphilis/MCT-shared
> >
> >
>
>
Re: New release manager wanted
Posted by Wilder Rodrigues <WR...@schubergphilis.com>.
Thanks for ll the hard work and support, Remi! We worked quite some weekends testing PRs in order to get them merged properly, following the guidelines: 2 LGTM (1 being code review; 1 being integration tests)
I hope that the same principle will now be taken as a standard.
Thanks again!
Cheers,
Wilder
> On 27 Jan 2016, at 14:08, Remi Bergsma <RB...@schubergphilis.com> wrote:
>
> Hi all,
>
>
> After picking up the RM role last summer, I've had an interesting ride with awesome results. First the release principles [1], then stabilizing master and finally 3 releases in a row: 4.6 in November, 4.7 in December and 4.8 in January (and as a bonus 3 more patch releases in between). As Seb pointed out, we could start a new vote at any time and release it. Given that we keep master stable, of course.
>
>
> Hundreds of Pull Requests got merged and each one has had a series of integration tests executed [2] before merge. That drove quality and velocity.
>
>
> I’m proud of the results we achieved and I’m also proud of the people who helped make it happen!
>
>
> The other side of the story, is that it took me a GREAT amount of time to do this. Schuberg Philis allowed me to work on it during the day, and next to that I also spent many many evenings and weekends working on it. Right now, I feel it’s time to scale that down again to normal proportions. I will continue to contribute, but I just won't take the lead for now.
>
>
> Long story short, please step up if you want to take over the RM role. I'd be happy to provide some guide lines and help.
>
>
> Regards,
>
> Remi
>
>
> [1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+principles+for+Apache+CloudStack+4.6+and+up
>
> [2] https://github.com/schubergphilis/MCT-shared
>
>