← Back to team overview

ubuntu-phone team mailing list archive

Re: Landing process, restoring "trunk" for development

 

On Tue, Apr 8, 2014 at 3:48 PM, Alberto Mardegan
<alberto.mardegan@xxxxxxxxxxxxx> wrote:
> On 04/08/2014 07:30 PM, Alexander Sack wrote:
>> On this topic, we will scheduled a CI call later this week where the
>> next steps from UDS will be one more time revisited and then planned
>> out; jfunk will probably send a summary after the call if you can't
>> attend. Reason why this didn't happen sooner was a series of high
>> priority items worked on by LT and CI Engineering team.
>
> Thanks for picking this up! :-)
>
>>  1. some teams want to try getting better infrastructure support so
>> they can develop on a branch that is not always matching what is in
>> the image
>
> Maybe you could run a small survey (among the team leaders only) to have
> a better understanding of the actual number? If it turns out that nearly
> everyone wants this, it might be simpler to you if there's no way to opt
> out, so you avoid having two different configurations.

As we discussed during that session, this is still a per-team
decision. Mir is already tracking the development and release in two
different branches, but that was a decision that they made and which
is fine.

Only remember that if you want to maintain two different branches,
you'll also need someone kind of dedicated to track the release branch
(releasing trunk, doing cherry-picks, fast-track for quick fixes and
so on).

We can probably try to propose a guideline for this use case, but
nothing is blocking your team to jump on that right now.

Cheers,
-- 
Ricardo Salveti de Araujo


References