Great! :)
On Fri, May 18, 2018 at 2:58 PM Kris Maglione wrote:
> Already done. :) https://bugzil.la/1460092
>
> On Fri, May 18, 2018 at 02:48:20PM -0400, Jared Wein wrote:
> >Have you looked in to adding an eslint rule for this? The eslint rule[1]
> >that recommends usage
Already done. :) https://bugzil.la/1460092
On Fri, May 18, 2018 at 02:48:20PM -0400, Jared Wein wrote:
Have you looked in to adding an eslint rule for this? The eslint rule[1]
that recommends usage of ChromeUtils.defineModuleGetter instead of
XPCOMUtils.defineLazyModuleGetter has been very
Have you looked in to adding an eslint rule for this? The eslint rule[1]
that recommends usage of ChromeUtils.defineModuleGetter instead of
XPCOMUtils.defineLazyModuleGetter has been very useful.
[1]
The discussion about what to do about these particular buildbot builds has
naturally shifted into a discussion about what kind of retention policy is
appropriate for CI builds.
I believe that right now we keep all CI build artifacts for 1 year. Nightly
and release builds are kept forever. There's
On 2018-05-18 3:30 AM, Henri Sivonen wrote:
On Thu, May 17, 2018 at 8:31 PM, mhoye wrote:
Well, more than a day or two. The MIT license is fine to include, and we
have a pile of MIT-licensed code in-tree already.
Other already-in-tree MPL-2.0 compatible licenses - the
On Thu, May 17, 2018 at 8:31 PM, mhoye wrote:
> Well, more than a day or two. The MIT license is fine to include, and we
> have a pile of MIT-licensed code in-tree already.
>
> Other already-in-tree MPL-2.0 compatible licenses - the "just do it" set,
> basically - include
6 matches
Mail list logo