> My proposal is that we move to running Django 1.2 trunk in master as soon as > we can. We can do this just as we do with development version of apps. We may > have to tweak the release build process for our needs. Of course any bugs we > find in Django itself will go through the normal Django contribution path. We > will want to dedicate some time to this process since it'd be nice to ensure > any *major* issues are resolved in the beginning. We'll need to update each > project's settings to work properly against 1.2.
+1 I couldn't agree more. > Testing each project and make sure all works nicely. I am already aware that > django-tagging is failing on 1.2. Though honestly I don't mind putting more > effort into another tagging library like django-taggit, but we can reserve > that for another discussion. Indeed, are there any apps we can't contribute to easily to prepare them for 1.2? > I'd recommend we plan a sprint if we all accept this should be the plan of > action. Comments, questions or suggestions are greatly welcome. +1 I'd like to propose a sprint (or more) in February, which is the time between Django 1.2 beta and release candidates according to the roadmap [1]. Best, Jannis 1: http://code.djangoproject.com/wiki/Version1.2Roadmap -- You received this message because you are subscribed to the Google Groups "Pinax Core Development" 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/pinax-core-dev?hl=en.
