Thunderbird/Security And Stability Releases/Rules

From MozillaWiki
Jump to navigation Jump to search

The Thunderbird 3.0.x releases are for security and stability updates. Typically these releases are restricted to security and stability fixes. The first few .x releases may include one or two regression fixes if necessary.

General Process for landing bugs on Thunderbird 3.0.x

(This only applies to patches affecting comm-*, mozilla-* patches should follow mozilla-* rules).

  1. Generate a patch for trunk and request reviews as per the standard process.
  2. Once reviews granted, land the patch on comm-central (if you don't have checkin privileges add checkin-needed to the keywords)
    • On checking the patch in the bug should be marked as FIXED, and the milestone field set to the next trunk milestone.
  3. Once the patch has baked for a few days:
    • request approval-thunderbird3.0.1 (by setting the flag to ?)
    • At the same time as requesting approval, explain the risk associated with the patch and why it should be taken for the security and stability branch.
  4. If approval is granted, land on comm-1.9.1 (more info on comm-central branches).
    • Once checked in, set the status-thunderbird3.0 field to '.1', '.2' as appropriate for the release the patch is being checked in for.

Notes:

Status Tracking

These bugzilla queries are used by drivers for tracking the Thunderbird 3.0.x releases.

Triage

Status

Open Blockers Needs Branch Patch Needs Landing Unverified
needed
3.0.2 3.0.2 3.0.2 3.0.2
3.0.1 3.0.1 3.0.1 3.0.1

Wanted/Not-Wanted Bugs

Core Bugs

Fixed and Check-ins

Fixed Check-ins
3.0.1 (just 3.0.1, not 3.0 RCs as well) 3.0.1

Note: check-in lists may contain SeaMonkey and Calendar only patches.

Retrieved from "https://wiki.mozilla.org/index.php?title=Thunderbird/Security_And_Stability_Releases/Rules&oldid=192480"