W3C home > Mailing lists > Public > public-css-testsuite@w3.org > October 2010

Re: Corrections to the Implemention Reports

From: Simon Fraser <smfr@me.com>
Date: Thu, 28 Oct 2010 08:37:50 -0700
Cc: fantasai <fantasai.lists@inkedblade.net>, "Tab Atkins Jr." <jackalmage@gmail.com>, Peter Linss <peter.linss@hp.com>, John Jansen <John.Jansen@microsoft.com>, "public-css-testsuite@w3.org" <public-css-testsuite@w3.org>
Message-id: <25714CD2-9C81-4F62-A1D3-DCB2F0EBD4F5@me.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
On Oct 28, 2010, at 6:33 am, Boris Zbarsky wrote:

>>> On this note, is it indeed acceptable to use current beta or dev
>>> builds of Chrome for the IR?
> ...
>> If the entire source is available along with build instructions
>> such that a member of the public can build a binary identical
>> to the one you used for testing, then, yes.
> Hold on.  I thought we had some criteria along the lines of "sort of shippable" (relaxed from "actually shipped") and in particular wanted to exclude special test builds, nightlies, etc, no?
> I haven't sorted out what the "beta" and "dev" labeling actually means in Chrome's case, but based on my weak understanding it seems like "dev" would not be acceptable and "beta" might be.

What I recall from CSS-WG minutes is that the implementation report can be generated with a public beta or nightly build, but that build has to have been available to the public for a minimum of one month.

Received on Thursday, 28 October 2010 15:38:30 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:13:21 UTC