![]() 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.
0 Comments
Leave a Reply. |