W3C home > Mailing lists > Public > public-web-perf@w3.org > February 2017

Re: Update the Editor's Draft Specification Page

From: Ilya Grigorik <igrigorik@google.com>
Date: Sat, 11 Feb 2017 00:19:04 -0800
Message-ID: <CADXXVKowVh2JTgLSFsvA7KWmm8nwAKVtAdOEmr6pitkHy8KZjw@mail.gmail.com>
To: Yoav Weiss <yoav@yoav.ws>
Cc: Joseph Pecoraro <pecoraro@apple.com>, public-web-perf <public-web-perf@w3.org>
A bit of context.. Earlier in the year we:

   - Froze L1 under "v1" branch
   - Moved L2 under "v2" branch
   - Resolved to use "gh-pages" as the L3 branch

Since then we've merged a few L3-specific changes into gh-pages and
continued doing L2 cleanup in "v2", but haven't consistently upstreamed all
the v2 updates into gh-pages as the focus has been on L2 for the past few
months. Joe, sorry about the confusion this may have caused!

Yoav, thanks for the update, I'll merge that in. However, for anyone
looking at gh-pages.. be aware that you're looking at L3, not L2.

As an aside, I just realized that our TR updates are not auto-published..
- https://www.w3.org/TR/resource-timing-1/ - looks OK
- https://www.w3.org/TR/resource-timing-2/ - out of date.

Philippe: do we need to do anything special to hook up "v2" branch to
autoupdate the above?




On Fri, Feb 10, 2017 at 12:31 AM, Yoav Weiss <yoav@yoav.ws> wrote:

> Seems like many recent fixes went into the V2 branch rather than the
> gh-pages one :/
> I filed https://github.com/w3c/resource-timing/pull/97 in order to fix
> that.
>
> In the mean time, you can look at http://yoavweiss.github.io/
> resource-timing/ for the latest version.
>
> On Fri, Feb 10, 2017 at 6:45 AM Joseph Pecoraro <pecoraro@apple.com>
> wrote:
>
>> The Latest Editor's Draft is out of date:
>> https://w3c.github.io/resource-timing/
>>
>> I've lost quite a bit of time digging into and starting to file issues
>> only to discover they have already been discussed and resolved months ago:
>> https://github.com/w3c/resource-timing/pull/79
>> https://github.com/w3c/resource-timing/pull/80
>>
>> Is there any chance the editors draft could be updated. Or is there a
>> better place to view the latest draft text?
>>
>> Thanks,
>> - Joe
>>
>>
Received on Saturday, 11 February 2017 08:20:17 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 11 February 2017 08:20:17 UTC