Releases/Firefox 6.0/BuildNotes: Difference between revisions

m
Line 423: Line 423:


==== Push the files ====
==== Push the files ====
Used the following script (~ffxbld/push_fennec_release.sh on stage):
<pre>
export VERSION=6.0
export BUILDNUM=1
export RD=/home/ftp/pub/mozilla.org/mobile/releases
export CD=/home/ftp/pub/mozilla.org/mobile/candidates
mkdir $RD/$VERSION
cd $RD/$VERSION
rsync -av --exclude=unsigned --exclude=*.txt --exclude=*crashreporter* \
--exclude=*tests* --exclude=*unaligned* --exclude=*old* --exclude=*install* \
--exclude=*logs* \
$CD/$VERSION-candidates/build$BUILDNUM/ $RD/$VERSION/
for p in linux macosx win32; do
    locales=`cd $CD/$VERSION-candidates/build$BUILDNUM/$p/; ls -1 --hide=en-US`
    for i in $locales; do
        cp -a $CD/$VERSION-candidates/build$BUILDNUM/$p/$i/install/*.xpi \
          $RD/$VERSION/$p/$i
    done
done
# repos
mkdir $RD/$VERSION/repos
rsync -av --exclude=*.install $CD/$VERSION-candidates/repos/ $RD/$VERSION/repos/
# symlink repos
rm -f maemo
ln -s repos maemo
# link fremantle to chinook for multi deb repo
cd $RD/$VERSION/maemo/multi/dists
ln -s fremantle chinook
cd $RD
rm -f latest
ln -s $VERSION latest
</pre>


==== Publish to the Android Market ====
==== Publish to the Android Market ====
* Downloaded http://ftp.mozilla.org/pub/mozilla.org/mobile/candidates/6.0-candidates/build1/android/multi/fennec-6.0.multi.eabi-arm.apk
* Downloaded http://ftp.mozilla.org/pub/mozilla.org/mobile/candidates/6.0-candidates/build1/android/multi/fennec-6.0.multi.eabi-arm.apk
* Uploaded to the Android Market
* Uploaded to the Android Market
 
* Disabled old, enabled new APK
TODO:
* Updated Recent Changes per {{Bug|679173}} - [Mobile] Update Firefox 6 "What's New" copy
* update Recent Changes in the Android Market, see {{Bug|679173}} - [Mobile] Update Firefox 6 "What's New" copy
* Activate new APK, deactivate 5.0 APK


'''IMPORTANT -''' Apparently it is possible for the old apk to "come back from the dead" and on this release it turned out that a second visit to the (insert expletive here) Market was necessary to '''re-activate''' the 6.0b4 apk AGAIN.  So watch your back with anything to do with the Market and check it twice.<br />
'''IMPORTANT -''' Apparently it is possible for the old apk to "come back from the dead" and on this release it turned out that a second visit to the (insert expletive here) Market was necessary to '''re-activate''' the 6.0b4 apk AGAIN.  So watch your back with anything to do with the Market and check it twice.<br />
Confirmed users
3,104

edits