Paul Eggleton 254dc0c7db RRS: enable grouping recipe upgrades by license ... Going back in OE-Core recipe upgrade history, we kept GPLv2 and GPLv3 versions of a number of recipes around, so this is the source of quite a few situations where we had multiple versions of recipes with the same recipe name around. Add means of grouping upgrades by license so that we can keep these versions separate in the upgrade history instead of detecting lots of apparent upgrades and downgrades if they are intermingled. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>		2019-11-21 02:51:30 +13: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
0008_upgrade_info.py	rrs_upgrade_history: use date/commit of last recipe upgrade import	2018-05-04 23:57:53 +12:00
0009_rmh_layerbranch.py	rrs_maintainer_history: add --fullreload option	2018-05-04 23:57:53 +12:00
0010_recipemaintenancelink.py	rrs: handle linking maintainership	2018-05-04 23:57:53 +12:00
0011_release_name_unique.py	rrs: releases should be unique by plan and name, not just name	2018-05-04 23:57:53 +12:00
0012_reup_layerbranch_field.py	rrs: link maintenance/upstream history to layerbranch	2018-05-04 23:57:53 +12:00
0013_reup_layerbranch_populate.py	rrs: link maintenance/upstream history to layerbranch	2018-05-04 23:57:53 +12:00
0014_reup_layerbranch_nonnull.py	rrs: link maintenance/upstream history to layerbranch	2018-05-04 23:57:53 +12:00
0015_rmh_layerbranch_populate.py	rrs: link maintenance/upstream history to layerbranch	2018-05-04 23:57:53 +12:00
0016_rmh_layerbranch_nonnull.py	rrs: link maintenance/upstream history to layerbranch	2018-05-04 23:57:53 +12:00
0017_maintenanceplan_maintainer_style.py	rrs: add flag to MaintenancePlan to specify layer-wide maintainers	2018-05-04 23:57:53 +12:00
0018_rmh_unique.py	rrs: fix unique constraint on RecipeMaintainerHistory sha1 field	2018-05-04 23:57:53 +12:00
0019_maintplan_admin_delete_null.py	RRS: add missing migration	2019-05-28 09:57:58 +12:00
0020_recipesymbol_initial.py	RRS: collect history independent of current recipes	2019-11-21 02:27:39 +13:00
0021_recipesymbol_nonnull.py	RRS: collect history independent of current recipes	2019-11-21 02:27:39 +13:00
0022_recipesymbol_finish.py	RRS: collect history independent of current recipes	2019-11-21 02:27:39 +13:00
0023_recipeupgrade_deleted.py	RRS: Add deleted recipe handling	2019-11-21 02:27:39 +13:00
0024_recipeupgrade_downgrade.py	RRS: handle downgrades	2019-11-21 02:27:39 +13:00
0025_recipeupgrade_move.py	RRS: handle recipe moves without overwriting data	2019-11-21 02:27:39 +13:00
0026_recipeupgrade_grouping.py	RRS: support grouping upgrades by version for multi-version recipes	2019-11-21 02:27:39 +13:00
0027_recipeupgrade_prev_version.py	RRS: record previous version	2019-11-21 02:27:39 +13:00
0028_recipeupgrade_srcrev.py	RRS: detect changes in SRCREV as upgrades	2019-11-21 02:51:30 +13:00
0029_rrs_license_group.py	RRS: enable grouping recipe upgrades by license	2019-11-21 02:51:30 +13:00