Just a couple of minor things to mention:
- In cases like below, is the version of any value for us later? if so,
can we keep it like other extra information that we keep in square
brackets (like `[<date>]`)?
```
-kinetic_linux: pending (5.19.0-47.49)
+kinetic_linux: ignored (end of life, was pending)
```
I also think cases like below are in a grey area and a bit confusing:
```
-jammy_linux-riscv: ignored (was needs-triage now end-of-life)
+jammy_linux-riscv: ignored (end of life, was needs-triage)
```
mostly in CVEs we use `ignored (end of life, was needs-triage)` as in
EOL of the release, however, in this case (and other similar cases) it's
not about `jammy`! and since they have different meanings, I believe
their comment could/should be different too.
Thanks for the PR David.
Just a couple of minor things to mention:
- In cases like below, is the version of any value for us later? if so,
can we keep it like other extra information that we keep in square
brackets (like `[<date>]`)?
```
-kinetic_linux: pending (5.19.0-47.49)
+kinetic_linux: ignored (end of life, was pending)
```
I also think cases like below are in a grey area and a bit confusing:
```
-jammy_linux-riscv: ignored (was needs-triage now end-of-life)
+jammy_linux-riscv: ignored (end of life, was needs-triage)
```
mostly in CVEs we use `ignored (end of life, was needs-triage)` as in
EOL of the release, however, in this case (and other similar cases) it's
not about `jammy`! and since they have different meanings, I believe
their comment could/should be different too.
Other than these, it looks good to me. Thanks :)