Ezio Melotti <ezio.melo...@gmail.com> added the comment:
Keep in mind that converting the repo to Git will make it more difficult to upgrade, since our roundup is a clone of the main Roundup repo. So, assuming this issue moves forward, we can either: * start using official Roundup releases (this means no changes to Roundup, only the instances); * wait for upstream Roundup to switch to git and keep the same workflow (there has been some talk about it, but if/when will happen is still unknown); * keep updating from their clone with some extra steps in between to convert between hg and git every time; * come up with a new workflow that is equally flexible and easy; Note that one of the reasons why we run a clone of Roundup is to be able to fix/change things upstream and being able to deploy them on our tracker immediately, without having to wait months for the next release and without having our branch diverge and have to deal with conflicts later. This has been done several times in the past in case of security issues. As for the metatracker, I wouldn't be against moving it to github (if it's possible to create a source-less project just to use the issue tracker). ---------- nosy: +ezio.melotti status: unread -> chatting _______________________________________________________ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> <http://psf.upfronthosting.co.za/roundup/meta/issue655> _______________________________________________________ _______________________________________________ Tracker-discuss mailing list Tracker-discuss@python.org https://mail.python.org/mailman/listinfo/tracker-discuss Code of Conduct: https://www.python.org/psf/codeofconduct/
