layerindex-web/rrs/migrations
Paul Eggleton ba27f9fee0 rrs_upgrade_history.py: enable to work across python2/3 versions
If you want to go back and get history for the earlier releases (krogoth
and previous) then we need to be able to support both python 2 and 3,
which practically means we need the same split for this script as we
have for the main layer index update script.

The catch here is that since we are going back and following the history
of changes forward, we basically need to use the same version of bitbake
that was current at that time. This works except for around the
transition between python 2 to 3 where the metadata lagged behind a bit,
so we need to take that into account. In order to keep things generic we
have a date field on the maintenance plan layer branch that specifies
the date in the metadata where we should switch over to python 3, and
then link to PythonEnvironment records that should be used for python 2
and 3 respectively.

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2018-05-04 23:57:53 +12:00
..
__init__.py rrs: add initial migration 2018-05-04 23:57:52 +12:00
0001_initial.py rrs: replace fixtures with initial data migration 2018-05-04 23:57:53 +12:00
0002_maintenanceplan.py rrs: add maintenance plans 2018-05-04 23:57:52 +12:00
0003_release_plan.py rrs: add Release link to MaintenancePlan 2018-05-04 23:57:52 +12:00
0004_maint_plan_default.py rrs: add Release link to MaintenancePlan 2018-05-04 23:57:52 +12:00
0005_release_plan_nonnull.py rrs: add Release link to MaintenancePlan 2018-05-04 23:57:52 +12:00
0006_maintplan_email.py rrs/models: add fields for more flexible email handling 2018-05-04 23:57:53 +12:00
0007_python23.py rrs_upgrade_history.py: enable to work across python2/3 versions 2018-05-04 23:57:53 +12:00