Bug 41669: Rebase base-browser stable to 102.9.0esr
Merge Info
Related Issues
Backport Timeline
-
Immediate - patchsets for critical bug fixes or other major blocker (e.g. fixes for a 0-day exploit) OR patchsets with trivial changes which do not need testing (e.g. fixes for typos or fixes easily verified in a local developer build) -
Next Minor Stable Release - patchset that needs to be verified in nightly before backport -
Eventually - patchset that needs to be verified in alpha before backport -
No Backport - patchset for the next major stable
Upstream Merging
-
Merge to base-browser- typically for!fixupsto patches in thebase-browserbranch, though sometimes new patches as well-
NOTE: if your changeset includes patches to both
base-browserandtor-browserplease please make separate merge requests for each part
-
NOTE: if your changeset includes patches to both
Issue Tracking
-
Link resolved issues with appropriate Release Prep issue for changelog generation
Change Description
Following the new rebase template we'll keep the previous round of fixups! as separate commits to ease any needed bisection this month, and they'll be squashed/fixup'd appropriately for 102.10esr. Range-diff is perfectly clean ( git range-diff FIREFOX_102_8_0esr_BUILD1..origin-push/base-browser-102.8.0esr-12.0-1 FIREFOX_102_9_0esr_BUILD1..richard/bug_41669-base-browser