ubuntu-phone team mailing list archive

[Didier Roche <didrocks@xxxxxxxxxx>]

Le 10/04/2014 00:24, Selene Scriven a écrit :
> * Didier Roche <didier.roche@xxxxxxxxxxxxx> wrote:
> > CI Train spreadsheet [1] now support that workflow:
> > * you will notice a new column next to "ready" (on the left
> > before the last visible one) entitled "QA sign off needed".
> > -> set it to No (default) if your landing falling into case 1.
> > -> set it to Yes for landing falling into cases 2. and 3.
> > ...
> > [1] https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFlCc1VzeVZzWmdBZS11WERjdVc3dmc&usp=drive_web#gid=0
> Makes sense, mostly.  However, QA is going to need write access
> in order to sign off on anything.

Yeah, I was waiting on the names to come on to know who to give write 
access to :)

> Also, I've noticed that the read-only status interferes with
> being able to read the entire contents of a cell when it scrolls
> outside the visible area, but that can be worked around by
> downloading the document and viewing locally.
Interesting that read-only prevents this scrolling. FYI, when things are 
ready for QA to sign off, the status field will have an orange 
background color.
The color code of the status field is:
- aubergine-like: upstream needs to act on the landings (they can 
rebuild, test, or their landing is in transit)
- orange: the landing is ready for QA to test and sign off (for cases 
when they need to)
- yellow: action from the landing team required: landing can be 
published or packaging changes needs to be reviewed
- light green: upstream can merge and clean (last step of the process). 
The landing is now in the release pocket and ready for next image to pick up
- dark green: landed, nothing else to do with that request

I'm opened to change the orange for something that suits QA more :)
Cheers,
Didier