| Subject: | feature: new meta entry for where to submit automated test reports |
No doubt this is the wrong place for this, but I'm not sure what mailing
list (or elsewhere?) would be best, instead, so, better here than
nowhere, for now:
(from #metacpan, 2012-09-23)
10:08 < ether> ... thoughts on a meta field indicating where to send
failed automated tests?
10:08 < ether> i.e. right now, cpantesters just mails to who last
released the dist, who may or may not be the primary author
10:09 < ether> it might be more useful for some dists to have an RT
ticket opened automatically
10:09 < ether> or an email to go to some other place entirely
11:29 < mike> project mailing list or something
11:29 < mike> I like it.
I've released a lot of dists recently that I didn't write and don't even
know the internals of very well, but because I was the last releaser, I
get all the failed cpantesters reports. If I don't now how to resolve a
particular issue, I just open an RT ticket for it to give the other
maintainers an opportunity to see it, but for dists with a large number
of maintainers, it would be more efficient to simply have a ticket be
opened directly and automatically. Likewise some large projects use
github issues to coordinate their task list, and it would be convenient
for them to have failed test reports to be channelled into that pipeline.
Is there a formal process for proposing additions to the meta spec?