Closed Bug 454679 Opened 16 years ago Closed 16 years ago

MozillaStageUpload should be able to upload language packs

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: kairo, Assigned: kairo)

Details

Attachments

(1 file)

To be able to use MozillaStageUpload for L10n builds, it should have an option for uploading langpacks. Patch upcoming.
CCing gozer, as in addition to the just-checked-in bug 453135, this is the other part we want to use in L10n builder configs.
This patch adds this option, defaulting it to off so that we don't return with a failure on finding the pattern on non-L10n builders.
Attachment #337972 - Flags: review?
Attachment #337972 - Flags: review? → review?(nthomas)
Comment on attachment 337972 [details] [diff] [review]
add an option for uploading langpacks

>Index: steps/transfer.py
...
>+        @type  uploadLangPacks: bool
>+        @param uploadLangPacks: When True, the MozillaStageUpload will upload
>+                                language pack XPIs to the datedDir/latestDir.
>+                                This option only applies when releaseToDated or
>+                                releaseToLatest is True.

Please add a 'Default: False' at the end of this doc. For kicks, you could put a 'Default=True' on uploadCompleteMar. r+ with that.
Attachment #337972 - Flags: review?(nthomas) → review+
Checked in with both the defaults for uploadCompleteMar and uploadLangPacks noted in the docs, thanks for the fast review!
Status: NEW → RESOLVED
Closed: 16 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.

Attachment

General

Creator:
Created:
Updated:
Size: