Closed Bug 1036104 Opened 11 years ago Closed 11 years ago

Partner repack changes for web.de, gmx, mail.com and 1&1 (Firefox 31)

Categories

(Release Engineering :: Release Requests, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mkaply, Unassigned)

Details

Attachments

(5 files)

Patch coming in a few minutes. Sorry for the lateness on this. Our build just got approved by QA.
We have switched to using a chrome JAR file and unpacking our extensions, primarily because we need to be able to use the searchplugins directory properly. So I'll be removing a lot of files and checking in a chrome.jar. I already checked and other extensions like yandex use a JAR file, so this doesn't seem to be an issue. I'll be attaching separate diffs for the actual toolbar. This diff will be a diff of our entire source tree (which is used as the basis for all three toolbars), so it should be much easier to review. Please let me know if you see any issues with this.
Question: Is it possible to use the try server to do a partner repack builds?
Attached file Overview of changes
Attached file Patches by commit
This contains each individual patch as a commit.
Attached patch Complete diffSplinter Review
This contains the complete diff. Most of these changes are cosmetic including: Changing lets to var and for each to forEach (for better Chrome merging). Changing debug to ddebug. Removal of coupon extension.
Attachment #8452858 - Flags: review?(mconnor)
Huge diff because it's mostly removed files.
Attached patch 1und1 changesSplinter Review
We are also officially adding a 1und1 browser toolbar with this release. Here is the diff for that. The source code comes from the same tree as the overall diff.
Is there any chance this can get reviewed? We're just about out of runway for Firefox 31. Again, my apologies for the delay.
Comment on attachment 8452858 [details] [diff] [review] Complete diff This looks okay, but I really don't understand why all of the let usage was changed to var... over-eager mechanical changes?
Attachment #8452858 - Flags: review?(mconnor) → review+
(In reply to Mike Connor [:mconnor] from comment #9) > Comment on attachment 8452858 [details] [diff] [review] > Complete diff > > This looks okay, but I really don't understand why all of the let usage was > changed to var... over-eager mechanical changes? We share our code between Chrome and Safari, so we wanted it to be able to be merged. Same with the for each code.
Builds from build2 should have these changes, according to tags.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Component: Custom Release Requests → Release Requests
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: