Somehow the discussion that happened here never made it back to the
list, although as best I can tell the list/newsgroup was CC'd.
The outcome of the discussion was as follows:
* After code review, automation will land on Cedar (m-c clone) and Ash
(m-a clone)
* We will verify that the automation works and doesn't break any other
automation.
* Then the automation will land on mozilla-central and mozilla-aurora
with a=NPOTB.
If you have any questions, please let us know.
Sorry that the list got dropped in the discussion, not sure what
happened there.
Clint
On 10/11/2012 5:16 PM, Jonathan Griffin wrote:
Reposting since this didn't make it to the mailing list, only the
newsgroup.
On 10/11/2012 11:46 AM, Clint Talbert wrote:
With the new changes to develop b2g on aurora, how do we want to handle
automation and test changes to the tree? In the past, when we first
brought up mobile automation for the original fennec we had approval
controls but all our automation and test changes did not require
approval; they were either a=TEST_ONLY or a=NPOTB.
Right now we are working hard to bring up automated testing for B2G. We
will be landing this on our Cedar project branch first (which is an m-c
clone). Once it works there, we'll check in the changes to m-c, and then
we'll land them on m-a.
What we'd like to do to speed our development would be to land on m-a
with automatic approval so we don't add to the approval queues and so we
can get the automation stood up sooner rather than later. To ensure we
don't break anything, we will use a second project branch that will be
an Aurora clone and we can use that as a checkpoint before we land
automation on m-a.
Does this process sound OK? It should reduce the load on the approval
queues so those can be focused on changes to shipping code, and we can
get the automation stood up faster.
Thanks,
Clint
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
