Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-update SECURITY.md #46

Open
madolson opened this issue Mar 27, 2024 · 4 comments
Open

Re-update SECURITY.md #46

madolson opened this issue Mar 27, 2024 · 4 comments
Labels
major-decision-pending Major decision pending by TSC team

Comments

@madolson
Copy link
Member

We need to include our responsible disclosure agreement as well as our maintenance plan. I think this is something worth figuring out now. I would like to suggest we introduce a policy of maintaining all versions for at least 3 years. This will be a bit different from Redis, as we had some weird number of major/minor thing. The time will start when the release is first GA'd, so we will commit to maintaining our compatibility fork for 3 years.

@madolson madolson added the major-decision-pending Major decision pending by TSC team label Mar 27, 2024
@PenguRin
Copy link

That would be appealing for companies aswell and them potentially selecting and contributing primarily to this fork.

@Varpie
Copy link

Varpie commented Mar 28, 2024

After the name change to Valkey, I can see that the current SECURITY.md still uses the name PlaceholderKV.

@zuiderkwast
Copy link
Contributor

Fixed?

@madolson
Copy link
Member Author

I would like to suggest we introduce a policy of maintaining all versions for at least 3 years.

I was going to keep this open until this line was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
major-decision-pending Major decision pending by TSC team
Projects
None yet
Development

No branches or pull requests

4 participants