Comment 15 for bug 264191

I am, probably along with others, concerned with what happens to 0.96 code that has completely depreciated in 1.0. Don't get me wrong, I want 1.0 to be in hardy-backports. Can we make python-django-0.96 and python-django-1.0 packages with a python-django meta-package pointing to the latest? I'd love to see that in hardy-backports. There's my wishlist.

Django 1.0 is easy enough to install and get working, we can all probably agree to that, however certain global scripts may behave or be named differently for an Ubuntu package user than they would a source user making less unified and hard to automate certain things.

So, my wishlist is probably not justified since it will force existing LTS users that subscribe to backports to immediately rewind to python-djano-0.96 when an upgrade suddenly breaks then subsequently fubar their database somehow. I've not been impressed in the past when similar things have happened to me, even though it only rarely happens.

Looking forward to information on how this will turn out.