Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Update issues links and add travis config #3
Thanks for this effort.
I prefer to keep all bug reports in the CPAN RT. That keeps all my Perl stuff in the same place and allows for depedency tracking. Has there been some community conversation about moving away from RT about which I'm not aware?
I have not made any CI effort for these small libraries in Travis or other CI tools, since cpantesters exists. Is there a similar conversation about that?
TravisCI seems to be gaining some real support as it has nice integrations with GitHub will run all the tests on all commits and pull requests. So if someone like me comes along with a pull request; it runs the tests so that any breakages are identified prior to it being accepted. For example if you take a look at lancew/Perl-Critic-Policy-Perlsecret#9 you can see where TravisCI has ticks and crosses showing when tests are passing or failing)
All before you do your release and it hitting cpantesters.
As for RT vs GitHub, mainly assumption on my part based on finding outstanding issues on GitHub and not on RT. :-)