Tracking bug for build/release of Fennec 4.0rc1

RESOLVED FIXED

Status

defect
P1
normal
RESOLVED FIXED
8 years ago
6 years ago

People

(Reporter: aki, Assigned: aki)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(10 attachments, 6 obsolete attachments)

2.38 KB, patch
aki
: review+
Details | Diff | Splinter Review
30.24 KB, patch
aki
: review+
Details | Diff | Splinter Review
2.45 KB, patch
nthomas
: review+
Details | Diff | Splinter Review
3.88 KB, patch
Pike
: review+
Details | Diff | Splinter Review
194 bytes, patch
Pike
: review+
Details | Diff | Splinter Review
2.96 KB, patch
Pike
: review+
Details | Diff | Splinter Review
898 bytes, patch
bhearsum
: review+
Details | Diff | Splinter Review
2.09 KB, patch
lsblakk
: review+
Details | Diff | Splinter Review
1.64 KB, patch
armenzg
: review+
lsblakk
: checked-in+
Details | Diff | Splinter Review
1.99 KB, patch
bear
: review+
lsblakk
: checked-in+
Details | Diff | Splinter Review
This is mostly the same as the betas, but has enough different that we need to be careful.
If you run this in mobile/releases/maemo/, the maemo .install files will point to fremantle the way we want.  (Only do this when we actually push live.)

LOCALES=`find . -maxdepth 1 -mindepth 1 -type d`
for locale in $LOCALES; do
   rm $locale/firefox.install
   (cd $locale; ln -s firefox-fremantle.install firefox.install)
   ls -l $locale/firefox.install
done

You can also do this by hand.
We need to edit buildbot-configs/mozilla2/mobile/android/mobile-browser/release/mozconfig to change the channel to 'release'.  If we were to do snippets, the test channel would change from 'beta-cck-test' to 'release-cck-test'.
Some more changes:

1) we probably want to turn doPartnerRepacks on.
2) the milestone probably matters more here than in betas.
3) we need to follow along with the branching mechanics email thread -- we may be building off of a releases/mobile-2.0 and releases/mozilla-2.0 and releases/l10n-mozilla-2.0 .
Depends on: 639980
We will be building off of releases/mobile-2.0 and releases/mozilla-2.1 and releases/l10n-mozilla-2.0.

The mozconfig will be android/mobile-2.0/release/mozconfig (landing that in bug 639980)
Posted patch 4.0rc1 build1 configs (obsolete) — Splinter Review
Attachment #518209 - Flags: review?(aki)
Posted patch 4.0rc1 build1 configs (obsolete) — Splinter Review
Attachment #518209 - Attachment is obsolete: true
Attachment #518209 - Flags: review?(aki)
Attachment #518220 - Flags: feedback?(aki)
Attachment #518211 - Flags: review?(aki) → review+
Comment on attachment 518220 [details] [diff] [review]
4.0rc1 build1 configs

>--- a/mozilla2/mobile_config.py
>+++ b/mozilla2/mobile_config.py
>+### mobile-2.0
>+MOBILE_BRANCHES['mobile-2.0']['main_config'] = config.BRANCHES['mozilla-2.1']

I was worried about this, but it looks like only mobile_master.py needs this, not release_mobile_master.py, so we're good.
However, we may barf on checkconfig unless we create at least an empty dictionary in mozilla2/config.py.

>+MOBILE_BRANCHES['mobile-2.0']['repo_path'] = 'releases/mozilla-2.1'
>+MOBILE_BRANCHES['mobile-2.0']['l10n_repo_path'] = 'l10n-mozilla-2.0'

I believe this is releases/l10n-mozilla-2.0.
http://hg.mozilla.org/releases/l10n-mozilla-2.0

>+MOBILE_BRANCHES['mobile-2.0']['l10n_tree'] = 'fennec_mc'

This would need to change but I think it only matters for nightlies/depend builds.

>+MOBILE_BRANCHES['mobile-2.0']['l10n_tinderbox_tree'] = 'Mozilla-l10n'

This too, maybe.

> # Sometimes we need the application version to be different from what we "call"
> # the build, eg public release candidates for a major release (3.1 RC1).
> # appVersion and oldAppVersion are optional definitions used in places that
> # don't care about what we call it. Eg, when version bumping we will bump to
> # appVersion, not version.
>-version             = '4.0b5'
>+version             = '4.0rc1'
> appVersion          = version

appVersion needs to change to '4.0', so we can release it as 4.0 if it passes qa.

>+milestone           = '2.1b1'

I think the milestone is '2.1'.

I would hazard a guess that releases/mozilla-2.1 default's milestone would change to 2.1.1pre

Other than the appVersion + milestone, I think this looks good :)
I'd feel safer if this were copied to mozilla2-staging, however, and one of us tested it.
Attachment #518220 - Flags: feedback?(aki) → feedback+
Posted patch 4.0rc1 build1 configs (obsolete) — Splinter Review
now includes the other config changes as well as the staging equivalents
Attachment #518220 - Attachment is obsolete: true
Attachment #518577 - Flags: review?(aki)
same as above but with releases/l10n-mozilla-2.0 for the mozilla2/ config
Attachment #518577 - Attachment is obsolete: true
Attachment #518578 - Flags: review?(aki)
Attachment #518577 - Flags: review?(aki)
Comment on attachment 518578 [details] [diff] [review]
4.0rc1 build1 configs

> # Sometimes we need the application version to be different from what we "call"
> # the build, eg public release candidates for a major release (3.1 RC1).
> # appVersion and oldAppVersion are optional definitions used in places that
> # don't care about what we call it. Eg, when version bumping we will bump to
> # appVersion, not version.
>-version             = '4.0b2'
>+version             = '4.0'
> appVersion          = version

version should be 4.0rc1
appVersion should be 4.0

both in mozilla2-staging and mozilla2.

With version set to 4.0, it's uploading to 4.0-candidates:
http://staging-stage.build.mozilla.org/pub/mozilla.org/mobile/candidates/4.0-candidates/
With version set to 4.0rc1, it'll upload to 4.0rc1-candidates (correct) and with appVersion set to 4.0 it'll report as version 4.0 in the browser itself (also correct).

r=me with that changed.  Thanks Lukas!
Attachment #518578 - Flags: review?(aki) → review+
After go to build, we need to sync the mozilla-2.1/mobile-2.0 repositories.
(Not sure about l10n-mozilla-2.0).

See:
https://wiki.mozilla.org/Releases/Firefox_4.0rc1/BuildNotes#Sync_repositories

Also, Stuart asked that we softlink the multi Fremantle deb repo to Chinook
before we push to moff.m.c.
This goes on top of Lukas' already r+'ed configs attachment 518578 [details] [diff] [review].
Attachment #519815 - Flags: review?(nrthomas)
Attachment #519815 - Flags: review?(nrthomas) → review+
Comment on attachment 519817 [details] [diff] [review]
forgot l10n changesets

Pulling again from Fennec4.0b5 milestone seems a bit odd to me, but only adding da to the multilocale limits the risk I guess. r+ if we can get someone from l10n to confirm what's going on, and we're OK to respin if not.
Attachment #519817 - Flags: review?(nrthomas) → review+
Attachment #519817 - Attachment is obsolete: true
Attachment #519852 - Flags: review?(l10n)

Updated

8 years ago
Attachment #519852 - Flags: review?(l10n) → review+
This will need to land in mobile-browser default, mobile-2.0 default, and mobile-2.0 relbranch.
Attachment #519937 - Flags: review?(l10n)
Comment on attachment 519937 [details] [diff] [review]
[checked in] add ja to maemo-locales

Yes, please. r=me.
Attachment #519937 - Flags: review?(l10n) → review+
Comment on attachment 519937 [details] [diff] [review]
[checked in] add ja to maemo-locales

Pushed to trunk, mobile-2.0, and relbranch:

http://hg.mozilla.org/mobile-browser/rev/f8f616b259ff
http://hg.mozilla.org/releases/mobile-2.0/rev/99b9c6f662d6
http://hg.mozilla.org/releases/mobile-2.0/rev/f8f616b259ff
Attachment #519937 - Attachment description: add ja to maemo-locales → [checked in] add ja to maemo-locales
ja is multilocale; nb-NO and nn-NO are removed; the rest of the locales listed in Axel's email have revision changes.
Attachment #519970 - Flags: review?(l10n)
Comment on attachment 519970 [details] [diff] [review]
l10n changesets for build 2

r=me. gladly seeing how resistant this way of doing things is.
Attachment #519970 - Flags: review?(l10n) → review+
Assignee: lsblakk → aki
The missing trailing slash killed the build 1 partner repack:

/scratchbox/moz_scratchbox -p -d /build/mobile-2.0-maemo5-gtk-partner/partner-repacks/scripts "dpkg-deb -b tmp_deb fennec_4.0_armel.deb"
eval eval /builds/scratchbox/sbin/chroot-uid /builds/scratchbox/users/cltbld /scratchbox/tools/bin/env - $SBENV /scratchbox/tools/bin/bash -l /scratchbox/tools/bin/exec.sh /build/mobile-2.0-maemo5-gtk-partner/partner-repacks/scripts dpkg-deb -b tmp_deb fennec_4.0_armel.deb
/scratchbox/tools/bin/exec.sh: line 1: cd: /build/mobile-2.0-maemo5-gtk-partner/partner-repacks/scripts: No such file or directory
dpkg-deb: failed to open package info file `tmp_deb/DEBIAN/control' for reading: No such file or directory
Error: shellCommand had non-zero exit status: 2
command was: /scratchbox/moz_scratchbox -p -d /build/mobile-2.0-maemo5-gtk-partner/partner-repacks/scripts "dpkg-deb -b tmp_deb fennec_4.0_armel.deb"
Attachment #520005 - Flags: review?(bhearsum)
Attachment #520005 - Flags: review?(bhearsum) → review+
Priority: -- → P1
Attachment #519984 - Flags: review?(lsblakk)
Attachment #519986 - Flags: review?(lsblakk)
Attachment #519986 - Attachment is obsolete: true
Attachment #519986 - Flags: review?(lsblakk)
Attachment #520032 - Flags: review?(lsblakk)
Comment on attachment 520032 [details] [diff] [review]
build 2 configs with changesets

do it!
Attachment #520032 - Flags: review?(lsblakk) → review+
Attachment #519984 - Flags: review?(lsblakk) → review+
For Lukas:

I think things are straightforward after this point.

* We need to softlink fremantle to chinook in the multi deb repo, per comment 12.
* There will be a maemo5-gtk partner repack for Ovi in the unsigned/ directory.  This deb file has gone to Stuart in the past, who sends it to Nokia.
* We need to remember to update the .install files when we push live per comment 1.
* Joduinn wants us to handle the push to Android Market (or at least watch Stuart when he does it).  This will be new and needs to be documented.

I'll be in the area and can be reachable via phone/sms/email.
moving to lukas, and adding new  blocker depbug.
Assignee: aki → lsblakk
Depends on: 642755
Attachment #519984 - Attachment is obsolete: true
Attachment #520222 - Flags: review?(armenzg)
Comment on attachment 520222 [details] [diff] [review]
debsign bumps for 4.0rc1 build3

kosher
Attachment #520222 - Flags: review?(armenzg) → review+
Attachment #520229 - Flags: review?(armenzg) → review?(bear)
Comment on attachment 520229 [details] [diff] [review]
4.0rc1 build3 configs

changesets match and build # accurate
Attachment #520229 - Flags: review?(bear) → review+
I've got Tuesday.
Assignee: lsblakk → aki
Blocks: 645283
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.