Re: administrivia: Candidate Recommendation and Last Working Draft

Jeff,
You are correct. Let's make sure we change the heading on the call today.

On Wed, Feb 21, 2018 at 10:27 AM, =JeffH <Jeff.Hodges@kingsmountain.com>
wrote:

> I am wondering why we have the new "Last Working Draft" milestone <
> https://github.com/w3c/webauthn/milestone/3> rather than just continuing
> to use the CR (Candidate Recommendation) milestone?
>
> Note that the description for "Last Working Draft" links to a superseded
> (old) version of the W3C Process doc rather than the current Process Doc.
>
> In the current W3C Process Doc <https://www.w3.org/Consortium/Process/>
> (of 1-Feb-2018), the section on Candidate Recommendation <
> https://www.w3.org/2018/Process-20180201/#candidate-rec> states:
>
>   "A Candidate Recommendation corresponds to a "Last Call Working Draft"
>   as used in the W3C Patent Policy. Publishing a Candidate
>   Recommendation triggers a Call for Exclusions, per section 4 of
>   the W3C Patent Policy,..."
>
> Thus, unless I am misunderstanding this (which is possible), CR maturity
> level now equates to what was formally known as "Last Call Working Draft".
>
> Our description for CR milestone <https://github.com/w3c/webaut
> hn/milestone/15> says...
>
>   "Proposal for Candidate Recommendation Candidate maturity level."
>
> ..though it links to the same superseded Process doc -- I suggest we
> update that process link for the CR milestone and just use the CR milestone
> such that our milestones match the current process doc.  Plus update the CR
> milestone description to say..
>
>   "Proposal for Candidate Recommendation Candidate maturity level
>   (equivalent to Last Call Working Draft").
>   See <https://www.w3.org/Consortium/Process/>"
>
>
> hth,
>
> =JeffH
>
>
>
>
>


-- 

John Fontana

Identity and Standards Analyst | Yubico <http://www.yubico.com/>

Phone: +1 303 301 4437
Skype: j_fontana