Hi, I wonder if there's any objection among the Trac team for moving toward accepting pull requests on GitHub? Is there a reason you prefer attaching patches to tickets instead? Django used to only accept patches that way, but since we started accepting pull requests some years ago, anytime someone uploads a patch to Trac, I ask if they can create a pull request instead. The ability to leave inline comments makes code review much easier and we also have continuous integration with Jenkins to automatically run the tests on each patch.
I've thought of trying to setup continuous integration for Trac using Travis unless there's already a system in place that I don't know about or if someone knows of a reason why Travis wouldn't work. I'd like to help with the Python 3 effort soon, but I think we'll need to use GitHub for review and it would be nice to have automated tests too. Thanks, Tim -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at https://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
