On Sat, Feb 5, 2011 at 10:00 AM, Jesus Cea <j...@jcea.es> wrote: > I do agree. I am getting the feeling that (some not small group of) > python core devs are not familiar with mercurial at all. That is a bit > scary, considering the two years migration patch (and counting) and that > to discuss workflow you must know the abilities of the tools... Really > scary :).
Work = CVS, Python = SVN, ??? = Hg. I don't believe you can genuinely learn any VCS until you use it for serious work, and there's simply nothing I work on currently that stresses the abilities of Hg. (The extent of my Hg usage is playing with the commit hooks and devguide repositories on hg.python.org). I've read plenty about it, and have a reasonable idea of how it works, but a lot of the things I've read about the recommended workflows simply don't line up with the way we have historically done things. As I've said, I'm happy to roll with that, but I consider the onus to be on the champions of the Mercurial switchover to document the best workflows they can collectively come up with for the benefit of those of us that are Mercurial novices. What we have with SVN certainly has its problems, but it mostly works and we're used to it. A wildly divergent 2.7 branch, with a 3.3 development branch, a 3.2 maintenance branch, 2.6 and 3.1 security branches and assorted feature branches is going to be plenty to be going on with, even before we get to the question of managing the 3.3 release in mid-to-late 2012. Consider the day of the switchover, when SVN has gone read-only and Hg is opened up for pushes. What should I have checked out on my machine in advance in order to work on: 1. PEPs 2. The dev guide 3. New 3.x features 4. 3.x only bug fixes 5. Bug fixes that also apply to 2.7 6. Security fixes that apply to 3.1/2.6 7. A feature-specific branch I'm happy to be guided by the Hg veterans here, *but the Hg veterans need to be willing to document their advice in a common location and come to consensus on it*. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers
