Landing process rules for ubuntu Touch

Registered by Didier Roche on 2014-03-05

This session will be a summary of the current landing process rules we put in place in the past few months. After a short summary, we'll open the floor on how to improve it.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Didier Roche
Direction:
Needs approval
Assignee:
None
Definition:
Discussion
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Things to discuss:
- landing process (through CI Train)
- rules used to assess stopping landing
- how can we communicate it?
- when/how do we take the decision to back out a landing?
- any better way to get a shorter "back to green" roundtrip?
- click packages: how to get a better (timezone wise) and more efficient releasing procedure?
- how to get core-dev landings for Touch component in line with that process.

(?)

Work Items