14 Aug
2015
14 Aug
'15
3:27 p.m.
Stefan wrote:
I think it might be best if such a decision didn't have to be taken for all of Boost at once. Why can't individual project maintainers decide for themselves (and their respective communities) what tools to use ? For example, I'm actively encouraging new Boost.Python issues to be filed on github, and I have documented that in the Boost.Python website
Makes sense. Does that complicate things for release managers in any way? (Having to check both Trac and GitHub issues?) Also, some libraries' GitHub Issues have been disabled. Glen -- View this message in context: http://boost.2283326.n4.nabble.com/boost-org-https-certificate-expired-4-mon... Sent from the Boost - Dev mailing list archive at Nabble.com.