| 1 |
On 28/12/19 11:05, Kent Fredric wrote: |
| 2 |
> On Sat, 28 Dec 2019 10:35:09 +0100 |
| 3 |
> Fabian Groffen <grobian@g.o> wrote: |
| 4 |
> |
| 5 |
>> Hmmm, interested to hear what kind of things you're thinking about here. |
| 6 |
> A lot of the "Work" of filing a keyword request is modelling all the |
| 7 |
> consequential keywordings that have to take place. |
| 8 |
> |
| 9 |
> If there was say, a web based UI, that: |
| 10 |
> |
| 11 |
> - Automatically determined which packages are ready for stabilization |
| 12 |
> due to all their dependencies already being stable (and maybe with |
| 13 |
> automatic cooldown-from-testing detection ) |
| 14 |
> |
| 15 |
> - Automatically determined which packages can be keyworded without |
| 16 |
> additional work due to all their dependencies being keyworded |
| 17 |
<snip> |
| 18 |
|
| 19 |
I know I'm gonna be shot down in flames, because $heresy, but here is where |
| 20 |
a package 'database' would actually work quite well, because you can |
| 21 |
trivially create a query that pulls this data out, and sorts it by package |
| 22 |
category or maintainer or whatever you like .. |
| 23 |
|
| 24 |
Ok, let the flamewars begin ... |
Archives