When the Firefox 2 help documents were imported, the structure and subject of the content was not changed. It does not showcase new features, that users may need to learn about (because they were not part of the old help documentation).
So what is the primary set of articles needed for Firefox 3.5 Support?
That will be a list of top articles, based on traffic and top search terms.
# Create partial patches and snippets ./patcher2--create-patches --app=firefox \ --config=../config/moz18-branch-major-update-patcher22mkdir -p /builds/verify/firefox-20011-3b2-fake-major/ cd /builds/verify/firefox-20011-3b2-fake-major/ cvs -d [email protected]:/cvsroot co -d updates mozilla/testing/release/updates/ cvs -d [email protected]:/cvsroot co -d common mozilla/testing/release/common/ cd updates ./-c moz18-firefox-$2# ssh [email protected] (prod 1.9 box) mkdir /builds/updates/firefox-20012-3b3-fake-major/ cd /builds/updates/firefox-20012-3b3-fake-major/ cvs -d [email protected]:/cvsroot co -d patcher -r UPDATE_PACKAGING_R1 mozilla/tools/patcher # check out Moz Build cd patcher cvs -d [email protected]:/cvsroot co -d Moz Build -r UPDATE_PACKAGING_R1 mozilla/tools/release/Moz Build cd ..
# config now lives in public repo cvs -d [email protected]:/cvsroot co -d config mozilla/tools/patcher-configs/moz18-branch-major-update-patcher2# apply patch waiting for review cd config curl -s https://bugzilla.mozilla.org/attachment.cgi? cd patcher export [email protected]cvs.mozilla.org:/cvsroot # build tools ./patcher2--build-tools --app=firefox --tools-rev=UPDATE_PACKAGING_R1 \ --config=../config/moz18-branch-major-update-patcher22&1 | tee firefox_# download complete MARs # FIXME - we only really need to "to" mars, not the "from" mars, but there must be "from" # mars present for patcher to build the patchinfo ./patcher2--download --app=firefox \ --config=../config/moz18-branch-major-update-patcher22&1 | tee firefox_# FIXME - patcher needs to see that the MARs that it thinks are partials # are there or else it will not attempt to generate patchinfo cd temp/firefox ln -s 3.0b3 2.0.0.12-3.0b3 cd ../..
# Create partial patches and snippets ./patcher2--create-patches --app=firefox \ --config=../config/moz18-branch-major-update-patcher22mkdir -p /builds/verify/firefox-20012-3b4-fake-major/ cd /builds/verify/firefox-20012-3b4-fake-major/ cvs -d [email protected]:/cvsroot co -d updates mozilla/testing/release/updates/ cvs -d [email protected]:/cvsroot co -d common mozilla/testing/release/common/ # get patch to trawl "Only in" directories cd common # on mac & linux curl -s https://bugzilla.mozilla.org/attachment.cgi?
id=304252 | patch -p0 # on win32 wget --no-check-certificate -O patch https://bugzilla.mozilla.org/attachment.cgi? A few packaging problems were discovered in applying the stock 3.b2 complete mars to en-US 2.0.0.11 installs.To fix this for b3, and the package-static files were adjusted.Now, at home I use the same add-ons and I'd like to prevent losing my tab groups so I'm looking for a way to disable automatic updates (which are enabled) An alternative solution to blocking all updates, is to move to a fork of Firefox which will keep the XUL add-on format, now called "Legacy" by Firefox, while still installing security updates.Two Firefox forks that keep the legacy add-ons are : I have tried Pale Moon, and it very nicely imported all my add-ons and profile data.Most users who don't exit the site after visiting the Product help start page, use the search field, which gives results for the entire Knowledge Base, not just in-product articles.