MIRRORS/layerindex-web
1
0
Fork 0
mirror of git://git.yoctoproject.org/layerindex-web.git synced 2025-07-19 11:59:01 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity
paule/docker-compose
layerindex-web/TODO
Paul Eggleton db08df4a86 Improve collection/display of LayerUpdate records 
Make layerupdate collection slightly more reliable and make it easier
to see when updates have actually been captured:

* Split layerbranch into separate layer and branch fields, since there
  may not be a layerbranch in existence but we might want to log an
  error relating to the branch and layer.
* Show all layerupdates on the update detail page, not just those with
  log messages
* Record before and after revisions and show these in the update detail
  and layerupdate detail (with links)
* Record return code of update_layer process
* Highlight layer updates with a non-zero return code, errors or
  warnings in the output on the update detail page
* Show duration on the layerupdate detail page

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2018-08-14 15:07:34 +02:00

3.5 KiB
Raw Permalink Blame History

TODO:

Bugs

  • Duplication of first maintainer when editing to add a second?
  • meta-tizen gives PathError in initial info gathering step
  • If a layer has not yet been fetched and it can't be then it still tries to parse it and blows up when querying git revision
  • meta-debian seems to be prompting for github credentials during recipe parsing?
  • Remote patches in SRC_URI trigger errors
  • We're wasting time gathering layer info at the start for layers that have not changed
  • import_layer on OE-Core then a layer that depends on core does not work

Features

  • Auto-detect dead layers and visually mark
    • Formal deprecation process?
    • Email people when status will change?
  • Show other branches when looking at layer - maybe change the focus to show all layers rather than layers at a selected branch?
  • Allow users to make a comment sent to admins/maintainers?
  • Marking for recipes with ptest enabled
  • Make it easy to update people's email addresses
  • Prevent selection of "Base" layer type for layer unless you have admin access (or layer is already of that type)
  • Use proper model to store inherits
  • Make dependency and inherits list items into search links
  • Full-text search on layer contents
  • Handle layers that have branch (e.g. master) that is empty
  • Add log in again link to logout page.
  • Collect interesting news (layer add/delete, recipe add/delete/upgrade) and provide RSS feed
  • "Split layer" tool for when a layer is split out of another? (Saves time adding records everywhere)
  • All-branch search/results so you can see version availability of recipes in all branches at once?
  • Show OE-Classic search results in OE-Core search? (with appropriate disclaimers)
  • Display no-results found message when search does not return any results in layer search
  • Way to notify in search results when user searches for something that has been renamed / replaced / deprecated?
  • Show an alert on recipe page when recipe is outside of layer's BBFILES
  • Document macros for URL fields
  • Show layer type in layer detail?
  • Usage links in list page?
  • Subdirs in list page?
  • Add comparison to duplicates page
  • Create simple script to check for unlisted layer subdirectories in all repos
  • Auto-detect more values from github pages?
  • Ability for submitters to get email notification about publication?
  • Update script could send warnings when parsing layers to maintainers? (optional)
  • Click on OE-Classic graph element to go to query?
  • Use bar instead of pie graphs for OE-Classic statistics
  • Ability for reviewers to comment before publishing a layer?
  • Show a note at the top of the layer edit form if there's a validation error
  • Show count in duplicates page
  • Search on layer selection dialogs

RRS:

  • Ability for maintainers to create their own maintenance plans
  • Use gitpython instead of shelling out to git to get commits?
  • "Last updated" date doesn't show without upstream status data ?
  • Try to replace raw SQL?
  • Why are we scanning through recipe files? For some scripts, surely just gather Recipe records for the layer?
  • Collecting/storing data for every maintainer for every change to the maintainers.inc file is wasteful
  • Clean up rrs/tools/common.py
  • Handle MAINTAINERS file?
  • Need to handle eventual move of RECIPE_MAINTAINER to recipes?
  • Change layer update structure so that RRS stuff can plug into it rather than having separate scripts
  • We only list recipes that have upgrade info (an earlier design decision) - should we list all?
  • Replace "All" with "(all)" and "No maintainer" with "(no maintainer)"?
  • Link to upstream changelogs? (will require per-recipe variable)