Release Management/Product details: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎How to update productdetails: improving readability)
(no longer needed)
Line 1: Line 1:
Product details are now automatically managed by ship-it.
Results are published here:
https://product-details.mozilla.org/


=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 Product Details==
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]).
'''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.
'''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|P]]
[[Category: Release Management|P]]

Revision as of 14:44, 17 January 2017

Product details are now automatically managed by ship-it. Results are published here: https://product-details.mozilla.org/

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