Open Bug 1827849 Opened 1 year ago Updated 10 months ago

deb: Ensure RC builds go to the beta population

Categories

(Release Engineering :: General, task, P3)

Tracking

(Not tracked)

People

(Reporter: jlorenzo, Unassigned)

References

(Blocks 1 open bug)

Details

:atrif mentioned RC builds in this meeting agenda[1]. I realized we haven't thought about RC builds. Firefox RC builds first go to the beta population before they reach the release one. If I'm not mistaken, the current implementation doesn't take that into account. We just ship beta builds to the beta population and RC builds just go to release on the release date.

I believe we should repackage RC builds twice:

  • the first time to brand it firefox-beta and send it to the beta population during the RC week
  • the second time firefox once we feel confident with the current release candidate.

[1] https://docs.google.com/document/d/1k-p0bAgtWv-TH0JDpsfeQFaC8sFvzQjElxCoJapjDVI/edit#

Severity: -- → S4
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.