On 2006-12-17, Victor Ng <[EMAIL PROTECTED]> wrote: > > Test coverage is ~44 test cases. There are currently 2 known problems > in the code from a 'correctness' standpoint, and there is a ton of > refactoring that needs to be done before it should be considered for > merging into the trunk.
I see, 44 test cases sound like a good start. > The code is *messy*. Writing schema evolution went hand in hand with > me learning how Django's schema generation worked. [...] > If someone wants to open up commit access on the django branch for > schema evo, I'll be happy to bring the schema evo code up to date with > the trunk. > > I *do* need help in tidying it up to get it merged back to trunk > though. I'm hard pressed for time right now and I could use some > help. It sounds like your code has potential to be a full fledged alternative implementation. I've never looked at the django internals, but I might be able to help nevertheless. I will have some time starting about 10 days from now. At this point it would be a question of where I spend my time - testing the existing branch code or helping test and/or clean up and integrate your code. The fact that you've already tried the existing schema evolution branch and spent this much effort so far on an alternative implementation certainly makes me lean towards your code. But it would be nice from a logistical point of view if we could have access it to it from a repository somewhere. Steve --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
