Please file bugs for any critical regressions that you find in Bugzilla and make sure to set the need-info? flag on release-mgmt at in order to alert the release management team to the issues.
Our request is not for full qualification of the builds but rather exploratory testing of internal websites and applications for which our QA team does not have access. Approval is required, so add "a=, we'd like your help in smoke testing the latest pre-release builds.Additionally, engineers shouldn't have to know what version of the ESR we're on.ģ) Once the mozilla-beta version matches the tracking-firefox-esr78/78 version(s), Security and Release Management teams will triage those bugs and make sure affected/checkin-pending fixes are landed at least 1 week prior to release so that we can go-to-build. Why are we using mainline versions to track the ESR? According to the ESR proposal, a chemspill uses a minor version number, thus throwing off our tracking flags.In the case of an ESR-specific regression, we'll track for the next ESR release.
Set approval-mozilla-esr78 (and if we're in the middle of support 2 versions, then also approval-mozilla-esr78) to ? and status-firefox-esr78/78 to checkin-pending if a patch is ready to land on mozilla-esr78/78Ģ) Members of both Security and Release Management teams will triage tracking-firefox-esr78/78=?, and if agreement is that it's needed for the ESR, the tracking flag will be set to the first version of mainline Firefox that the patch is present in and the approval-mozilla-esr78/78 flag will be set to +.
Set status-firefox-esr78 (and if we're in the middle of supporting 2 versions, then also status-firefox-esr78) to affected if an ESR patch is still being worked on.Set tracking-firefox-esr78 (and if we're in the middle of supporting 2 versions, then also tracking-firefox-esr78) to ?.Status-esr78: ?, unaffected, wontfix, affected, checkin-pending, fixed, verified The processġ) When an engineer believes that a stability bug needs to be addressed for the ESR, or a security fix that's landed on a branch affects the ESR: Status-esr78: ?, unaffected, wontfix, affected, checkin-pending, fixed, verified As the versions progress we should limit this to the most critical security fixes.Įxception: If patches only make changes to tests, test harnesses or anything else that does not affect the shipped builds, they may land with self approval (use a=testonly, a=npotb etc). In the first few cycles of ESR we may be more flexible on these criteria. Security and some major stability fixes when they're landed/merged onto mozilla-beta, or fixes for regressions specific to the ESR. What should land on mozilla-esr78/mozilla-esr78 The ESR78 repo: The ESR78 repo: More info about the ESR 7.5.2 Request to push release to esr channel.3 What should land on mozilla-esr78/mozilla-esr78.