|
|
| Line 46: |
Line 46: |
| ==Release== | | ==Release== |
| * Same step as Beta | | * Same step as Beta |
| * Once the notes have been signed off and the release is live, ''is_public'' has to be turn on. | | * Once the notes have been signed off and the release is live, ''is_public'' has to be turned on. |
|
| |
|
| =Product Details=
| |
| * These live in [http://viewvc.svn.mozilla.org/vc/libs/product-details/ svn]
| |
| * (Add a link to how to get access)
| |
|
| |
|
| ==How to update productdetails==
| | [[Category:Release_Management|R]] |
| Product details should be updated for Beta and Release after QE signs off on that push. For example, QE will email release-drivers mailing list with the subject line, "[Desktop] Firefox 37.0b3 updates on beta channel signed off by QE". This means 37.0b3 is already live on the beta channel and QE has tested that the updates work.
| |
| | |
| Note: Currently we can't update product details for RC builds. (See [https://bugzilla.mozilla.org/show_bug.cgi?id=1192197 Bug 1192197]).
| |
| | |
| Updating for aurora:
| |
| follow the steps below, but modifying FIREFOX_AURORA.php and mobile_alpha_version.php, for example from 38.0a2 to 39.0a2. History does not need to be updated.
| |
| | |
| Updating for esr:
| |
| modify FIREFOX_ESR.php (and potentially FIREFOX_ESR_NEXT), then modify history/firefoxHistory.class.php to add the esr number to the section listing security and stability releases.
| |
| | |
| | |
| Note that in the history classes, there's a stability release section for .1s (and esrs) and a release section for .0s.
| |
| | |
| | |
| <pre>
| |
| Need to checkout libs/product-details:
| |
| svn co svn+ssh://'youremail'@svn.mozilla.org/libs/product-details product-details
| |
| ### in product-details
| |
|
| |
| % ls
| |
| README json regionDetails.class.php
| |
| export_json.php localeDetails.class.php regions
| |
| firefoxDetails.class.php mobileDetails.class.php thunderbirdBuildDetails.php
| |
| firefoxDetails.class.php~ mobileDetails.class.php~ thunderbirdDetails.class.php
| |
| history productDetails.class.php
| |
| | |
| % vim LATEST_FIREFOX_DEVEL_VERSION.php
| |
| # update to most recent version
| |
| - const LATEST_FIREFOX_DEVEL_VERSION = '33.0b4';
| |
| + const LATEST_FIREFOX_DEVEL_VERSION = '33.0b5';
| |
| | |
| % vim LATEST_FIREFOX_RELEASED_DEVEL_VERSION.php
| |
| # update to most recent version
| |
| - const LATEST_FIREFOX_RELEASED_DEVEL_VERSION = '33.0b4';
| |
| + const LATEST_FIREFOX_RELEASED_DEVEL_VERSION = '33.0b5';
| |
| | |
| % vim mobile_beta_version.php
| |
| # bump the const
| |
| -const beta_version_ = '33.0b2';
| |
| +const beta_version_ = '33.0b4';
| |
| | |
| % vim history/firefoxHistory.class.php
| |
| # add the newest version
| |
| '11.0b3' => '2012-02-17',
| |
| + '11.0b4' => '2012-02-24',
| |
| | |
| % vim history/mobileHistory.class.php
| |
| # add the newest version
| |
| '11.0b3' => '2012-02-17',
| |
| + '11.0b4' => '2012-02-24',
| |
| | |
| % svn status
| |
| M history/mobileHistory.class.php
| |
| M history/firefoxHistory.class.php
| |
| M firefoxDetails.class.php
| |
| M mobileDetails.class.php
| |
| | |
| % ./export_json.php
| |
| % svn status
| |
| M history/mobileHistory.class.php
| |
| M history/firefoxHistory.class.php
| |
| M firefoxDetails.class.php
| |
| M mobileDetails.class.php
| |
| M json/firefox_primary_builds.json
| |
| M json/firefox_history_development_releases.json
| |
| M json/mobile_details.json
| |
| M json/mobile_history_development_releases.json
| |
| M json/firefox_versions.json
| |
| M json/firefox_beta_builds.json
| |
| | |
| % svn ci -m "11.0b4 released"
| |
| Sending firefoxDetails.class.php
| |
| Sending history/firefoxHistory.class.php
| |
| Sending history/mobileHistory.class.php
| |
| Sending json/firefox_beta_builds.json
| |
| Sending json/firefox_history_development_releases.json
| |
| Sending json/firefox_primary_builds.json
| |
| Sending json/firefox_versions.json
| |
| Sending json/mobile_details.json
| |
| Sending json/mobile_history_development_releases.json
| |
| Sending mobileDetails.class.php
| |
| Transmitting file data ..........
| |
| Committed revision 102190.
| |
| # grab this commit rev
| |
| | |
| | |
| | |
| ==Edit properties on mozilla.com==
| |
| ### Now edit the mozilla.com repo
| |
| ### you will need to go up a directory and checkout mozilla.com
| |
| ### svn co svn+ssh://'youremail'@svn.mozilla.org/projects/mozilla.com mozilla.com
| |
| ### you can make sure you have the current commit number that has your changes, by checking on http://svn.mozilla.org/libs/product-details/
| |
| | |
| % svn propedit svn:externals tags/stage/includes
| |
| # paste in the new commit rev from the libs/product-details push & save
| |
| Set new value for property 'svn:externals' on 'tags/stage/includes'
| |
| | |
| % svn propedit svn:externals tags/production/includes
| |
| # paste in the new commit rev from the libs/product-details push & save
| |
| Set new value for property 'svn:externals' on 'tags/production/includes'
| |
| | |
| # probably want to update before trying to commit these
| |
| % svn up
| |
| | |
| % svn diff
| |
| | |
| Property changes on: tags/stage/includes
| |
| ___________________________________________________________________
| |
| Modified: svn:externals
| |
| - product-details -r101880 http://svn.mozilla.org/libs/product-details
| |
| certs http://svn.mozilla.org/libs/certs
| |
| + product-details -r102190 http://svn.mozilla.org/libs/product-details
| |
| certs http://svn.mozilla.org/libs/certs
| |
| | |
| | |
| Property changes on: tags/production/includes
| |
| ___________________________________________________________________
| |
| Modified: svn:externals
| |
| - product-details -r101880 http://svn.mozilla.org/libs/product-details
| |
| certs http://svn.mozilla.org/libs/certs
| |
| + product-details -r102190 http://svn.mozilla.org/libs/product-details
| |
| certs http://svn.mozilla.org/libs/certs
| |
| | |
| | |
| % svn ci -m "11.0b4 released"
| |
| Sending tags/production/includes
| |
| Sending tags/stage/includes
| |
| Committed revision 102191.
| |
| | |
| | |
| # Mozilla.org updates the product details every 5 (or so) minutes
| |
| </pre>
| |
| | |
| =Updating Web Buttons=
| |
| Now that the product-details and mozilla.com externals have been updated, you want the buttons on pages like:
| |
| | |
| * Release: https://www.mozilla.org/firefox/new/
| |
| * Beta: http://www.mozilla.org/firefox/channel/#beta
| |
| * Aurora: https://www.mozilla.org/firefox/channel/#aurora
| |
| * ESR: https://www.mozilla.org/firefox/organizations/all/
| |
| | |
| To have the correct binary download links.
| |
| | |
| | |
| After you update product details, within 30 minutes, the web pages will be refreshed with the current information.
| |
| | |
| =Troubleshooting=
| |
| * If you get an error like "svn: Entry '/Users/synergy/Dropbox/Mozilla/relman/mozilla-europe.org/trunk/sv-SE' has unexpectedly changed special status" when trying to commit, do a revert `svn revert -R .` then `svn up` and try again, if that still fails - re-pull the repo.
| |
| * If you can't get to bedrock and the big red button, check that:
| |
| ** you are on the VPN
| |
| ** you don't have https everywhere installed, and are connecting through http
| |
| | |
| If all else fails ask on #MOC or #www
| |
| | |
| [[category:Release_Management|R]]
| |
Release Notes
What's the purpose of release notes?
Release notes are a central source of information about changes in each Firefox release. They're mainly aimed at advanced and technical users of Firefox who want to be informed about the changes in Firefox's latest updates. They may be web developers, IT managers who deploy Firefox for their users, or people who need to know all the details of the browser they use to accomplish their work. Technical journalists also follow our release notes in order to write stories on changes in Firefox.
How you can help with release notes
- 1. Nominate fixes and features!
Anyone can go to a bug in bugzilla.mozilla.org, and nominate fixes or changes for release notes. Open the "Tracking Flags" menu on the right side of the page. Then please set the relnote-firefox: flag to "?". Release management checks this flag regularly.
A form will pop up in the Bugzilla comments box, asking for your suggested wording for the note and an optional url to link to further documentation.
- 2. Explain the fix
If your fix or other project should be in release notes, tell us what it did, what it means, and what the users and tech press should know. Ideally, we link from each note to an MDN page, a blog post hosted somewhere on mozilla.org, or even a wiki page for users to understand changes, fixes, and new features. Details are very useful here.
What release managers do for relnotes
Release management may skim through the entire list of fixed bugs for a release to find possible release notes. That's often around 4000 bugs!
We also ask engineering managers and developer teams to tell us what note-worthy fixes are upcoming for aurora, beta, and release channels. We check other sources like hacks.mozilla.org to find notable new work. In every release cycle, relman asks people on several engineering mailing lists to read release note drafts, review them, and suggest changes.
The release notes are written and managed in the Nucleus interface available on https://nucleus.mozilla.org/.
Notable fixes and new features in more detail for developers can be found at https://developer.mozilla.org/en-US/Firefox/Releases
Aurora and Beta Cycles
For the first aurora release, from the nucleus interface:
- Create a new aurora release
- Copy the requirements and description from the previous aurora release
- Make sure that is_public is disabled
- Ask for review to the various relevant teams (the list is available in the Release Team Calendar)
- Enable is_public on the aurora release day
For the first beta release, from the nucleus interface:
- Copy the aurora release (is_public is going to be disabled)
- Update the title
- Update the date
- Update the description text (since aurora Text links to information about what Developer Edition is)
- Ask for review (cf aurora)
- Enable is_public on the beta release day
During the aurora/beta cycle:
- Scan the relnote-firefox "?" flags
- Try to find some important unresolved bugs
- Check if some features have not been disabled
Release
- Same step as Beta
- Once the notes have been signed off and the release is live, is_public has to be turned on.