Re: Retaining Nightly users after disabling of legacy extensions

On 8/24/17 2:08 AM, Andrew Swan wrote: > On Thu, Aug 24, 2017 at 12:03 AM, Alessio Placitelli < > aplacite...@mozilla.com> wrote: > >> 2017-08-24 0:00 GMT+02:00 Andrew McKay : >>> The recommendations are being populated and other changes are being >>> made. For example, on

Photon Engineering Newsletter #14

(via https://mikeconley.ca/blog/2017/08/24/photon-engineering-newsletter-14/ - I suggest visiting that post directly if you want to see the animated GIFs inline) Just like jaws did last week , I'm taking over for dolske

Update: Treeherder downtime / Tree closure 8/26/17 7:00am PT

After talking to releng and a few others, I’ve moved this closure to this Saturday 8/26/17 7:00am PT (was originally going to be Monday) Details: I have to run a DB migration on Treeherder that will take around 4 hours to complete. And during that time, job ingestion will be paused. So

Re: Retaining Nightly users after disabling of legacy extensions

2017-08-24 0:00 GMT+02:00 Andrew McKay : > If an extension updates to a WebExtension, users will automatically > get that update. > > If the author or another author creates an alternative then a user > will have to find that. > > The recommendations are being populated and

Re: Triage Summary 2017-08-21

I've seen you started marking unassigned P1s as "stale" and stating their priority will be reset if they stay unassigned. Please don't do that, it's a very bad idea. We are using P1s to have a list of bugs the team should be working on as soon as they have time, and there must be no strict

Re: Retaining Nightly users after disabling of legacy extensions

On Thu, Aug 24, 2017 at 12:03 AM, Alessio Placitelli < aplacite...@mozilla.com> wrote: > 2017-08-24 0:00 GMT+02:00 Andrew McKay : > > The recommendations are being populated and other changes are being > > made. For example, on September 1st only WebExtensions will be > >

Re: refcounting - which types to use ?

On Thursday, August 17, 2017 at 1:02:56 PM UTC+2, Aryeh Gregor wrote: > Note that in this case you cannot ignore the return value -- it must > be assigned to an nsCOMPtr or a RefPtr, or else it will leak. Ideally > we would allow a return type of nsCOMPtr&&, but > currently I think we don't.

Re: refcounting - which types to use ?

How could I make it compile error? I did write RefPtr xxx = yyy; xxx.forget(); It is ok for compiling on my Mac. The comment [1] said " Makes it a compile time error to not use the return value of a function which has this type", but how do I make the clang format take effect? BTW, if you

Re: refcounting - which types to use ?

On Thursday, August 24, 2017 at 11:56:53 AM UTC+2, James Cheng wrote: > How could I make it compile error? > > I did write > > RefPtr xxx = yyy; > xxx.forget(); You need to run the static analyser. The documentation about MOZ_MUST_USE_TYPE is explained there

Deploying xulrunner application with Firefox-SDK

Hi, I am working on a desktop application named "AZARDI" which is based on xulrunner. It is an offline ePub Reader for all three major platforms (Windows, Mac, Linux). You can check it out at http://azardi.infogridpacific.com/. I have been deploying the application successfully with