I agree that we should move to hg, the posts about it are becoming antagonistic and unhelpful. So let's back up a bit.
The main issue right now is that there are still changes with proposed fixes in the issue tracker, and they have not been applied. There are also a bunch of fixes in the 1.2dev branch which could conceivably be back-ported. Cleaning those up is more of an immediate cleanup task than a major effort. It needs to be completed before we can change the system. If we start changing the system, we will be occupied with that instead of with fixing bugs and cleaning up the issue tracker. When the dust settles on the 1.1 branch (I would estimate that happening about two months from now), then I would seriously recommend a move to hg, leaving 1.1 on svn or just importing its history. Although we are "only adding 2 or 3 committers," that is still at least a 100% increase, and the committers will likely be working on unrelated tasks most of the time, with occasional bouts of collaboration or specific bug fixes. If we have a system which allows them to keep separate branches for specific new features and leave the 1.2 branch to bug fixes, then we will no longer have the problem we have right now, which is that some bugs are fixed in 1.2dev that should have been fixed in 1.1, but weren't back-ported due to architectural changes that change the nature of the bug fix. When a new feature is baked enough to merge in, we can do that without having worried about keeping up with bug fixes to the old version the whole time. In addition, I believe hg's patch system is easier to use than svn's, and if we keep our local repos on bitbucket as well, it will be easier to browse changes made by another developer and determine whether a pull would be appropriate. Until then, we really need to focus on cleaning up the existing issues to make any future transitions easier, and to push out the first "community release" which should contain the fixes we are making right now. And for those of you who haven't tried hg or git, I really think you should at least read a couple of pages of tutorials for one or the other. At least do due diligence on it. I used svn for a long time, but switched because of issues very similar to the ones we are having now. DVCSes solve problems you didn't even know you had. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
