On 28/12/06, Steve Hutton <[EMAIL PROTECTED]> wrote:
On 2006-12-22, Victor Ng <[EMAIL PROTECTED]> wrote: > > Hi, sorry for the long delay in replying. Holiday season and work > craziness is getting in the way of writing free software - which is > really the fun part isn't it? ;) :-) > It's a little different, but barely. > > The current codebase emits an SQL file with all the SQL statements to > evolve the database, There's no provision to save the version > anywhere, but that would be simple to do. > > If nobody want's to champion the code, I can volunteer ~3-5 hours a > week to work on this stuff. My own team needs schema evolution in the > long run anyway - so it's well worth my time to make sure this > eventually gets back to trunk. > > I won't be able to do too much until the new year though - so that > said - can somebody open up the schema evolution branch, or better - > open up a new branch from trunk so that we can start hacking away at > this problem? Sounds great to me. Any core devs care to open a new branch for this? Thanks, Steve
From my earlier involvement I know Victor's code is based on the
current schema evolution branch so I think it makes sense for his fixes to be checked into it. Also it would be less confusing for the rest of the django community if there was a single branch, considering that there is atleast one enquiry a week about it. Victor, have you got a ticket open with your patch? It would be worth opening one so that other people could try it out while you are waiting for commit access to be granted. regards matthew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
