Conversation
Signed-off-by: danehans <daneyonhansen@gmail.com>
Alice-Lilith
left a comment
There was a problem hiding this comment.
Looks good to me but I think we need to define what "supported" means for a release? I assume security vulnerabilities, but we should have a police about bugfixes and what kind of security patches (high severity / all) would require us to backport fixes to an old release.
|
@AliceProxy thanks for the review and feedback. IMHO "supported" means that we'll answer questions, reproduce, fix, etc. reported issues. This Slack thread is a good example of what "support" means. I specifically did not include patch or security releases under the |
Codecov Report
@@ Coverage Diff @@
## main #665 +/- ##
==========================================
+ Coverage 62.82% 62.92% +0.10%
==========================================
Files 47 47
Lines 5762 5762
==========================================
+ Hits 3620 3626 +6
+ Misses 1912 1904 -8
- Partials 230 232 +2
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
|
|
||
| ## Release Schedule | ||
|
|
||
| In order to align with the Envoy Proxy [release schedule][], Envoy Gateway releases are produced on a fixed schedule |
There was a problem hiding this comment.
WDYT about moving the target release date back another ~week to the last day of each month? That would give us two weeks between Envoy's target date and EG's, which would make it less likely that an Envoy release slip would affect EG's timeline.
There was a problem hiding this comment.
Not a strong opinion, but: That sounds like a good idea to me.
skriss
left a comment
There was a problem hiding this comment.
LGTM, one suggestion on timelines but fine with whatever the group wants to do.
Adds a doc that provides EG release details.
Fixes #663
Signed-off-by: danehans daneyonhansen@gmail.com