W3C home > Mailing lists > Public > public-webauthn@w3.org > May 2017

RE: WD-05 Publish Schedule

From: Anthony Nadalin <tonynad@microsoft.com>
Date: Wed, 3 May 2017 18:43:36 +0000
To: "Hodges, Jeff" <jeff.hodges@paypal.com>, W3C Web Authn WG <public-webauthn@w3.org>
Message-ID: <SN1PR0301MB2029B48A012FB3472E7365D7A6160@SN1PR0301MB2029.namprd03.prod.outlook.com>
I believe that was the agreement we came to today 

-----Original Message-----
From: Hodges, Jeff [mailto:jeff.hodges@paypal.com] 
Sent: Wednesday, May 3, 2017 11:30 AM
To: Anthony Nadalin <tonynad@microsoft.com>; W3C Web Authn WG <public-webauthn@w3.org>
Subject: Re: WD-05 Publish Schedule 

Ok, based on our discussion on the call today..
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2017%2F05%2F03-webauthn-minutes.html&data=02%7C01%7Ctonynad%40microsoft.com%7C90c7ee3e89cd4056c45608d492526785%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636294330001553568&sdata=r2uyN8r%2B4pmVaX94qxTseC5YVof7bKaYPaYDlWR0VFY%3D&reserved=0

..all issues marked for milestone WD-05..
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwebauthn%2Fmilestone%2F9&data=02%7C01%7Ctonynad%40microsoft.com%7C90c7ee3e89cd4056c45608d492526785%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636294330001553568&sdata=QyAsaCDpAPJAx3e2NfSr6gMFp8jyRkGg4TeBcCtTze8%3D&reserved=0

..EXCEPT for issues #245 and #367 (which will ostensibly be fixed by PR#429 [1], yes?), should be moved to milestone WD-06, yes?


[1] https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwebauthn%2Fpull%2F429&data=02%7C01%7Ctonynad%40microsoft.com%7C90c7ee3e89cd4056c45608d492526785%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636294330001553568&sdata=T46b0lS9wx%2BVdll6JbsFlOHknWjLe5hG1CpxyFNPRhA%3D&reserved=0



On 5/2/17, 4:25 PM, "Anthony Nadalin" <tonynad@microsoft.com> wrote:

There have various issues that have been tagged by various people as “priority:implementation” that the some of the implementors are willing to take a risk on in hope that the change will not be needed or there is a good justification for making a breaking change, going into an implementation draft will help justify the remaining open issues. I really don’t want this to linger on trying for every single issue to be resolved as next week there will be someone’s else’s view on for instance what a name should be. I’m using  PR#429 as a gauge to publish WD05. So let’s see if we can’t push to resolve tomorrow and start the process to publish WD-05 so we have a concreate “thing” to point developers to.


Received on Wednesday, 3 May 2017 18:44:11 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 07:26:25 UTC