Friday, 21 March 2014

Re: ANN: TRAINCON-0 - CITRAIN all stop starting Friday

Hi,

On Fri, Mar 21, 2014 at 3:23 AM, Scott Kitterman <[email protected]> wrote:
> On Thursday, March 20, 2014 18:58:28 Alexander Sack wrote:
>> Hi,
>>
>> I am sending this as a proxy for the not-yet existing TRAINCON bot
>> that will give you updates about our touch image alert state that come
>> with individual landing rules.
>>
>> The TRAINCON levels that were discussed at UDS are:
>>
>> - TRAINCON-2 - everything green, normal landing rules apply
>> - TRAINCON-1 - no promotion for 2 days, restricted landing rules that
>> avoids risks and fastpath regression fixes apply
>> - TRAINCON-0 - no promotion for 5 days, regression fixes only rules apply
>>
>> Since we were not able to promote a touch image since last friday, we
>> want to pursue according to the vUDS scheme above and move on to
>> TRAINCON-0 state for our touch images. To make that happen, I have
>> given the directive to the Landing Team to put the CITrain in "all
>> stop" mode first thing Friday morning in Europe. If you have
>> questions, concerns or want an exception of this "all stop" approach,
>> please contact me (asac) or in case I am not around rickspencer3
>> directly.
>>
>> We also kindly ask our core-devs with direct upload power for their
>> support. Please wait with your uploads that affect touch until we have
>> fully recovered.
>>
>> The bugs that are needed to get fixed are below:
>>
>> * music-app: https://bugs.launchpad.net/music-app/+bug/1292306 (Kevin
>> and Saviq)
>> - Upon upgrading to Qt5.2 the music app no longer plays the next
>> song if the screen is off
>>
>> * alarms:
>> https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295122
>> (Thomas S.)
>> - Alarms not going off reliably on recent touch images
>>
>> * alarms:
>> https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1295237
>> (Thomas S.)
>> - Alarm ringing not going off when clicking dismissed and you have
>> to reboot the phone to stop it.
>>
>> Thanks for everyone helping us in the past week flashing out many bugs
>> related to the qt transition and special helps for those brave heros
>> that currently work hard to get these three blockers sorted.
>
> If you want to make changes in current policy for archive uploads, I think
> that should be coordinated with ubuntu-release. "But it's phone ..." doesn't
> give free reign to bypass the community structure of Ubuntu.

Sorry if you read it like this, but this is no attempt to change
policies for distro at all!

It's merely a measure to gauge the influx of our (Canonical Touch)
engineering teams so we can achieve our continuous quality and
delivery goals. Think of it like a "voluntarily" self imposed higher
quality bar for Touch engineering teams and friends.

As mentioned in the mail, for individual cases where this measure
makes things tricky for the distro stakeholders, we would like to hear
about them so we can see how we can help/fix this.

On qt, we have already admitted that it is not good practice to do it
like we did it this cycle and that we only did it because we were
fully aware that kubuntu was not blocked on it - and we also got
regularly feedback from kubuntu (I was told) while doing this. If not,
then that's what we should do better for sure.

Feel free to also reach out on IRC to me.

- Alexander

--
ubuntu-devel mailing list
[email protected]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel