Update definition to:
The new definition of Triaged will be Firefox-related bugs of type
defect where the component is not
UNTRIAGED, and a non-default value not equal to -- or N/A.
Bugs of type Task or Enhancement may have a severity of N/A,
but defects must have a severity that is neither -- or
N/A.
This means edits to the references to setting release
status flags (which are now not required.)
Also switching to using :ref:`link text <target>` for
internal links because of some errors when compiling
.rst to HTML.
Fix linter error in rst
Differential Revision: https://phabricator.services.mozilla.com/D74515
This changeset covers the new, severity-based triage process
Fix linting errors
Fix links and language
Fix headings and broken link
Add missing newline to labels.rst
Differential Revision: https://phabricator.services.mozilla.com/D73999
Code should be using `throw Components.Exception("", Cr.ERROR);` instead,
since `new Error()` just converts the int value of the Cr.ERROR into a string,
whereas `Exception` constructs an Exception object with the result property set
to the Cr.ERROR value, so other code can identify it.
Differential Revision: https://phabricator.services.mozilla.com/D28074
This rule is based on the ESLint built-in no-throw-literal. Cr.ERRORs are also
literals since they are just integers and so have all the same disadvantages of
no stack info.
TestInterfaceJS.js is explicitly testing handling of throwing raw Cr.ERRORs and
thus needs to stay.
Differential Revision: https://phabricator.services.mozilla.com/D28072
And tweak it so that if people want it can work outside-of the box (as
long as they have `eslint` in their path).
I've checked that mozilla-specific plugins also work with the setup I
mentioned.
Differential Revision: https://phabricator.services.mozilla.com/D71050
--HG--
extra : moz-landing-system : lando
For now, the local detection sucks. I will fix that once bug 1625884
is fixed
Differential Revision: https://phabricator.services.mozilla.com/D69683
--HG--
extra : moz-landing-system : lando
This is a frequent question in #introduction / #developers. I'm not
aware of any page in MDN that documents this kind of stuff.
This is intended to be a catch-all page for stuff that some people may
want to have like auto-completion, debugger/linter integration, etc...
In the future, maybe this should be a sub-section in a more general
"Improving your development environment" section or something like that,
where other stuff like commit hooks / mozconfig managers like [1] could
also be explained, but that seems premature, at least for now.
[1]: https://github.com/emilio/mozconfigs
Differential Revision: https://phabricator.services.mozilla.com/D70659
--HG--
extra : moz-landing-system : lando
Are there any Rust crates outside mozilla-central that include or emit Mozilla C++ code that should be updated to use [[nodiscard]] instead of MOZ_MUST_USE?
Depends on D68751
Differential Revision: https://phabricator.services.mozilla.com/D69319
--HG--
extra : moz-landing-system : lando
for now, it is just a pandoc -trst conversion and titles added
I will polish the files.
Differential Revision: https://phabricator.services.mozilla.com/D68510
--HG--
extra : moz-landing-system : lando
This preliminary in-tree build documentation is focused on the `mach`
workflow.
I've used reStructuredText for this because there are some nice features
(for example, see the nice 'Note' box we get).
I added a marker so that we could get a nice link to the linux build. Note,
that link only looks sensible if the whole tree of docs is built (first time
you run `mach doc`). Subsequent rebuilds only seem to rebuild the subtree
that is changed, and so that label isn't found and so is printed funny.
Differential Revision: https://phabricator.services.mozilla.com/D68299
--HG--
extra : moz-landing-system : lando
mhoye
Tilden Windsor
Benoit Chauvet
Sylvestre Ledru
Emma Humphries
Ian Moody
championshuttler
Frederik Braun
pbz
Cosmin Sabou
Emilio Cobos Álvarez
Ting-Yu Lin
Narcis Beleuzu
Chris Peterson
Matthew Gaudet
Andrew Halberstadt