Trac'ing tests status

Will Coleda will at coleda.com
Wed Aug 26 14:49:20 UTC 2009


We should be following rakudo's example of not closing tickets for
which tests could be written.

We could abuse the existing trac fields we have to help track this
status, or we could add a new "Tests" field, with "needs, has, can't,
<null>"

Moritz has suggested we should additionally track the name of the test file.

Throwing to the list for discussion; I'll get OSU to update our trac
instance if it turns out we decide we need new field(s) for this.

-- 
Will "Coke" Coleda


More information about the parrot-dev mailing list