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

Re: updating milestone labels

From: <jeff.hodges@kingsmountain.com>
Date: Fri, 6 May 2016 18:46:43 -0600
Message-ID: <86a60038b6191dff24453289ed4cf378.squirrel@box514.bluehost.com>
To: "Wendy Seltzer" <wseltzer@w3.org>
Cc: "W3C WebAuthn WG" <public-webauthn@w3.org>


> On 05/06/2016 06:15 PM, jeff.hodges@kingsmountain.com wrote:
>> Tony created two milestones in our w3c/webauthn repo..
>>
>>    https://github.com/w3c/webauthn/milestones
>>
>>    FPWD - First Public Working Draft - only issues that need to be resolved
>> for
>> the Second Public Working Draft
>>
>>    SPWD - Second Public Working Draft - only issues that need to be resolved
>> for the Second Public Working Draft
>>
>>
>> However, as Wendy informed us on the call last Tue, the W3C process doesn't
>> have a notion of "second public working draft".  Rather, the next major
>> process step is to promote the draft spec to "candidate recommendation"..
>>
>>    https://www.w3.org/2015/Process-20150901/#maturity-levels
>>
>>
>> Note that a FPWD is allocated a spot in the W3C "TR" (technical report)
>> namespace, namely..
>>
>>    https://www.w3.org/TR/<ShortNameHere>/
>>
>> Further note that we, the WG, can (and likely will) update our working draft
>> spec copy in the TR namespace from time-to-time as our "editors' draft"
>> matures (the latter (in rendered form) is: https://w3c.github.io/webauthn/).
>
> Yup, the process (and good practice of keeping the /TR document a useful
> reference to those following our work) also recommends publishing
> periodic snapshots of the Editors' Draft.

I believe we are effectively doing the latter by auto-snapshotting to the
gh-pages branch upon merges to master, and thus published at
https://w3c.github.io/webauthn/, yes?



>> Thus I suggest we establish milestones as we go along for such updates to
>> published-in-TR-namespace-working-draft along the lines of..
>>
>>    FPWD-00  (renamed present FPWD milestone (yes, milestone
>>              names are updateable))
>>    FPWD-01  (MS for next refresh of published-in-TR-namespace-working
>>              -draft, target date TBD)
>>
>>    ..etc (if needed)..
>>
>>    CR       (renamed SPWD milestone with same target date
>>              of 13-Sep-2013 (for now))
>>
>>
>> WDYT?
>
> Makes sense to me. (Possibly just WD-01, etc., since after FPWD, it's no
> longer First.)

good point, agree.

=JeffH
Received on Saturday, 7 May 2016 00:53:50 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:38:15 UTC