> IMHO, you should still include author-only tests in your published > distributions, even if they don't run during the usual "test" > target. That way, you can still get patches from developers who can't > (or won't) pull the code from the repository.
Frankly, I'm not too worried about missing out on patches from people who can't/won't grab the latest version from the well-publicized public repository. That's a pretty low bar. > Plus, it helps encourage other developers to write similar tests if > they happen to see you doing it too A better point, but if other developers want to learn from you, they should be checking out your development environment, not just your published product. -- Greg Sabino Mullane g...@endpoint.com End Point Corporation PGP Key: 0x14964AC8
signature.asc
Description: OpenPGP digital signature
