Ilias Lazaridis wrote: > After reviewing the relevant source code base a little, I have started > with the implementation of the schema evolution skeleton (which will > contain a functional "Add Field" support). > > http://case.lazaridis.com/multi/wiki/DjangoSchemaEvolution > > With a very small assistance from the team (mostly subjecting constructs > and of course review of resulting code), I estimate to have a working > solution within 3 days. > > My questions to the team is: > > Can I have a branch / or sandbox location for this (within the django > SVN), or do I have to setup an own svn? ...
It would be nice if I could have an answer on this, thus I can avoid redundant effort. - The simple "ADD FIELD" functionality is ready (draft version, but functional). To simplify things, I could provide several patches. * 1 patch which decouples some existent functionality into a seperate function * 1 patch which adds some function * 1 patch which refactors an existent function * 1 patch which enlinks the "ADD FIELD" evolution into the syncdb command But working with patches is terribly inconvenient. I prefere to make incremental check-in's, thus the development is trackable for other developers. It would be nice, if a branch location could be opened, something like "evolution-draft". . -- http://lazaridis.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
