On Fri, Sep 12, 2008 at 1:50 PM, Jonathan Vanasco <[EMAIL PROTECTED]> wrote: > > i was just talking about open source projects in general... > > a lot of people seem to be leaving subversion for git, or mercurial, > or other more distributed apps, and only syncing to the main svn repo > on a major release
Pylons has moved to Mercurial for Pylons, Routes, WebHelpers, and Ben's other projects. Several other Python packages have also moved to Mercurial because it's really convenient to commit to your local repository, share a tentative patch with somebody for testing, and then push it to the main repository if it's good. The ability to clone repositories during development is also useful; e.g., to test a feature/refactoring which may turn out to be a dead end. I have stayed away from git because Mercurial is Python, its command syntax is modeled after Subversion, while git is written in C and has a reputation for being uebergeek/hard to use. I don't know of any Python projects using git. In the Pylons repositories, people do check in minor changes just like they do in Subversion. When enough changes accumulate or the BDFL considers one of them is critical, a release is cut. But note that some packages have multiple repositories: https://www.knowledgetap.com/hg/ - pylons-0.9.6 : stable bugfix branch - pylons-1.0 : experimental 1.0 branch without deprecated/Python 2.3 support - pylons-dev : development branch (future 0.9.7, now at 0.9.7rc1) - routes : Routes 1.x stable and incremental development branch - routes2-dev : Routes 2 development branch (not yet usable) -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
