W3C home > Mailing lists > Public > public-web-perf@w3.org > April 2021

Re: Call for Consensus - CR publishing

From: Benjamin De Kosnik <bdekoz@mozilla.com>
Date: Thu, 15 Apr 2021 11:01:03 -0700
Message-ID: <CAEHQyn1HY8r32G=CbcwOESeAwua7R_id4RfN_5UTnNtJ+j7Cng@mail.gmail.com>
To: Yoav Weiss <yoavweiss@google.com>
Cc: public-web-perf <public-web-perf@w3.org>, Nic Jansma <nic@nicj.net>, Carine Bournez <carine@w3.org>
No objection, just to put it in the record.

-benjamin

On Thu, Apr 15, 2021 at 7:47 AM Yoav Weiss <yoavweiss@google.com> wrote:

> Hey all,
>
> This is a call for consensus, following the WG discussion on April 1st
> <https://w3c.github.io/web-performance/meetings/2021/2021-04-01/index.html>.
> We’d like to get the group’s consensus to publish the following
> specifications to CR:
>
> Performance Timeline L2 <https://www.w3.org/TR/performance-timeline-2/>
>
> Resource Timing L2 <https://www.w3.org/TR/resource-timing-2/>
>
> User Timing L3 <https://www.w3.org/TR/user-timing-3/>
>
> The high level plan is to move those specifications to CR, and then keep
> them there as a Living Standard, with regular CR draft
> <https://www.w3.org/2020/Process-20200915/#candidate-recommendation-draft>
> publication and periodic CR updates
> <https://www.w3.org/2020/Process-20200915/#publishing-crrs>.
>
> We don’t plan to publish L3 for Performance Timeline and Resource Timing,
> and instead want to make sure that the default /TR link points at the
> latest CR drafts of those specifications.
>
> Please let us know of any objections you may have of the above plan.
>
> The deadline for this CfC is April 30th.
>
> Cheers,
>
> Yoav & Nic
>
>
Received on Thursday, 15 April 2021 18:01:28 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 15 April 2021 18:01:29 UTC