Also to note, we moved spark? to 2.5? and spark+ to 2.5+ for blocking-b2g
bugs
On Tue, Jun 30, 2015 at 6:32 PM, Josh Cheng wrote:
> Dear b2g friends,
>
> Just to inform you the following change has been applied to Bugzilla since
> we have announced FxOS 2.5:
>
> 1. *blocking-b2g* and* feature-b2
Dear b2g friends,
Just to inform you the following change has been applied to Bugzilla since we
have announced FxOS 2.5:
1. blocking-b2g and feature-b2g flags are renamed from 3.0?/+ to 2.5?/+.
2. New tracking flag status-b2g-v2.5 is created.
Sincerely,
-
On Tue, Jun 30, 2015 at 3:04 PM, Fabrice Desré wrote:
> On 06/30/2015 02:50 PM, Jonas Sicking wrote:
>> Definitely use RequestSync rather than alarm API! There are battery
>> saving advantages already, and these advantages will just get better
>> in the future as we improve the implementation of t
On 06/30/2015 02:50 PM, Jonas Sicking wrote:
> Definitely use RequestSync rather than alarm API! There are battery
> saving advantages already, and these advantages will just get better
> in the future as we improve the implementation of the API.
Are you sure about the battery savings? Last I look
Definitely use RequestSync rather than alarm API! There are battery
saving advantages already, and these advantages will just get better
in the future as we improve the implementation of the API.
/ Jonas
On Tue, Jun 30, 2015 at 10:32 AM, wrote:
> Speaking of using the RequestSync API, is that
Speaking of using the RequestSync API, is that what Mozilla recommends using
now? I think most user-created apps are still using alarms for that
functionality. But since the email app now uses it (bug 1098289), I'm guessing
it's OK for all apps to use. If so, I think the MDN App Development FAQ
