Russ, Can I suggest doing it the other way round in this case. I believe that the multiple-db-support branch has only a small user base and I haven't had time to properly test all aspects of the merge, I think it might make it easier for others to test if they can just svn up. There are some aspects of the branch that still need work and I think that most people who are using it recognize this. Also as Carole has expressed an interest in contributing and also SVK, it would be beneficial to her (and any others) to be able to grab a local copy of the branch which she can keep in source control as she adds bits to it.
What do you think? Ben On 08/06/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote: > > > On 6/8/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > It would be nice if someone might tell either myself or Ben, how we > > would go about getting the merged code committed, once it's been > > completed and tested.... or do we just submit it as a patch or > > something on the wiki page for this branch? > > Initially, I would suggest submitting as a patch. If there isn't > already a ticket for the multi-db feature, open one, and keep the > patch up to date. > > Once you demonstrate that you're (1) capable of doing the work, and > (2) are in this for the long haul, we can get you an SVN login for the > branch. > > Yours, > Russ Magee %-) > > > > -- Regards, Ben Ford [EMAIL PROTECTED] +628111880346 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
