Release Management/Release Notes Process

This is a proposal for the process by which we construct release notes, but does not represent a final decision.

Release/Channel Specific Notes

Can be displayed above "What's New" - please get in contact with Alex to change these.

What's New Section Candidates

(channel) notes for Firefox (n) should be pulled from

• bugs keyworded with "relnote"

OR

• Features/Release_Tracking

OR

• https://developer.mozilla.org/en/Firefox_N_for_developers

OR

• An email to Alex

OR

• has patch with approval-mozilla-(channel) added since the last merge date
• status-firefox(n) is "fixed"

Known Issues Section Candidates

Let's say we're about to push Firefox (n) to Aurora. To find known issues, we should look at all bugs that are

• status-firefox(n) is "affected" or "wontfix"
• tracking-firefox(n) is "?" or "+", or tracking-firefox(n+1) is "?" or "+"

https://bugzilla.mozilla.org/buglist.cgi?type0-1-0=equals&list_id=1664152&field0-1-0=cf_tracking_firefox10&type0-1-2=equals&field0-0-0=cf_status_firefox10&type0-1-3=equals&type0-0-1=equals&field0-0-1=cf_status_firefox10&type0-1-1=equals&value0-1-3=%2B&resolution=---&field0-1-2=cf_tracking_firefox11&query_format=advanced&value0-1-0=%3F&value0-1-2=%3F&field0-1-1=cf_tracking_firefox10&value0-1-1=%2B&value0-0-1=wontfix&type0-0-0=equals&value0-0-0=affected&field0-1-3=cf_tracking_firefox11

OR

( affected || tracking=+ || tracking=? ) and (Keywords = qawanted || Keywords = top crash || keywords = relnote || votes >3 ) and !fixed and !unaffected

https://bugzilla.mozilla.org/buglist.cgi?field0-3-0=cf_status_firefox10&type0-1-0=substring&list_id=1664132&field0-1-0=keywords&type0-1-2=substring&field0-0-0=cf_status_firefox10&type0-1-3=greaterthan&type0-0-1=equals&columnlist=bug_severity%2Cpriority%2Cop_sys%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Ccf_tracking_firefox10%2Ccf_status_firefox10%2Cchangeddate&field0-0-1=cf_tracking_firefox10&type0-1-1=substring&value0-1-3=3&resolution=---&resolution=DUPLICATE&value0-0-2=%3F&value0-3-0=unaffected&field0-1-2=keywords&query_format=advanced&type0-0-3=equals&field0-0-3=cf_status_firefox10&value0-0-3=wontfix&value0-2-0=fixed&value0-1-0=qawanted&value0-1-2=relnote&type0-3-0=notequals&field0-1-1=keywords&value0-1-1=topcrash&field0-2-0=cf_status_firefox10&field0-0-2=cf_tracking_firefox10&value0-0-1=%2B&type0-0-0=equals&value0-0-0=affected&field0-1-3=votes&type0-2-0=notequals&type0-0-2=equals

OR

• status-firefox(n) is "affected" or "wontfix", or tracking-firefox(n) is "?" or "+"
• keyworded with "relnote" (perhaps this should be an approval flag)

If a bug is keyworded/flagged with "relnote", the requestor can additionally specify whether or not additional testing is required, and if so, where bugs should be filed.

Updating Release Notes

All "Known Issues" (bugs) that do not have a fix date in the DB should be checked to see if they've subsequently been resolved in a newer Firefox version. This needs to happen on a weekly basis, since that's the cadence for Aurora/Beta.