Re: CR exit criteria and features at risk for HTML5

I don't recall all of the specifics, but the Mercurial based system that the CSS WG was using for logging and tracking appeared quit elegant and powerful. The few tests that I was able to add went pleasantly and smoothly. FWIW.

John Foliot
Sent from my mobile device.
** Go Android **

"L. David Baron" <> wrote:

>On Thursday 2012-08-16 10:32 +0200, James Graham wrote:
>> On 08/16/2012 09:21 AM, Boris Zbarsky wrote:
>> >Well, a good start would be having a simple, advertized way to
>> >contribute tests.  I don't even know how I'd go about contributing a
>> >test for the HTML5 test suite, and my experience with contributing tests
>> >for other W3C working groups has been less than pleasant.  :(
>> >
>> >Of course contributing test suites to browsers that are not Mozilla is
>> >not that easy for me either.  But for Mozilla, it takes me very little
>> >time to add a test to the Mozilla test suite.  If we can get
>> >contributing tests for the official test suite down to that level, I bet
>> >developers will be more likely to contribute.
>> Well the actual "contribute" part is basically "commit to a hg
>> repo". The full instructions are at [1].
>Are those instructions sufficient to get a test into the "Approved
>Tests" list? [2]  Or is the "Approved Tests" subset not a relevant
>> [1]
>𝄞   L. David Baron                  𝄂
>𝄢   Mozilla                    𝄂

Received on Friday, 17 August 2012 19:37:19 UTC