Handling off comm-* repository merges

Wayne Mery (Thunderbird QA) vseerror at lehigh.edu
Tue Nov 3 18:34:15 UTC 2015


Patrick, thanks for stepping forward.  We need more people stepping up 
to participate like this. And it will be great to have you in this role.



On 10/29/2015 7:56 AM, Patrick Cloke wrote:
> Mark / Philipp,
>
> I could probably help out with these too. I think I meet all the
> requirements. :)
>
> Unfortunately I'm not available today to help out.
>
> --Patrick
>
> On 10/29/15 4:17 AM, Philipp Kewisch wrote:
>> Hi Mark,
>>
>> sorry for not getting to this earlier. While I am hesitant to take yet
>> another role, I am probably the foremost candidate for this. At least
>> aleth and I have treestatus access, I think it would be good to
>> involve some other folks though in case I am not available during the
>> merge time.
>>
>> Philipp
>>
>>
>> On 10/29/15 8:59 AM, Mark Banner wrote:
>>> The merges have been moved forward to today (see Sylvestre's
>>> dev.planning post).
>>>
>>> I've not had any offers for taking over this yet.
>>>
>>> Mark.
>>>
>>> On 26/10/2015 11:48, Mark Banner wrote:
>>>> Hi folks,
>>>>
>>>> I've currently been doing comm-* repository merges for the last few
>>>> years, and I'd like to hand them off to other people now. Hence, I'm
>>>> looking for volunteers, so you know what you're signing up for,
>>>> here's a few pointers:
>>>>
>>>>   * Merges happen once every six weeks on merge day
>>>>     <https://wiki.mozilla.org/RapidRelease/Calendar>. Generally
>>>>     these happen in the morning pacific time.
>>>>   * We have scripts (and some older documentation) to automatically
>>>>     merge the repositories. Only a quick visual check of the results
>>>>     is required.
>>>>   * Only one person is needed to do the merges on a particular day,
>>>>     but having multiple people who can do it would obviously be
>>>>     better if someone is away.
>>>>   * I think its probably a requirement that you're already familiar
>>>>     with pushing to comm-*, level 3 access is definitely required.
>>>>   * You'll need to have treestatus access to be able to close & open
>>>>     the trees
>>>>   * You probably don't have bandwidth limits on your connection (the
>>>>     current scripts perform fresh clones each time to ensure a clean
>>>>     merge)
>>>>
>>>> I'd like to transition to at least one person starting next week -
>>>> 2nd Nov. I should be around for the December one as well if there's
>>>> any follow-up questions, but generally I'd like to move away from
>>>> doing these now.
>>>>
>>>> If you want to help out with these, please let me know. If there's
>>>> more than one, we'll look at getting a couple of you up to speed,
>>>> and then you can arrange it amongst yourselves.
>>>>
>>>> Mark.
>>>>




More information about the tb-planning mailing list