[Development] Staging changes in release branch

Knoll Lars Lars.Knoll at digia.com
Wed Nov 13 20:33:59 CET 2013

On 13/11/13 18:49, "Sean Harmer" <sean.harmer at kdab.com> wrote:

>On Tuesday 12 November 2013 12:46:46 Heikkinen Jani wrote:
>> Hi all,
>> We have agreed in release team that Antti Kokko (irc: ankokko) will
>> all approved changes in release branch and stage all clear ones (fixes
>> P1 & P0 issues) automatically. Unclear changes (p2 or lower + changes
>> without bug ID) will be handled case by case by change owner + release
>> (Antti will host discussion via email).
>> For you who didn't know: Antti started 1.11.2013 in release team in
>>Oulu. A
>> lot of work and challenging tasks for him right from the start are the
>> way to learn. Whole release team will support Antti with all this!
>First of all thanks to Antti for taking this on. However, is it wise to
>have a 
>single person be responsible for this? The issue is that we are still
>with a CI system that see's issues with tests meaning that some changes
>several attempts to get through the CI even if the change is good.
>Right now there are no changes either staged or integrating which is
>the precious little time we have before the RC is tagged.
>I would therefore like to request that we have more than one person able
>stage changes to help cover times when Antti is not available.

I believe we¹re already doing this. Antti helps to coordinate and stage
what he can. But other members of the release team and myself can (and
are) also staging during other hours for the stuff that¹s clear.


More information about the Development mailing list