Figure out a lifecycle strategy for deb publishing
Open
- Dominant language
- Starlark
- Stars
- 1
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
atm once something gets published in the apt repository it will stay there
this means that unsupported and potentially vulnerable versions of envoy will continue to be published
we probably either want to stop publishing them and remove or at least push unsupported versions into a separated apt repo or mark them with separate components
this is a follow up of conversation here https://github.com/envoyproxy/envoy/issues/16867
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.