Will Coleda wrote:
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>"
This might be a good point at which to review all of the existing
fields. For example, we might want to have one field called "testing"
that deals with our overall testing procedures (example, the issue of
does each PMC get its own test file) and a differently named field for
particular failing tests.
kid51
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
