Release Management/Release Notes Process: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Redirected page to Release Management/Release Notes)
 
(10 intermediate revisions by one other user not shown)
Line 1: Line 1:
This is a proposal for the process by which we construct release notes, but does not represent a final decision.
#REDIRECT [[Release_Management/Release_Notes]]
 
=== Release/Channel Specific Notes ===
Linked to "What's new" which appears on every channel's download page .
<br>Eg : Check http://www.mozilla.org/en-US/firefox/new/ for latest Release and click on "What's new" below the green Firefox Download button to go to release notes
 
=== What's New Section Candidates ===
(channel) notes for Firefox(version) Desktop or Mobile should be pulled from :
* For features or known issues to be considered for release noting, set relnote-firefox: ?
* We go through these release note nominations in a feature review meeting with various stake holders from product,project,marketing and other drivers where If we agree, we'll either set the flag to relnote-firefox:{version}+ for the first version of Firefox the feature will be present in, or just relnote-firefox:+ for known issues that will be noted until resolution
* If we do not intend to release note something in any way, drivers will set relnote-firefox:-
 
Note : Please make sure to only nominate those features and issues that are significant . [http://www.mozilla.org/en-US/firefox/21.0/releasenotes/ Sample] notes.
 
=== 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)
 
https://bugzilla.mozilla.org/buglist.cgi?type0-0-4=equals&type0-1-0=substring&list_id=1664261&field0-1-0=keywords&field0-0-0=cf_tracking_firefox10&type0-0-1=equals&field0-0-1=cf_tracking_firefox10&resolution=---&resolution=DUPLICATE&field0-0-4=target_milestone&value0-0-2=affected&query_format=advanced&type0-0-3=equals&field0-0-3=cf_status_firefox10&value0-0-3=wontfix&value0-1-0=relnote&value0-0-4=mozilla10&field0-0-2=cf_status_firefox10&value0-0-1=%2B&type0-0-0=equals&value0-0-0=%3F&type0-0-2=equals
 
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.

Latest revision as of 15:00, 30 August 2022

Redirect to:

Retrieved from "https://wiki.mozilla.org/index.php?title=Release_Management/Release_Notes_Process&oldid=1243800"