Paul Eggleton 7606664eeb rrs: link maintenance/upstream history to layerbranch ... 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>		2018-05-04 23:57:53 +12:00
..
migrations	rrs: link maintenance/upstream history to layerbranch	2018-05-04 23:57:53 +12:00
static	rrs/base_toplevel.html: Navbar redesign	2018-05-04 23:57:52 +12:00
tools	rrs: link maintenance/upstream history to layerbranch	2018-05-04 23:57:53 +12:00
__init__.py	rrs: show full name in admin	2018-05-04 23:57:52 +12:00
admin.py	rrs: link maintenance/upstream history to layerbranch	2018-05-04 23:57:53 +12:00
apps.py	rrs: show full name in admin	2018-05-04 23:57:52 +12:00
context_processors.py	rrs: Add application	2018-05-04 23:57:51 +12:00
models.py	rrs: link maintenance/upstream history to layerbranch	2018-05-04 23:57:53 +12:00
urls.py	rrs: add charts page	2018-05-04 23:57:53 +12:00
views.py	rrs: link maintenance/upstream history to layerbranch	2018-05-04 23:57:53 +12:00
wsgi.py	rrs: Add wsgi file for serve with gunicorn	2018-05-04 23:57:52 +12:00