| 2014-01-09 21:13:09 |
dobey |
description |
This is applicable to the current upstream-merger/daily-release process and the CI Airline changes discussed in the UDS session:
http://summit.ubuntu.com/uds-1311/meeting/22092/core-1311-ci-airline/
To support this, I think we need two interfaces:
1) Given a trunk branch, return a list of all MPs available for merging (i.e. they are approved, meet the reviewer requirements, etc.)
2) Given an MP and a revision ID, merge it (while checking that it still meets the approved to merge criteria)
The idea is that we want to scan a trunk branch for available MPs, select one (perhaps a specific one to do some prioritization), do various CI operations on that branch and then merge it while ensure that the MP being merged hasn't changed. There are also workflows in which we already have the MP in hand and we just want to merge it. |
This is applicable to the current upstream-merger/daily-release process and the CI Airline changes discussed in the UDS session:
http://summit.ubuntu.com/uds-1311/meeting/22092/core-1311-ci-airline/
Given a trunk branch, return a list of all MPs available for merging (i.e. they are approved, meet the reviewer requirements, etc.)
The idea is that we want to scan a trunk branch for available MPs, select one (perhaps a specific one to do some prioritization), do various CI operations on that branch and then merge it while ensure that the MP being merged hasn't changed. There are also workflows in which we already have the MP in hand and we just want to merge it. |
|
