Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,083
edits
SeaMonkey:Release Process: Difference between revisions
Jump to navigation
Jump to search
website: updates RDF file(s)
(website: updates RDF file(s)) |
|||
| Line 154: | Line 154: | ||
In the <code>releases/index.html</code> itself, a selective search and replace is done to update the old version number with the new one. The language packs are left at the currently mentioned version number if this is a security update during a localization freeze phase, unless a newer language pack is available for that language. The L10n freeze allows us to use a langpack for, say, SeaMonkey 1.1.2 flawlessly with a 1.1.5 release build, people should still be linked to that because of this fact. All (contributed) builds that are now updated to the new release version but are not available yet, get commented out with HTML comments, so it's easy to put them back once they are available. In the "Previously released..." section, the old version needs to be added with a link to its archive HTML page. | In the <code>releases/index.html</code> itself, a selective search and replace is done to update the old version number with the new one. The language packs are left at the currently mentioned version number if this is a security update during a localization freeze phase, unless a newer language pack is available for that language. The L10n freeze allows us to use a langpack for, say, SeaMonkey 1.1.2 flawlessly with a 1.1.5 release build, people should still be linked to that because of this fact. All (contributed) builds that are now updated to the new release version but are not available yet, get commented out with HTML comments, so it's easy to put them back once they are available. In the "Previously released..." section, the old version needs to be added with a link to its archive HTML page. | ||
<code>releases/updates/en-US.rdf</code> (and the files for any localizations that already have binaries) needs to be updated to a fitting update build ID. For SeaMonkey, 1.1.x, this is in the form of e.g. <code>1.8.1.20071008</code> where the first three numbers are from the Gecko version number and the fourth is the release's Gecko date. If not all builds for all platforms have the same Gecko date, use the lowest date of all of them, as our update notification service will just check if the announced number is higher then the running build's version. | |||
Finally, <code>mozilla-org/html/VARIABLES</code> needs to be updated to reflect the new version, as the stuff defined in there is used among others on the SeaMonkey front page and the www.mozilla.org front and downoload pages. Note that checkins to that file are restricted to a small group of people. | Finally, <code>mozilla-org/html/VARIABLES</code> needs to be updated to reflect the new version, as the stuff defined in there is used among others on the SeaMonkey front page and the www.mozilla.org front and downoload pages. Note that checkins to that file are restricted to a small group of people. | ||