[webkit-dev] Filling the features.json files

[Benjamin Poulain]

On 4/8/15 3:52 PM, Bem Jones-Bey wrote:
>
>> On Apr 8, 2015, at 15:45, Benjamin Poulain <benjamin at webkit.org>
>> wrote:
>>
>> On 4/8/15 12:01 PM, Bem Jones-Bey wrote:
>>>
>>> On 4/7/15, 21:09, "Benjamin Poulain" <benjamin at webkit.org>
>>> wrote:
>>>>
>>>> The only mandatory fields are "name" and "status".
>>>
>>> What are the valid values for the “status” field, and what is the
>>> criteria for a feature to be classified under each value?
>>
>> -"enabled-by-default" tells if the feature is in WebKit nightly.
>> -"status" is free text, it will be shown as it is. -"shipped" is
>> the list of the first release versions shipping the feature.
>>
>> For the status text, I have not made up any rule yet. I used:
>> -"Done": fully functional, maybe some minor bugs left.
>> -"Prototyping": proof of concept kind of work. -"In Development":
>> anything in between the other two. Even something that barely work
>> can use this.
>>
>> Outside status, you can also add "comment" if you want to clarify
>> something, want feedback, etc.
>
> What do you think about having a version of “Done” for fully
> functional, but -webkit prefixed? For example, we’ve implemented all
> the features of CSS Shapes Level 1, the spec is in CR, but we still
> have some bugs to fix. I’d assume that would be past the prototyping
> phase at this point, but not quite Done, given that it’s still
> prefixed.

If there are only minor bugs left, my first preference would be to 
unprefix. :)

If the bugs are not so minor, I think "In Development" would be okay.

You can also make up your own status string for now, I'll triage them at 
some point :)

All of this is really about documentation. Add as much comments as you 
need in "comment" to explain the state of the feature.

Benjamin