On 7/11/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > The best thing to do is host your changes remotely. That way there's > no implicit assumptions about if and when it'll get merged into > Django. >
Hi, Jacob. I'll mention Bazaar, too. My experience with it has been very pleasant. I get a copy of Django from the official SVN, create a bzr repo off that SVN version as is (.svn files and all). I then use bzr to track my changes, which still allows me to SVN up. Merging is basically just an svn up away unless I touch a file that has also been updated, in which case I can use bzr to see what came from me instead of via SVN. The UI for bzr is nearly identical to svn, so svn users should be able to use it with little learning curve. For example: mkdir repos cd repos bzr init svn co http://code.djangoproject.com/svn/django/trunk/ django_trunk bzr add django_trunk bzr commit Then you can bzr branch from there to have as many branches as needed. Also, it might be worth the project's time to pick a distributed VCS and host mirrors on djangoproject.com. It would allow core devs to pull patches in easier, I imagine. I certainly understand if you don't want that overhead, but we're doing something similar for Samba and it hasn't been too painful at all. Cheers, deryck -- Deryck Hodge Lead Developer, Product Development Washington Post.Newsweek Interactive Samba Team --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
