Confirm
2,959
edits
Changes
→Regression Window Process
* http://hg.mozilla.org/releases/mozilla-aurora/pushloghtml?fromchange=71a8786c3815&tochange=e8f6bdf8db3d
Where c0f85061c7d3 & 71a8786c3815 are examples of the last working changesets in gecko and cd3e9359fd64 & e8f6bdf8db3d are examples of the first broken changeset in gecko. Next, open the link and check you will want to figure out if the regressing changeset you can take advantage of b2g-inbound tinderbox engineering builds to do an even deeper bisection. To determine this, you need to be in one of two situations: * The bug was from determined to be a Gaia regression* The hg link reveals that there are b2g-inbound merge. changesets in the bugs in the push log If it waseither of these situations apply, then you'll want to bisect even further using b2g-inbound tinderbox builds to find the exact regressing changeseta regression window.
At this point, you'll have all of the data you need to present a regression window on a bug. Here's an example of a presentation of a Gecko regression window:
