We are behind on this body of work. The proposal linked in comment 0 originally had dates that would result in achieving automatic Betas by Dec 3rd. That date is at-risk, largely due to additional resources needed for the Taskcluster migration bug 1591152 I'd still like to target Dec 3rd for most of this work but modify MVP. Essentially still target the automated scheduling, creating, and triggering of a release without human intervention, however, leave the `ship` tasks (in both shipit and balrog) to be done manually. One of the benefits of this is it will allow us to: 1. have more time to internally validate and reduce risk before shipping or making ff user facing changes automatically 2. allow QE to continue running their manual tests before we ship the graphs. Once releng, QE, and relman are confident, we could target full automation, including shipping betas in Dec. I'll update the proposal accordingly.
Bug 1579125 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
We are behind on this body of work. The proposal linked in comment 0 originally had dates that would result in achieving automatic Betas by Dec 2nd. That date is at-risk, largely due to additional resources needed for the Taskcluster migration bug 1591152 I'd still like to target Dec 2nd for most of this work but modify MVP. Essentially still target the automated scheduling, creating, and triggering of a release without human intervention, however, leave the `ship` tasks (in both shipit and balrog) to be done manually. One of the benefits of this is it will allow us to: 1. have more time to internally validate and reduce risk before shipping or making ff user facing changes automatically 2. allow QE to continue running their manual tests before we ship the graphs. Once releng, QE, and relman are confident, we could target full automation, including shipping betas in Dec. I'll update the proposal accordingly.