Release Management/Product details: Difference between revisions

Jump to navigation Jump to search

Release Management/Product details (view source)

Revision as of 09:14, 27 July 2022

280 bytes added ,  27 July 2022
update some info especially around firefox_versions.json
m (Use a nicer title)
(update some info especially around firefox_versions.json)
Line 9: Line 9:
Historically that data was managed with direct commits into a code repository on svn. The [https://product-details.mozilla.org/1.0/ current version of the API is 1.0] and is meant to be fully compatible with the version we had hosted on svn. If we rewrite the structure of these files in the future, this will be done in version 2.0 and there will be a transition period during which both 1.0 and 2.0 are available.
Historically that data was managed with direct commits into a code repository on svn. The [https://product-details.mozilla.org/1.0/ current version of the API is 1.0] and is meant to be fully compatible with the version we had hosted on svn. If we rewrite the structure of these files in the future, this will be done in version 2.0 and there will be a transition period during which both 1.0 and 2.0 are available.


The mozilla.org development team maintains a copy of the [https://github.com/mozilla/product-details-json product-details files on GitHub ] that is synced with product-details.mozilla.org so as to facilitate deployment and continuous deployment of mozilla.org.
There is a copy of the [https://github.com/mozilla-releng/product-details product-details files on GitHub] which is synced to product-details.mozilla.org.


Since this data is managed via Ship-It, bug reports about the data or requests for additional data should be done on bugzilla in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Release%20Engineering&component=Ship%20It Release Engineering::Ship-It] and not through the Github Repository.
Since this data is managed via Ship-It, bug reports about the data or requests for additional data should be done on bugzilla in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Release%20Engineering&component=Ship%20It Release Engineering::Ship-It] and not through the Github Repository.
Line 16: Line 16:


=== all.json ===
=== all.json ===
This file holds historical information about all Firefox, Firefox for Mobile (aka Fennec), Firefox Dev Edition and Thunderbird releases we shipped in the past.
This file holds historical information about all Firefox, Firefox for Android (aka Fennec and Fenix), Firefox Dev Edition and Thunderbird releases we shipped in the past.
Example:
Example:
<syntaxhighlight lang="JSON">
<syntaxhighlight lang="JSON">
Line 140: Line 140:
<syntaxhighlight lang="JSON">
<syntaxhighlight lang="JSON">
{
{
     "FIREFOX_NIGHTLY":                       "60.0a1",
     "FIREFOX_AURORA": "",
     "FIREFOX_AURORA":                         "",
     "FIREFOX_DEVEDITION": "104.0b2",
     "FIREFOX_ESR":                           "52.6.0esr",
     "FIREFOX_ESR": "91.12.0esr",
     "FIREFOX_ESR_NEXT":                       "",
     "FIREFOX_ESR_NEXT": "102.1.0esr",
     "LATEST_FIREFOX_DEVEL_VERSION":           "59.0b14",
     "FIREFOX_NIGHTLY": "105.0a1",
     "FIREFOX_DEVEDITION":                     "59.0b14",
    "FIREFOX_PINEBUILD": "",
     "LATEST_FIREFOX_OLDER_VERSION":           "3.6.28",
    "LAST_MERGE_DATE": "2022-07-25",
     "LATEST_FIREFOX_RELEASED_DEVEL_VERSION": "59.0b14",
    "LAST_RELEASE_DATE": "2022-07-26",
     "LATEST_FIREFOX_VERSION":                 "58.0.2",
    "LAST_SOFTFREEZE_DATE": "2022-07-21",
     "LATEST_FIREFOX_DEVEL_VERSION": "104.0b2",
     "LATEST_FIREFOX_OLDER_VERSION": "3.6.28",
     "LATEST_FIREFOX_RELEASED_DEVEL_VERSION": "104.0b2",
     "LATEST_FIREFOX_VERSION": "103.0",
    "NEXT_MERGE_DATE": "2022-08-22",
    "NEXT_RELEASE_DATE": "2022-08-23",
    "NEXT_SOFTFREEZE_DATE": "2022-08-18"
}
}
</syntaxhighlight>
</syntaxhighlight>
Line 157: Line 164:
* FIREFOX_ESR_NEXT is usually empty except for a couple of months a year when we have two ESR overlapping and we need to provide both on mozilla.org for download.
* FIREFOX_ESR_NEXT is usually empty except for a couple of months a year when we have two ESR overlapping and we need to provide both on mozilla.org for download.
* LATEST_FIREFOX_DEVEL_VERSION is the latest Firefox Beta built, not necessarily exposed for downloading
* LATEST_FIREFOX_DEVEL_VERSION is the latest Firefox Beta built, not necessarily exposed for downloading
* FIREFOX_DEVEDITION is Firefox Developer Edition (Beta 1 to 4 in the release cycle)
* FIREFOX_DEVEDITION is Firefox Developer Edition
* LATEST_FIREFOX_OLDER_VERSION is unused today, it is the last version we shipped before we moved to the Rapid Release cycle
* LATEST_FIREFOX_OLDER_VERSION is unused today, it is the last version we shipped before we moved to the Rapid Release cycle
* LATEST_FIREFOX_RELEASED_DEVEL_VERSION is the validated latest Firefox Beta built, exposed for downloading
* LATEST_FIREFOX_RELEASED_DEVEL_VERSION is the validated latest Firefox Beta built, exposed for downloading
* LATEST_FIREFOX_VERSION is the Firefox Version we ship on the release channel
* LATEST_FIREFOX_VERSION is the Firefox Version we ship on the release channel
* NEXT_MERGE_DATE is the date of the next scheduled merge of mozilla-central to mozilla-beta
* NEXT_RELEASE_DATE is the date of the next scheduled major Firefox release
* NEXT_SOFTFREEZE_DATE is the date of the next soft code freeze on mozilla-central, ahead of the merge to mozilla-beta


=== l10n/ ===
=== l10n/ ===
Retrieved from "https://wiki.allizom.org/Special:MobileDiff/1243473"

Navigation menu