On Tuesday, December 1, 2015 at 6:04:30 PM UTC-8, Jonas Sicking wrote:
> Oh well. Bummer.
>
> / Jonas
If it cheers you up any, the 2.0 API that replaces the U2F API uses promises -
http://www.w3.org/Submission/2015/SUBM-fido-web-api-20151120/
Richard, it would help if you could clarify - are yo
Oh well. Bummer.
/ Jonas
On Tue, Dec 1, 2015 at 5:36 PM, Richard Barnes wrote:
> It's my understanding that U2F qua U2F is considered pretty much baked by
> the developer community, and there's already code written to it. But these
> concerns will be great for the W3C group and the successor AP
It's my understanding that U2F qua U2F is considered pretty much baked by
the developer community, and there's already code written to it. But these
concerns will be great for the W3C group and the successor API. I've got a
similar list started related to crypto and future-proofing.
On Tue, Dec
Any chance that the API can be made a little more JS friendly? First
thing that stands out is the use of success/error callbacks rather
than the use of Promises.
Also the use of numeric codes, rather than string values, is a pattern
that the web has generally moved away from.
/ Jonas
On Tue, Dec
The FIDO Alliance has been developing standards for hardware-based
authentication of users by websites [1]. Their work is getting significant
traction, so the Mozilla Foundation has decided to join the FIDO Alliance.
Work has begun in the W3C to create open standards using FIDO as a starting
point
On Fri, Nov 27, 2015 at 02:53:35PM -0800, Dave Townsend wrote:
Going forwards we'd like to enable it in more directories and turn on
more rules. You can help! If there is a directory you work in a lot
try removing it from the top-level .eslintignore file and see what
fails, then fix it. Mostly it
On Tue, Dec 1, 2015 at 5:27 PM, Gregory Szorc wrote:
>
> On Tue, Dec 1, 2015 at 2:21 PM, Chris AtLee wrote:
>
>> Right now we've got debug OSX builds in the cloud on Try in parallel with
>> the regular builds. There's a bunch more work to be done there to be able
>> to switch over, but we're def
On Tue, Dec 1, 2015 at 2:21 PM, Chris AtLee wrote:
> Right now we've got debug OSX builds in the cloud on Try in parallel with
> the regular builds. There's a bunch more work to be done there to be able
> to switch over, but we're definitely making progress.
>
> All Windows / OSX unit tests are c
Right now we've got debug OSX builds in the cloud on Try in parallel with
the regular builds. There's a bunch more work to be done there to be able
to switch over, but we're definitely making progress.
All Windows / OSX unit tests are currently done on our own infra. Q Fortier
is working on gettin
On 12/1/15 12:41 PM, Chris AtLee wrote:
Last week we made the same change to the rest of the Windows build
infrastructure. All our Windows builds are now running in AWS. We're seeing
good performance gains there too. On mozilla-inbound, we've reduced opt
build times by at least 45 minutes, and n
One approach we've taken when considering changes to the routes used is to
play in the 'garbage.' prefix. You can see the results of earlier
experiments there:
https://tools.taskcluster.net/index/#garbage/garbage
Regarding your proposal, I find the word 'nightly' overloaded, and it needs
more con
A few weeks ago I posted about switching our Windows builds on Try over to
EC2, resulting in a 30 minute speed improvement.
Last week we made the same change to the rest of the Windows build
infrastructure. All our Windows builds are now running in AWS. We're seeing
good performance gains there to
To close the loop here, I just enabled service workers on Firefox 44
(currently on Aurora.)
Thanks to everyone who helped make this happen. It was a lng ride. :-)
On Fri, Nov 20, 2015 at 5:24 PM, Robert O'Callahan
wrote:
> On Sat, Nov 21, 2015 at 9:42 AM, Ben Kelly wrote:
>
> > I think t
Hello Everyone,
There's a new addition to https://telemetry.mozilla.org today: Dashboard
Generator (https://telemetry.mozilla.org/dashboard-generator/index.html).
It comes with an accompanying blog post (
https://chuttenblog.wordpress.com/to-order-telemetry-dashboards-dashboard-generator/)
bu
Yes, I will be testing those features on Fennec later this week and
enabling them as well if they work well (or investigating why if they
don't). :)
On Tue, Dec 1, 2015 at 2:14 PM, Kearwood "Kip" Gilbert
wrote:
> Excellent, Kats!!
>
> Perhaps this will also unblock smooth scrolling and scroll sna
Excellent, Kats!!
Perhaps this will also unblock smooth scrolling and scroll snapping for fennec.
Cheers,
- Kearwood “Kip” Gilbert
> On Nov 30, 2015, at 8:37 AM, Kartikaya Gupta wrote:
>
> Hi all,
>
> Just a heads up that I landed the patch to enable APZ on Fennec
> (nightly channel only for
hi,
Because we have an index, it's now very easy to add new routes. I think
it would be a lot more user-friendly to have an index that starts with
the product name ("firefox" for example).
For example: "gecko.v2.firefox.win64-opt.nightly.latest" instead of
"gecko.v2.mozilla-central.nightly.latest
You're right in that we can't change the expiration after the fact, but we
can copy all of the artifacts to new tasks with the longer expiration.
On Tue, Dec 1, 2015 at 9:53 AM, Ryan VanderMeulen wrote:
> What does that mean for jobs that have already run? My understanding is
> that we can't cha
Awesome! Thanks to the team that made this happen.
(CC'ing dev-mobile-firefox too)
On Mon, Nov 30, 2015 at 11:37 AM, Kartikaya Gupta
wrote:
> Hi all,
>
> Just a heads up that I landed the patch to enable APZ on Fennec
> (nightly channel only for now). It should be in the Dec 1 nightly and
> onw
What does that mean for jobs that have already run? My understanding is
that we can't change the expiration after the fact for them? Though I
guess that it's not an issue as long as we fix bug 1145300 prior to
shutting off publishing to archive.m.o?
I just want to avoid any gaps in nightly bui
The expiration is currently set to one year, but we can (and should!)
change that for nightlies. That work is being tracked in
https://bugzilla.mozilla.org/show_bug.cgi?id=1145300
On Mon, Nov 30, 2015 at 7:00 PM, Ryan VanderMeulen wrote:
> On 11/30/2015 3:43 PM, Chris AtLee wrote:
>
>> The RelEn
Localized builds should be at e.g.
gecko.v2.mozilla-central.latest.firefox-l10n.win32-opt
And yes, once we've got the naming structure nailed down, wget-en-US should
change to use the index.
On Tue, Dec 1, 2015 at 5:22 AM, Axel Hecht wrote:
> I haven't found localized builds and their assets by
Hi,
To give a little insight into our work and make our work more visible to
our Community we decided to create a monthly report of what's going on in
the Sheriffs Team.
If you have questions or feedback, just let us know!
In case you don't know who the sheriffs are, or to check if there are
cu
On 2015-11-30 22:11, Mitchell Baker wrote:
5. Many inside of Mozilla, including an overwhelming majority of our
leadership, feel the need to be laser-focused on activities like Firefox
that can have an industry-wide impact.With all due respect to
Thunderbird and the Thunderbird community, we
On Monday, November 30, 2015 at 10:08:19 PM UTC+1, Mitchell Baker wrote:
> This is a long-ish message. It covers general topics about Thunderbird
> and the future, and also the topics of the Foundation involvement (point
> 9) and the question of merging repositories (point 11). Naturally, I
>
I haven't found localized builds and their assets by glancing at things.
Are those to come?
Also, I suspect we should rewrite wget-en-US? Or add an alternative
that's index-bound?
Axel
On 11/30/15 9:43 PM, Chris AtLee wrote:
The RelEng, Cloud Services and Taskcluster teams have been doing a
26 matches
Mail list logo
