On 11 jul, 16:12, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
wrote:
> On 7/11/07, Ben Ford <[EMAIL PROTECTED]> wrote:
>
> > None as yet, I'm really keen to get it back into the svn repo, but I think
> > the people concerned are busy with other things at the moment.
>
> I've said this a couple times, but I guess it's been missed:
>
> We're moving away from giving branch access since it's not really
> worked so well in the past. It simply doesn't scale very well --
> there's only one of me, and I'm quite bad about remembering to get
> people access -- and people assume that SVN branches are on track to
> be merged, which may not be the case.
Maybe I am missing something here. I understand why you would be
reluctant to open up new branches, but I don't understand why this
would justify keeping a branch in a 7 month old status if someone has
done the (big) effort of bringing it more or less up to date. I don't
care who commits the changes to the branch, but my idea is that since
it is there and the work has been done, it might just as well go in.
To me it seems the best way to get some new interest for the branch
and to get it moving again.
I think this is especially interesting for an important one as multi-
db. This feature really is a life-saver for those of us who have to
use existing data, but still want to have all the niceties that
working with django brings us.
>
> 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.
Isn't that what the wiki is for: to give a clear idea about the status
of a branch?
>
> Probably the best way to host an "unofficial" branch would be by using
> Tom's Mercurial mirror of Django trunk:http://hg.korpios.com/django.trunk/.
>
> Jacob
Groetjes uit België,
Koen
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
