many of the tasks required for this bug are tracked here: https://github.com/orgs/mozilla-releng/projects/2?add_cards_query=is%3Aopen

I don't think there is a way to define Github dependencies in Bugzilla.

Official proposal: https://docs.google.com/document/d/12cxKmDcuLmq3HbHkJs_lQcDOYZomUyz5RGlcKG6jlNY/edit#heading=h.34112uadhipp

adding Bug 1501167 - Rerunning a balrog submit results in duplicate partials information and Bug 1537710 - nightlies based on same revision end up adding two entry points for the same file in Balrog blobs as deps since this should be solved for daily betas too

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.

(In reply to Jordan Lund (:jlund) from comment #2)

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.

proposal doc and milestones are updated to reflect the above. adding ritu and stuart to this bug so they can track