MIRRORS/layerindex-web
1
0
Fork 0
mirror of git://git.yoctoproject.org/layerindex-web.git synced 2025-07-19 20:59:01 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity

TODO: add RRS items

Browse Source 
Add some stuff still left to be done after the merging.

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
This commit is contained in:
Paul Eggleton 2018-04-19 00:55:27 +12:00
parent 32617fc366
commit fd0079d5c9
2 changed files with 20 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
TODO
View File

@ -10,6 +10,7 @@ TODO:
Bugs Bugs
* Duplication of first maintainer when editing to add a second? * Duplication of first maintainer when editing to add a second?
* GitPython sometimes reports renamed files as type M but we don't handle that properly e.g. OE-Core 59285b324f6d9ed270b0bef209ef5da22a620a83 086308aa2a5e332de6f00ed397c4a55d132f158f
Other Other
* Full-text search on layer contents * Full-text search on layer contents
@ -35,3 +36,22 @@ Other
* Click on OE-Classic graph element to go to query? * Click on OE-Classic graph element to go to query?
* Use bar instead of pie graphs for OE-Classic statistics * Use bar instead of pie graphs for OE-Classic statistics
* Ability for reviewers to comment before publishing a layer? * 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
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)
* Link to other distro comparisons?
* Link to other distro package info pages?

4
TODO.rrs
View File

@ -1,4 +0,0 @@
TODO:
Bugs:
- gcc-source recipe has his own recipes per version. This is triggered in gcc-source.inc