- Build: Memory footprint
Background: 8 GB is our recommended minimum for building on Windows. New
contributors don't necessarily have high-end developer machines. By
noticing bumps we can evaluate the cost/benefit of these and protract
further bumps of the recommended minimum.
- Tests:
Hi,
at the moment, there is major internet outage affecting cloud services
like Amazon's AWS.
Because the release automation infrastructure depends on that, we had to
close the trees and you won't be able to push. At the moment, it's not
possible to say when trees will be reopened.
This has now been merged to mozilla-central and autoland.
Sebastian
Original-Nachricht
Betreff: PSA: RELEASE_BUILD gets renamed to RELEASE_OR_BETA
Von: Sebastian Hengst <a...@gmx.de>
An:
Datum: 2016-10-08 15:55
https://bugzilla.mozilla.org/show_bug.cgi?id=1304829 r
https://bugzilla.mozilla.org/show_bug.cgi?id=1304829 renames the
RELEASE_BUILD switch to RELEASE_OR_BETA. This has already landed on
mozilla-inbound and so will likely get merged around to mozilla-central
and autoland over the weekend.
Please update your patches if they use RELEASE_BUILD and
Hi,
as has been announced earlier
https://groups.google.com/forum/#!topic/mozilla.dev.fxos/FoAwifahNPY the
Boot 2 Gecko (B2G) code will be removed from mozilla-central.
A tracking bug has been created for that work:
https://bugzilla.mozilla.org/show_bug.cgi?id=1306391 So if you remove
code
TL;DR
- UI got more verbose, elements unnecessary hidden
- Too much vertical space used
- Passes and failures shouldn't be separated
- failure log becomes longer because of failure snippets
User persona
Developers:
- check the results of their own pushes to Try and own pushes to
official
https://bugzilla.mozilla.org/show_bug.cgi?id=1328464
The 'Add me to CC list (follow this bug)' checkbox in Bugzilla is
broken, use the Follow button in modal UI for CCing.
Sebastian
___
dev-platform mailing list
dev-platform@lists.mozilla.org
The new policy will be used from now on.
- Sebastian
Original-Nachricht
Betreff: mozilla-inbound backout policy subject to change (become
similar to autoland)
Von: Sebastian Hengst
Datum: 2018-06-19 15:04
Hi,
If you don't push code to mozilla-inbound, you can stop reading
Original-Nachricht
Betreff: Re: mozilla-inbound backout policy subject to change (become
similar to autoland)
Von: Boris Zbarsky
Datum: 2018-06-24 21:28
On 6/19/18 9:04 AM, Sebastian Hengst wrote:
TL;DR: We would like to change the mozilla-inbound backout policy to
be like
Hi,
If you don't push code to mozilla-inbound, you can stop reading now.
TL;DR: We would like to change the mozilla-inbound backout policy to be
like autoland’s.
In order to decrease tree closure times for inbound, allow for more
frequent merges from inbound to m-c, and ensure consistent
Original-Nachricht
Betreff: Re: mozilla-inbound backout policy subject to change (become
similar to autoland)
Von: Myk Melez
Datum: 2018-08-09 02:11
Boris Zbarsky wrote on 2018-06-26 21:53:
On 6/27/18 12:50 AM, Mike Hommey wrote:
Perma bustage of tier-2 jobs usually do.
to autoland)
Von: Sebastian Hengst
Datum: 2018-06-19 15:04
Hi,
If you don't push code to mozilla-inbound, you can stop reading now.
TL;DR: We would like to change the mozilla-inbound backout policy to be
like autoland’s.
In order to decrease tree closure times for inbound, allow for more
frequent
Hi,
if you push to the Try server, use base revisions (= the shared revision
on top of which you add your changes) from 2019-02-06 or newer, else
there will be many test failures due to expired certificates. The newer
base revisions have the fixes from
Hi,
some of you use the Mercurial bzpost extension to get Treeherder links
generated and posted to the mentioned bug after you pushed to the Try
server. A Treeherder change requires that those links use the last
revision from the push to work. The fix is available, you can install it
by
Hi,
mozilla-central got merged to mozilla-beta today (both on Gecko 70) and
the tool to update the merged bugs ran unnecessarily. Please ignore
those comments which mention the push urls for beta.
Thank you
Sebastian Hengst
Code Sheriffing Lead
:
If code from inbound can be merged to central, it will get merged by
sheriffs approximately every 6h during workdays and every 12h on weekends.
Sebastian Hengst
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org
Because some certificates stored in the source code directory needed
renewal, pushes to Try based on older revisions than the latest commit
("tip") for all mozilla-* repositories and autoland will yield many test
failures.
Please rebase your patch stack before pushing to Try.
that enable new Features that were untested in the Nightly
cycle
- Plan to kick off new experiments that might impact a feature's merge
readiness
Please let us know if you have any questions/concerns.
Thanks,
Sebastian & the Release Management team
--
Sebastian Hengst
Code Sheriffing
The Nightly version bump to 82 was completed successfully today and the
soft freeze is now lifted.
Sebastian
Am 19.08.2020 um 16:27 schrieb Sebastian Hengst:
Hi all,
With Firefox 80 release candidates already shipping, we are nearing the
end of the Nightly 81 cycle.
In order to avoid
process is schedule to be complete at 14:00 UTC, the
Firefox CI should be unavailable for a shorter timeframe.
Sebastian Hengst
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
If you use Treeherder to add tasks to Try pushes, retrigger them etc.
and get an error about the credentials being disabled, please resolve
the issue with these steps:
1. Open a Treeherder tab: https://treeherder.mozilla.org/
2. In Firefox, press Ctrl+Shift+H to open the browser's history.
3.
21 matches
Mail list logo
