This page describes the process of getting bug fixes into stable and stable-rc grimoires between regular integrations. All of this assumes there's a bug report for it on http://bugs.sourcemage.org. If such a bug report doesn't exist, e.g. because a guru just fixed something in test grimoire without a bug report, a bug should be created for the integration. No integration should happen to stable-rc or stable grimoire between release cycles without going through this process. The only exemption to this rule are updates of the linux spell that contain subpatchlevel changes (eg. 2.6.18.53 to 2.6.18.54) or release candidates for the next kernel release (LATEST_PRE_2_6).
This same process should also be used for security fixes.
- The bug "Version" field should be set to the highest grimoire it applies to, stable being the highest
- When a bug is fixed in test, mark the bug as FIXED. Then the "integrate to $BRANCH grimoire" flags should be set to "?" for the branches the fix should get integrated to.
- Each commit should fix only the bug/security issue and nothing else. Any commit which does more than the bug will be denied until reverted and done correctly.
- One of the gatekeepers (currently Eric Sandall, Seth Woolley, Arwed v. Merkatz (as assistant for Eric Sandall), Jeremy Blosser, George Sherwood (as assistant for Eric Sandall)), and Jaka Kranjc approves or denies the request(s) for integration, with an explanation added at least for the deny case. If the requester for an integration is a gatekeeper himself, a different gatekeeper has to approve the request.
- Once a request for integration is approved (flag set to "+"), it can be integrated to the branch for which it was approved. This integration can be done by anyone with stable/stable-rc grimoire access (which currently includes: Jeremy Blosser, Jaka Kranjc, Arwed von Merkatz, Eric Sandall, George Sherwood, and Seth Woolley).
- Once integrated, post which commit id the integration is and mark the "Integrated" flag to "+".
- Request verification if the bug is more complicated than "update to version X.Y.Z" or "missing dependency on foo" and mark CLOSED once it's VERIFIED and available in the specified tarball version, otherwise mark CLOSED once it's available in the specified tarball version.
Tarball creation guidelines:
Gatekeepers check for integration requests at least once a day.
Integrators check for approved integrations at least once a day.
Tarballs are only regenerated outside the normal 6 hour period (test) for security updates or BLOCKER/CRITICAL bugs. Stable and stable-rc tarballs are always generated manually.
list of must-fix-before-release bugs
list of approved pending integrations
list of requested (not yet approved) integrations
(new) list of fixed-not-closed bugs
(codex only) list of approved pending integrations
Bugzilla now supports shared searches. If you go to your account preferences, you can enable the saved shared searches for the above bug types. That way you'll have quicker access.