Skip to content

Decide how to handle "wrong-year" advisories #14

@gastamper

Description

@gastamper

Examples:
CESA-2019:2003 (April 2020 CR)
CEBA-2018:0748 (October 2020 CR)

Worth bothering with? If so, how? Would have to undo neighbor-year checking of cache, which otherwise makes things a lot faster.

Also these advisories don't show in online mode since they are in the "incorrect" year (2018 in 2020). Only option would be to iterate over other years when no hits found in current & adjacent year, and that seems messy and spammy.

Metadata

Metadata

Assignees

Labels

questionFurther information is requested

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions