← Back to team overview

ubuntu-phone team mailing list archive

.click release procedures blocking in-archive development, for 4 weeks and counting. (python2 removal)

 

At the moment phablet-tools upload is stuck in a silo, blocked by our
inability to release no-change uploads of clicks.

On 2014-02-24 revision 205 of calendar-app was merged into trunk, and
not released into the archive.

Fast-forward to today. 201 is still on the images and has known crasher bugs.

I request to release calendar-app click 205 into the store and the
images. I am told that latest trunk of ubuntu-calendar-app (at
revision 212) is still not in a releasable state, has new features,
yet doesn't resolve existing crasher bugs. With .deb / ci-train
things, we can upload no-change rebuilds direct into the archive
without affecting anything, or in ci-train case, the trunks always
match the image hence there is no problem with "broken trunks".
Unfortunately our pre-installed click apps are uploaded into the
store, under a celebrity account which only limited amount of people
have access to (is it 2-3 people? that's not enough to cover
bus/weekend/timezones/holiday/busy factors)

The complete diff that I want to land is this:
http://paste.ubuntu.com/7125514/

The only thing in the actual .click that would change is the version
of the tests shipped "s/201/205". That's exactly equivalent to
"no-change rebuild" for the in-archive .debs. The difference in the
phablet-click-test-setup would be instructed where to fetch fixed up
tests for compatibility with new phablet-test-run.

It is blocking releasing phablet-tools which is ready and gainst
support for executing python3 and python2 tests and unblocks releasing
ported .deb based autopilot tests and essentially removing python2 off
the ubuntu-phablet images... For another 4 weeks and counting.

What procedure can I follow to release v205 .click on to the images as
soon as possible? ( without being blocked on resolving existing and
new crashers, as well as bugs in the never yet released features of
the calendar-app whilst not at all changing the user-experience. )

-- 
Regards,

Dimitri.


Follow ups