Move the chrome.automation API to dev channel.

Move the chrome.automation API to dev channel.

BUG=309681, 414153
TEST=AutomationApiTest.*.

Committed: https://crrev.com/87c58249f011d9d18a04cc135ba4bc7c460405ac
Cr-Commit-Position: refs/heads/master@{#294982}

[David Tseng, 2014-09-10 21:50:22]

dtseng@chromium.org changed reviewers:
+ miket@chromium.org

[David Tseng, 2014-09-10 21:51:47]

@miket, please advise as to other steps needed to make this change. API has been
stable for some time and no blocking workitems.

[miket_OOO, 2014-09-12 19:15:08]

On 2014/09/10 21:51:47, David Tseng wrote:
> @miket, please advise as to other steps needed to make this change. API has
been
> stable for some time and no blocking workitems.

If there's a launch bug, please update the CL description to include it. If
there isn't, should there be one?

[David Tseng, 2014-09-15 04:00:19]

On 2014/09/12 19:15:08, miket wrote:
> On 2014/09/10 21:51:47, David Tseng wrote:
> > @miket, please advise as to other steps needed to make this change. API has
> been
> > stable for some time and no blocking workitems.
> 
> If there's a launch bug, please update the CL description to include it. If
> there isn't, should there be one?

I went ahead and created a bug to track the launch to dev.

[miket_OOO, 2014-09-15 18:21:49]

On 2014/09/15 04:00:19, David Tseng wrote:
> On 2014/09/12 19:15:08, miket wrote:
> > On 2014/09/10 21:51:47, David Tseng wrote:
> > > @miket, please advise as to other steps needed to make this change. API
has
> > been
> > > stable for some time and no blocking workitems.
> > 
> > If there's a launch bug, please update the CL description to include it. If
> > there isn't, should there be one?
> 
> I went ahead and created a bug to track the launch to dev.

That bug is missing the usual launch flags. I'm not sure how they are normally
created -- perhaps a PM would know. Meanwhile, this is a good enough skeleton to
track. LGTM.

[David Tseng, 2014-09-15 18:31:55]

The CQ bit was checked by dtseng@chromium.org

[commit-bot: I haz the power, 2014-09-15 19:16:46]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patchset/561933002/1

[commit-bot: I haz the power, 2014-09-15 20:26:23]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-09-15 20:26:24]

Try jobs failed on following builders:
  mac_chromium_rel_swarming on tryserver.chromium.mac
(http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[David Tseng, 2014-09-15 23:32:16]

The CQ bit was checked by dtseng@chromium.org

[commit-bot: I haz the power, 2014-09-16 00:01:06]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patchset/561933002/1

[commit-bot: I haz the power, 2014-09-16 02:23:44]

Committed patchset #1 (id:1) as e3cf0b45f05e08c1e9e87e00975957c624052d56

[commit-bot: I haz the power, 2014-09-16 02:27:00]

Patchset 1 (id:??) landed as
https://crrev.com/87c58249f011d9d18a04cc135ba4bc7c460405ac
Cr-Commit-Position: refs/heads/master@{#294982}