sting time and effort into this area!
Improvements to build times are always always welcome.
I seem to recall we collect opt-in Telemetry on things like build times. If
so, have we noticed any changes in those graphs?
-Mike
--
glob — engineering workflow manager — mo
.
-glob
--
glob — engineering workflow manager — moz://a
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
h out to Joe Walker if you have an urgent need to land changes.
--
glob — engineering workflow manager — moz://a
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
out of sequence.
See https://bugzilla.mozilla.org/1657542 for more information.
--
glob — engineering workflow manager — moz://a
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
to the MozillaBuild shell
* Removed nodejs
* Updated Python2 to version 2.7.16 and Python3 to version 3.7.4
* Updated emacs to 26.3
* Other updates to various included components.
Full Release Notes:
https://docs.google.com/document/d/1sIjCoqpRQqb-MbcZ7m6uLnlVSPh_CbQt2LfPYiqCfPc
-glob
--
glob
It's available now - make sure you're running the latest version by
running `moz-phab self-update`.
-glob
Henrik Skupin wrote on 23/10/19 11:49 pm:
Piotr Zalewa wrote on 22.10.19 17:25:
Since today MozPhab does not require Arcanist to submit patches in all
supported VCS's. I
feel should be written down.
The contents will be moved to a more suitable home once the initial
gathering phase is completed.
Thanks!
-glob
--
glob — engineering workflow — moz://a
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https
lando.
--
glob — engineering workflow — moz://a
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
.
--
glob — engineering workflow — moz://a
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
firefox-dev mailing list
firefox-...@mozilla.org
https://mail.mozilla.org/listinfo/firefox-dev
--
glob — engineering workflow — moz://a
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
ever it would be worse as it's imposed by a system separate
from the review/landing tooling).
-glob
--
glob — engineering workflow — moz://a
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
ction up-front.
thanks mak for drawing attention to this difference/feature.
-glob
--
glob — engineering workflow — moz://a
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
mhoye wrote:
Does "just do it" imply that it's now OK to import that stuff without
an analog of the previous r+ from Gerv?
I'm putting together a licensing runbook with Legal's help, and the
aim of that will be getting us to that point. As well, Glob is
building some
thanks to everyone who provided feedback for this proposal.
looks like general consensus is to proceed with the plan.
i've filed bug 1454867 to track the work.
-glob
glob wrote:
The plan is to create a YAML file for each library containing
metadata such as the homepage url, vendored ve
. devtools,
activity stream, screenshots, etc) will need to take a different
approach, which will be addressed later (this is the primary reason for
the manifest having a 'schema' field).
--
glob — engineering workflow — moz://a
___
dev-platf
using moz.build
files for declaring static metadata (such as bug components); see
https://groups.google.com/forum/#!topic/mozilla.dev.builds/X5hbK6a4VQc
--
glob — engineering workflow — moz://a
___
dev-platform mailing list
dev-platform@lists.mo
use
https://spdx.org/licenses/ and have a script to enforce that bogus
values don't creep in.
thanks; updated.
--
glob — engineering workflow — moz://a
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
vendoring, is that intentional?
to echo gps and mike's responses use of a sha to is preferred over tags.
--
glob — engineering workflow — moz://a
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
files where required, as well as
adding the capability for push-button vendoring of new revisions.
Please address comments to the dev-platform list.
--
glob — engineering workflow — moz://a
___
dev-platform mailing list
dev-platform@lists.mozilla.org
.org/mozilla-central/source/netwerk/dns/effective_tld_names.dat?raw=1
http://mxr.mozilla.org/mozilla/source/security/nss/lib/ckfw/builtins/certdata.txt?raw=1
(via https://bugzilla.mozilla.org/show_bug.cgi?id=1281389)
-glob
--
byron jones :: glob.com.au <htt
't accurate: when a patch is autolanded, the committer is set to
the person who triggered autolanding, not a generic 'autoland' account.
you cannot use the commiter name to filter our patches that were not
autolanded.
-glob
___
dev-
a lot
of time against securing it.
you'd be better served by deploying an alternative source browser.
-glob
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
this started happening via
https://bugzilla.mozilla.org/show_bug.cgi?id=972040
please file a bug and we'll apply per-product filtering -- currently
it'll be set on any product that has that flag.
(i'm not sure why seamonkey has that flag visible on its bugs)
-glob
Philip
23 matches
Mail list logo