mirror of
git://git.yoctoproject.org/layerindex-web.git
synced 2025-07-19 20:59:01 +02:00
7606664eeb
RecipeUpstreamHistory was not linked to the layer it was produced from, which meant that it wasn't easy to query for a different maintenance plan (i.e. a different layer) and thus the maintenance plan selection on the recipe list didn't really work. Add a link field, populate it in a migration and then make it required. We had added a link earlier from RecipeMaintainerHistory to LayerBranch but it was optional; for the same reasons we now populate it and make it required. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| 0001_initial.py | ||
| 0002_maintenanceplan.py | ||
| 0003_release_plan.py | ||
| 0004_maint_plan_default.py | ||
| 0005_release_plan_nonnull.py | ||
| 0006_maintplan_email.py | ||
| 0007_python23.py | ||
| 0008_upgrade_info.py | ||
| 0009_rmh_layerbranch.py | ||
| 0010_recipemaintenancelink.py | ||
| 0011_release_name_unique.py | ||
| 0012_reup_layerbranch_field.py | ||
| 0013_reup_layerbranch_populate.py | ||
| 0014_reup_layerbranch_nonnull.py | ||
| 0015_rmh_layerbranch_populate.py | ||
| 0016_rmh_layerbranch_nonnull.py | ||