Closed Bug 507168 Opened 15 years ago Closed 15 years ago

move 1.9.1 mobile builds to new 1.9.2 branch

Categories

(Release Engineering :: General, defect)

ARM
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mozilla, Assigned: mozilla)

References

Details

Attachments

(1 file, 1 obsolete file)

once we branch.
Attached patch 1.9.1->1.9.2 (obsolete) — Splinter Review
This shouldn't land before the branch, of course.
Basically just an |s,1.9.1,1.9.2,g| in mobile_config.py
Attachment #391367 - Flags: review?(catlee)
Attachment #391367 - Flags: review?(catlee) → review+
Blocks: 504143
Depends on: 508281
Do we need l10n for this branch?
We're probably going to be releasing GM off 1.9.2 so yeah.
I'll revisit this patch since the p-m split probably changed things.
Took a bit more to add linux-i686 and l10n polling etc.

I was able to get the linux-i686 and maemo nightly + nightly l10n repacks going on staging.  Winmo 1.9.2 nightly had a compilation error but I'm not sure if that's code or configuration.
Attachment #391367 - Attachment is obsolete: true
Attachment #393997 - Flags: review?(bhearsum)
Comment on attachment 393997 [details] [diff] [review]
adding l10n and linux-i686

Coop for the l10n. Either or I suppose.
Attachment #393997 - Flags: review?(ccooper)
Comment on attachment 393997 [details] [diff] [review]
adding l10n and linux-i686

>diff --git a/mozilla2-staging/l10nbuilds2.ini b/mozilla2-staging/l10nbuilds2.ini

>+MOBILE_BRANCHES['mobile-1.9.2']['l10n_tree'] = 'fennec10x_192'
>+MOBILE_BRANCHES['mobile-1.9.2']['l10n_platforms']['linux-gnueabi-arm'] = 'linux'
>+MOBILE_BRANCHES['mobile-1.9.2']['l10n_platforms']['linux-i686'] = 'linux'
>+MOBILE_BRANCHES['mobile-trunk']['allLocalesFile'] = "locales/all-locales"
>+MOBILE_BRANCHES['mobile-trunk']['l10nUploadPath'] = \
>+    '/home/ftp/pub/mozilla.org/firefox/nightly/latest-mobile-trunk-l10n'
>+MOBILE_BRANCHES['mobile-trunk']['enUS_binaryURL'] = \
>+    config.BRANCHES['mozilla-central']['download_base_url'] + '/nightly/latest-mobile-trunk'
>+MOBILE_BRANCHES['mobile-trunk']['tinderbox_tree'] = 'MozillaTest'
>+MOBILE_BRANCHES['mobile-trunk']['l10n_tinderbox_tree'] = 'MozillaStaging'

These should be mobile-1.9.2, right?


I'll give this a try in staging today along with the other 1.9.2 patch.
oh, yup. thanks for the catch.
Attachment #393997 - Flags: review?(bhearsum) → review+
Comment on attachment 393997 [details] [diff] [review]
adding l10n and linux-i686

This looks fine to me (and has run fine) other than the aforementioned issue. r=me with that fixed
Comment on attachment 393997 [details] [diff] [review]
adding l10n and linux-i686

-en_us_binary = http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mobile-browser/
+en_us_binary = http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mobile-trunk/

Is the change just for consistency? Are we going to cleanup stage/ftp to get rid of the old latest-mobile-browser/ dir (or make it a symlink)?
Attachment #393997 - Flags: review?(ccooper) → review+
Comment on attachment 393997 [details] [diff] [review]
adding l10n and linux-i686

changeset:   1428:427205ebe442
Attachment #393997 - Flags: checked-in+
I've seen builds go by without issue. FIXED.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
(In reply to comment #9)
> (From update of attachment 393997 [details] [diff] [review])
> -en_us_binary =
> http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mobile-browser/
> +en_us_binary =
> http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mobile-trunk/
> 
> Is the change just for consistency? Are we going to cleanup stage/ftp to get
> rid of the old latest-mobile-browser/ dir (or make it a symlink)?

Afaict there is no latest-mobile-browser on stage/ftp, and has been that way for some time.  (mobile-trunk ever since I enabled 1.9.1 builds)

I think these are getting the en_us_binary from the mobile_config setting rather than the l10n ini, so yes, consistency, and yes we should probably look into whether removing this line breaks anything, but I don't really sense any urgency on that front.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: