Create default SECURITY.md #5
Conversation
|
Any interest in this one? |
|
Actually we have a policy in the project to support the previous major version up to 2 years after the release of the current major (to let community upgrade to the current major), e.g. we have been supporting Vert.x 3.9.x releases until 6 months ago, currently 3.9.x is not officially supported anymore since Vert.x 4.0.0 has been released more than 2 years ago. Can we update the document to mention ? @mbarbero |
Signed-off-by: Mikaël Barbero <mikael.barbero@eclipse-foundation.org>
Done ✅ |
|
Gentle ping. Thanks! |
|
Is there anything in the proposed policy that you would like to see edited before merging it? Thanks! |
|
@mbarbero it looks good to me, if I think about something relevant I'll open an issue, sorry for the delay |
It's still only approved, not merged :) |
|
shall I merge it ? |
If you're ok with the content, yes, please. I'm not a committer and don't have write permission on your repositories :) |
|
@mbarbero oh right I didn't realise this |
Default security policy based on Eclipse Foundation's recommendations https://github.com/eclipse-csi/security-handbook/blob/main/templates/SECURITY.md Similar to eclipse-vertx/.github#5
Default security policy from Eclipse Foundation's recommendations https://gitlab.eclipse.org/security/best-practices/