Hey all — Pinax currently ships Django 1.0.4. This has worked well for us and I still think 1.0.X is a solid version of Django. However, Django has moved on and 1.0.X is now only taking security related bug fixes and will lose complete support as of the Django 1.2 release. Django 1.2 is looking to be a big forward movement in the Django world and we definitely should not fall behind. The timeline for both Pinax 0.9 and Django 1.2 are roughly similar in that I'd like to see the final release sometime shortly after Django 1.2 at the latest.
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. 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. 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. Brian Rosner http://oebfare.com http://twitter.com/brosner -- 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.
