Hello, My 2 cents:
I think that this discussion has moved from the important topic. I don't think it is important right now which VCS we keep using (it is just a tool), the important thing right now, is how pyglet is going to keep alive (maintenance, bug fixing, improvements, port to python 3, etc). I agree we Tristam, we must start by merging back maintenance branch with trunk. regards, Lucas On Aug 15, 2:44 am, Florian Bösch <[email protected]> wrote: > On Aug 15, 1:44 am, Francesco Pischedda > > <[email protected]> wrote: > > well, private branch are the common and required features of dvcs-es and I > > agree > > Using mercurial you can either: > 1) create a branch (named or unnamed) and continue developing it, > merging changes in from the tip as you go, when you commit this head > will be visible. > 2) create a clone of the repository where you work on the changes, > pull and merge from the upstream repository and when you're done > commit, no new branch will be created for others. > 3) create a Queue which gets re-applied after you've pulled from > upstream repositories, therefore creating a local "view" of what you > do, you can add/drop the whole queue at any time (particularly handy > if somebody wants to try out your changes with his own non published > clone) > > I really don't see what's the handwaving over "ohno don't change the > VCS". It's a nobrainer. mercurial is as easy to use as SVN (it allows > you to ignore most of the fancy features), it is a hell of a lot > faster doing a full checkout, it's a hell of a lot faster displaying > diffs, it's a *lot* more flexible, the migration to it has been done > and closed... > > Now you can cry all you want how this is a solution in search of a > problem, or how it's all to risky or you simply hate DVCSes, at the > end of the day, Mercurial *is* better then SVN in every respect. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
