Paul Eggleton 1f037470fb rrs: releases should be unique by plan and name, not just name ... I missed changing this constraint when adding the plan field. We want to be able to have the same named release on another plan. 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
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