ubuntu-phone team mailing list archive

[Alexander Sack <asac@xxxxxxxxxxxxx>]

On Tue, Apr 8, 2014 at 2:30 PM, Alberto Mardegan
<alberto.mardegan@xxxxxxxxxxxxx> wrote:
> Hi all!
>   At the USD there was a session about the landing process, and some
> people brought up the point that having the "trunk" branch synchronized
> with the archive was inconvenient for developers:
>
>   https://www.youtube.com/watch?v=Igj-JyUNGPU#t=36m13s
>
> In the last 5 minutes of the session, a solution was proposed: leaving
> "trunk" for development purpose (like it was before the CI train
> started) and push the landed commits into other branches, such as
> "trusty". However no decision was taken, other than continuing the
> discussion on the mailing list. I've been eagerly waiting for it, but
> since almost a month has passed and I haven't seen this discussion being
> brought up, here it is. :-)
>
> I think this would be a very good time to implement this proposal, since
> trusty is going to be released soon, and as soon as the Upstarting
> Unicorn (this would be a wonderful name, admit it) gets open for
> development, it would not be very clear what "trunk" is synched to.
>
> So, what's the deal? :-)

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.

To give everyone a picture what this is about, here a very high level
of what was discussed at UDS:

 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
 2. they would like to call this trunk as they believe they want all
the launchpad bells-and-whistles that come with the "trunk" for their
out-of-image development branch.
 3. they would prefer to get CI MP Bot with automerge feature enabled
for their trunks
 4. In turn they self-impost a release frequency and will explore
options how to keep incentives in teams right to drive for early and
often release mentality.

The initial pilots will be looked at closely and we will assess if
that model is feasible and how to tweak to get to something that works
well; point why we should be careful is that we basically go down the
road to replicate the previous global working model now on a team
level. While this can work, the success of this model will be highly
dependent on the piloting engineering teams figuring out how to
balance the focus of their engineers in a dynamic manner.

Hope this helps. Progress and pilots will be made soon. jfunk or me
will update you as we go.


 - Alexander



>
> Ciao,
>   Alberto
>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to     : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help   : https://help.launchpad.net/ListHelp