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 some more items

Browse Source 
There's always more work to do...

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
This commit is contained in:
Paul Eggleton 2018-09-06 09:31:35 +12:00
parent abe470e618
commit ac32edb5bd
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
TODO
View File

@ -1,6 +1,8 @@
TODO: TODO:
Bugs Bugs
* Directory where bitbake-cookerdaemon.log is placed isn't right (meta dir)
* bitbake-cookerdaemon.log should be cleared out every time
* Duplication of first maintainer when editing to add a second? * Duplication of first maintainer when editing to add a second?
* Remote patches in SRC_URI trigger errors * Remote patches in SRC_URI trigger errors
* We're wasting time gathering layer info at the start for layers that have not changed * We're wasting time gathering layer info at the start for layers that have not changed
@ -41,9 +43,12 @@ Features
* Show a note at the top of the layer edit form if there's a validation error * Show a note at the top of the layer edit form if there's a validation error
* Show count in duplicates page * Show count in duplicates page
* Search on layer selection dialogs * Search on layer selection dialogs
* Close buttons on site-wide messages (using cookie to keep closed ?)
RRS: RRS:
* gcc recipes showing up as not updated (we have maintainer links, but not upstream links - gcc-source-${PV} is the actual recipe)
* Make it easier to create release with milestones
* Ability for maintainers to create their own maintenance plans * Ability for maintainers to create their own maintenance plans
* Use gitpython instead of shelling out to git to get commits? * Use gitpython instead of shelling out to git to get commits?
* "Last updated" date doesn't show without upstream status data ? * "Last updated" date doesn't show without upstream status data ?
@ -57,3 +62,7 @@ RRS:
* We only list recipes that have upgrade info (an earlier design decision) - should we list all? * 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)"? * Replace "All" with "(all)" and "No maintainer" with "(no maintainer)"?
* Link to upstream changelogs? (will require per-recipe variable) * Link to upstream changelogs? (will require per-recipe variable)
* Tie into AUH? i.e. display last sent auto recipe upgrade status on recipe detail, add overall AUH status
* Display outstanding patches on recipe detail? (keyword search from patchwork?)
* Record update logs for all scripts
* Sorting by patch count should sort numerically