Account confirmers, Anti-spam team, canmove, Confirmed users, Bureaucrats and Sysops emeriti
4,083
edits
SeaMonkey:Release Process: Difference between revisions
m
→Preparing Website Updates
(website: updates RDF file(s)) |
|||
| Line 151: | Line 151: | ||
When the actual release is nearing, updates to the SeaMonkey web pages can be prepared locally (not checked in yet). We currently have a separate, new SeaMonkey website in work, I'll only touch the [http://www.mozilla.org/projects/seamonkey/ www.mozilla.org project site] here for now. The source for those pages is hosted in the mozilla.org www repository on cvs, in the directory <code>mozilla-org/html/projects/seamonkey/</code>. | When the actual release is nearing, updates to the SeaMonkey web pages can be prepared locally (not checked in yet). We currently have a separate, new SeaMonkey website in work, I'll only touch the [http://www.mozilla.org/projects/seamonkey/ www.mozilla.org project site] here for now. The source for those pages is hosted in the mozilla.org www repository on cvs, in the directory <code>mozilla-org/html/projects/seamonkey/</code>. | ||
First, the existing <code>releases/index.html</code> is copied to a version-specific archive file, e.g. <code>releases/1.1.4.html</code> and modified to be just about this version and contain a warning about this version being outdated. Comments excluding files that never have been published for this version can be stripped as well. It's best to look at the older archive files for what needs to be done. | First, the existing <code>releases/index.html</code> is copied to a version-specific archive file, e.g. <code>releases/1.1.4.html</code> and modified to be just about this version and contain a warning about this version being outdated. Comments excluding files that never have been published for this version can be stripped as well. It's best to look at the older archive files for what needs to be done. This new archive page can be checked in ahead of the announcements, it just won't be linked until the <code>releases/index.html</code> update. | ||
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. | ||