f1c2cfb45429b1fe877e7c84bf69aeb4b06c51b7: No bug - Tagging 4c434d19d03d5461e54fa22dfb82eaed4cd6631b with FENNEC_68_0b10_RELEASE a=release CLOSED TREE DONTBUILD
Mozilla Releng Treescript <release+treescript@mozilla.org> - Fri, 14 Jun 2019 14:42:18 +0000 - rev 533892
Push 11455 by ryanvm@gmail.com at Fri, 14 Jun 2019 18:05:46 +0000
No bug - Tagging 4c434d19d03d5461e54fa22dfb82eaed4cd6631b with FENNEC_68_0b10_RELEASE a=release CLOSED TREE DONTBUILD
20a7d69a5950d9c627271caf4399f65597843506: no bug - Bumping Firefox l10n changesets r=release a=l10n-bump DONTBUILD
L10n Bumper Bot <release+l10nbumper@mozilla.com> - Fri, 14 Jun 2019 18:00:21 +0000 - rev 533891
Push 11454 by ffxbld at Fri, 14 Jun 2019 18:00:27 +0000
no bug - Bumping Firefox l10n changesets r=release a=l10n-bump DONTBUILD cs -> 7339bf684137 ro -> e60ddab91ed6
0b8786f5fca31c06b9970f43410623150899b500: no bug - Bumping Fennec l10n changesets r=release a=l10n-bump DONTBUILD
L10n Bumper Bot <release+l10nbumper@mozilla.com> - Fri, 14 Jun 2019 18:00:14 +0000 - rev 533890
Push 11454 by ffxbld at Fri, 14 Jun 2019 18:00:27 +0000
no bug - Bumping Fennec l10n changesets r=release a=l10n-bump DONTBUILD cs -> 7339bf684137 ro -> e60ddab91ed6
ff31e7f583dacd77a1e3106c5ee9361c318b0d08: no bug - Bumping Firefox l10n changesets r=release a=l10n-bump DONTBUILD
L10n Bumper Bot <release+l10nbumper@mozilla.com> - Fri, 14 Jun 2019 17:00:22 +0000 - rev 533889
Push 11453 by ffxbld at Fri, 14 Jun 2019 17:00:30 +0000
no bug - Bumping Firefox l10n changesets r=release a=l10n-bump DONTBUILD cs -> 5ec53a58b642 en-GB -> d6d315a1d178 et -> 79c9d84ece11 pa-IN -> 2eb44fcc299e ro -> babd9e770954
9b37433a054508d16843307ee2b0d901e23720fa: no bug - Bumping Fennec l10n changesets r=release a=l10n-bump DONTBUILD
L10n Bumper Bot <release+l10nbumper@mozilla.com> - Fri, 14 Jun 2019 17:00:16 +0000 - rev 533888
Push 11453 by ffxbld at Fri, 14 Jun 2019 17:00:30 +0000
no bug - Bumping Fennec l10n changesets r=release a=l10n-bump DONTBUILD cs -> 5ec53a58b642 en-GB -> d6d315a1d178 et -> 79c9d84ece11 pa-IN -> 2eb44fcc299e ro -> babd9e770954
4f6a9270754a0ca4e368bb0bf3256c72669fe79c: Bug 1553065 - Move profile-use mozconfig info into common mozconfigs; r=firefox-build-system-reviewers,chmanchester a=RyanVM
Mike Shal <mshal@mozilla.com> - Fri, 31 May 2019 23:56:16 +0000 - rev 533887
Push 11452 by jlorenzo@mozilla.com at Fri, 14 Jun 2019 15:11:56 +0000
Bug 1553065 - Move profile-use mozconfig info into common mozconfigs; r=firefox-build-system-reviewers,chmanchester a=RyanVM The 3-tier PGO builds used a separate mozconfig called 'profile-use' for the final tier. This created a problem when it rode to beta, since the same mozconfig was used for all trees, which meant we ended up with nightly branding on beta builds. With the PGO-enabling logic in common mozconfigs, we can enable it by setting the MOZ_PGO_PROFILE_USE environment variable from the task definition. All of the final-tier PGO builds now use the nightly, beta, etc mozconfigs like before, so branding should be intact. Differential Revision: https://phabricator.services.mozilla.com/D33172
4a7962ae170f16bc2b7b0e50348322ca1f01a7dc: Bug 1553065 - Use MOZ_LTO environment variable in mozconfig.unix; r=firefox-build-system-reviewers,chmanchester a=RyanVM
Mike Shal <mshal@mozilla.com> - Fri, 31 May 2019 23:56:12 +0000 - rev 533886
Push 11452 by jlorenzo@mozilla.com at Fri, 14 Jun 2019 15:11:56 +0000
Bug 1553065 - Use MOZ_LTO environment variable in mozconfig.unix; r=firefox-build-system-reviewers,chmanchester a=RyanVM This makes it consistent with bug 1530908 and 1536194. Differential Revision: https://phabricator.services.mozilla.com/D33171
a8333688fcbe378aad3757fd62673928b1668179: Bug 1553972 - make --with-pgo-profile-path take a directory; r=nalexander a=RyanVM
Nathan Froyd <froydnj@mozilla.com> - Fri, 24 May 2019 01:53:59 +0000 - rev 533885
Push 11452 by jlorenzo@mozilla.com at Fri, 14 Jun 2019 15:11:56 +0000
Bug 1553972 - make --with-pgo-profile-path take a directory; r=nalexander a=RyanVM e10s profiling or IR-based PGO instrumentation will both produce multiple `.profraw` files that need to be handled in some way. Since clang's `-fprofile-generate` option takes a directory, it seems fitting to make `--with-pgo-profile-path` mirror that by taking a directory, and letting `merge_profdata.py` deal with whatever files it might find in said directory. Differential Revision: https://phabricator.services.mozilla.com/D32389
8622e0514d5e93da2912ea78bfd841ebbf3ace45: No bug - Tagging 4c434d19d03d5461e54fa22dfb82eaed4cd6631b with FIREFOX_68_0b10_RELEASE a=release CLOSED TREE DONTBUILD
Mozilla Releng Treescript <release+treescript@mozilla.org> - Fri, 14 Jun 2019 14:48:52 +0000 - rev 533884
Push 11451 by ffxbld at Fri, 14 Jun 2019 14:49:01 +0000
No bug - Tagging 4c434d19d03d5461e54fa22dfb82eaed4cd6631b with FIREFOX_68_0b10_RELEASE a=release CLOSED TREE DONTBUILD
f0a7f5aba2a2935a9e30e654fe17ac559015a6d7: Automatic version bump CLOSED TREE NO BUG a=release DONTBUILD
Mozilla Releng Treescript <release+treescript@mozilla.org> - Fri, 14 Jun 2019 14:45:38 +0000 - rev 533883
Push 11450 by ffxbld at Fri, 14 Jun 2019 14:45:47 +0000
Automatic version bump CLOSED TREE NO BUG a=release DONTBUILD
bb85d635b9ca9fbab2e5fff4d56fde5449eaf682: No bug - Tagging 4c434d19d03d5461e54fa22dfb82eaed4cd6631b with DEVEDITION_68_0b10_RELEASE a=release CLOSED TREE DONTBUILD
Mozilla Releng Treescript <release+treescript@mozilla.org> - Fri, 14 Jun 2019 14:45:34 +0000 - rev 533882
Push 11450 by ffxbld at Fri, 14 Jun 2019 14:45:47 +0000
No bug - Tagging 4c434d19d03d5461e54fa22dfb82eaed4cd6631b with DEVEDITION_68_0b10_RELEASE a=release CLOSED TREE DONTBUILD
c3afedd385f9605707f9db384afc694a76af9e7c: no bug - Bumping Firefox l10n changesets r=release a=l10n-bump DONTBUILD
L10n Bumper Bot <release+l10nbumper@mozilla.com> - Fri, 14 Jun 2019 14:00:21 +0000 - rev 533881
Push 11449 by ffxbld at Fri, 14 Jun 2019 14:00:28 +0000
no bug - Bumping Firefox l10n changesets r=release a=l10n-bump DONTBUILD et -> 80b798436017 kab -> 8f3b88265f73 ro -> 22efa19b8530
3d186dc3c2d0fb16e6d5554ed144fddd538a6b68: no bug - Bumping Fennec l10n changesets r=release a=l10n-bump DONTBUILD
L10n Bumper Bot <release+l10nbumper@mozilla.com> - Fri, 14 Jun 2019 14:00:14 +0000 - rev 533880
Push 11449 by ffxbld at Fri, 14 Jun 2019 14:00:28 +0000
no bug - Bumping Fennec l10n changesets r=release a=l10n-bump DONTBUILD et -> 80b798436017 kab -> 8f3b88265f73 ro -> 22efa19b8530
16b3ac40ffda0ecebd15f71ecb44e9514bcae781: no bug - Bumping Firefox l10n changesets r=release a=l10n-bump DONTBUILD
L10n Bumper Bot <release+l10nbumper@mozilla.com> - Fri, 14 Jun 2019 13:00:22 +0000 - rev 533879
Push 11448 by ffxbld at Fri, 14 Jun 2019 13:00:29 +0000
no bug - Bumping Firefox l10n changesets r=release a=l10n-bump DONTBUILD da -> 7c657538062f et -> a63df1237af4 fr -> 956ecd31111a pt-PT -> 8996c3f8adb8 sl -> e911313efb00
f39171df90997dbbffb4e2e853abfcf26a80b837: no bug - Bumping Fennec l10n changesets r=release a=l10n-bump DONTBUILD
L10n Bumper Bot <release+l10nbumper@mozilla.com> - Fri, 14 Jun 2019 13:00:15 +0000 - rev 533878
Push 11448 by ffxbld at Fri, 14 Jun 2019 13:00:29 +0000
no bug - Bumping Fennec l10n changesets r=release a=l10n-bump DONTBUILD da -> 7c657538062f et -> a63df1237af4 fr -> 956ecd31111a kab -> 97ce02682006 pt-PT -> 8996c3f8adb8 sl -> e911313efb00
c9edc4fbdfc8a0a5656e43d0afda6df03b93de7c: no bug - Bumping Firefox l10n changesets r=release a=l10n-bump DONTBUILD
L10n Bumper Bot <release+l10nbumper@mozilla.com> - Fri, 14 Jun 2019 06:00:22 +0000 - rev 533877
Push 11447 by ffxbld at Fri, 14 Jun 2019 06:00:28 +0000
no bug - Bumping Firefox l10n changesets r=release a=l10n-bump DONTBUILD eo -> 7da4ce932c6f es-CL -> ab40c79bec85 et -> b2ed039679b6 eu -> d967eaaab1e0 fr -> fa0f455baeb1 id -> b5920a695c4c nl -> c1cbc1be5f37 pt-PT -> 3aa7fe565d3b ro -> 4b47bc8639fc sk -> 559104ff218f sl -> 9b27dfe830b6 uk -> dd8cd4f1d9d0
abf322efc723897624040ad5e48519845b821bd1: no bug - Bumping Fennec l10n changesets r=release a=l10n-bump DONTBUILD
L10n Bumper Bot <release+l10nbumper@mozilla.com> - Fri, 14 Jun 2019 06:00:15 +0000 - rev 533876
Push 11447 by ffxbld at Fri, 14 Jun 2019 06:00:28 +0000
no bug - Bumping Fennec l10n changesets r=release a=l10n-bump DONTBUILD eo -> 7da4ce932c6f es-CL -> ab40c79bec85 et -> b2ed039679b6 eu -> d967eaaab1e0 fr -> fa0f455baeb1 id -> b5920a695c4c nl -> c1cbc1be5f37 pt-PT -> 3aa7fe565d3b ro -> 4b47bc8639fc sk -> 559104ff218f sl -> 9b27dfe830b6 uk -> dd8cd4f1d9d0
9ac627048305775d78799ea022d269d18d593262: Bug 1550291 - Ensure we save CRASHED status to be able to restore previous tabs; r=AndreiLazar, a=RyanVM, l10n=flod
Petru Lingurar <petru.lingurar@softvision.ro> - Thu, 13 Jun 2019 13:26:57 +0000 - rev 533875
Push 11446 by ryanvm@gmail.com at Thu, 13 Jun 2019 21:32:43 +0000
Bug 1550291 - Ensure we save CRASHED status to be able to restore previous tabs; r=AndreiLazar, a=RyanVM, l10n=flod Default app behavior for when a crash occurs involves starting an Activity that lets users submit a crash report and maybe provide additional info. In the event of a crash we want to restore for the user all previous tabs, this Activity being the component that saves the CRASHED status that will trigger the restore process. On Android Q, when a crash notification is posted but ignored by the user, upon starting the app would not know it crashed and it would not try restoring tabs. Executing the "save CRASHED status" logic whenever a crash occurs, irrespective of if we'll show the Activity or just post a notification ensures users will always have their previous tabs restored. Differential Revision: https://phabricator.services.mozilla.com/D34826
22cfa63e856377c0b7f502d194d4b17dc0c3acc9: Bug 1550291 - Android Q: Use the overlay permission or a foreground notification to start the crash handler; r=VladBaicu, a=RyanVM
Petru Lingurar <petru.lingurar@softvision.ro> - Mon, 10 Jun 2019 15:52:58 +0000 - rev 533874
Push 11446 by ryanvm@gmail.com at Thu, 13 Jun 2019 21:32:43 +0000
Bug 1550291 - Android Q: Use the overlay permission or a foreground notification to start the crash handler; r=VladBaicu, a=RyanVM Android Q doesn't allow starting Activities from background. https://developer.android.com/preview/privacy/background-activity-starts We can either piggy-back the SYSTEM_ALERT_WINDOW permission given by the user for the Tab Queue functionality or use a foreground notification from where users could start `CrashReporterActivity`. Differential Revision: https://phabricator.services.mozilla.com/D33029
a74afc1a7a210a327a623a075c5c206ef08e60ed: Bug 1550291 - Add new "Crash handler" notification channel; r=JanH, a=RyanVM
Petru Lingurar <petru.lingurar@softvision.ro> - Fri, 07 Jun 2019 08:01:46 +0000 - rev 533873
Push 11446 by ryanvm@gmail.com at Thu, 13 Jun 2019 21:32:43 +0000
Bug 1550291 - Add new "Crash handler" notification channel; r=JanH, a=RyanVM Differential Revision: https://phabricator.services.mozilla.com/D33028
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 tip