Re: python-django_1.8.18-1~bpo8+1_amd64.changes REJECTED
Thorsten Glaser <t.glaser@tarent.de> writes:
> How, by the way, is the upgrade from jessie to stretch handled?
> If this makes users lose data (without using the 1.8 packages)
> that’s probably an RC bug.
Django is just a Python library. Django itself has no data or
configuration. Upgrading/Downgrading it will not affect data in anyway.
It is the applications that use Django that may have to handle data
migrations. An version of an application that supports a newer version
of Django will typically be a newer version that could have database
changes.
This is typically handled with Django DB migrations. There should not be
any problems migrating from one upstream version to new version (if they
have done their job correctly), the migrations keep track of what needs
to happen automatically.
Having an intermediate step between Jessie and Stretch does not change
this in anyway. You will still end up running exactly the same
migrations by the time you install the Stretch version.
There might be configuration files that also need to be updated,
depending on the application. Not getting this right shouldn't cause any
data loss however.
--
Brian May <bam@debian.org>
Reply to: