-
Notifications
You must be signed in to change notification settings - Fork 38
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
Question regarding Brupop's Support Policy #548
Comments
Hey, thanks for raising this question. We should probably look at providing guidance around this in the README. Brupop follows semver, so changes introduced in minor versions will not introduce breaking or backwards-incompatible changes. Only the latest minor version receives patches for security issues. Given this policy, I'd recommend always using the latest version of Brupop available. |
@cbgbt Thank you! This is very helpful 😃 If I may, I'd just like to reiterate your guidance via an example so that I know I've understood it correctly.
Please let me know if my understanding is correct. And I agree having the support policy be a part of the README will be very valuable to other users who might be after the same information :) I'll be very happy to make a PR if you'd like me to. |
@stmcginnis @cbgbt I've created the PR: #550 :) |
Image I'm using:
N/A
Issue or Feature Request:
This isn't an issue or a feature request, rather a question:
What is the support policy for Brupop in terms of which versions are supported at a given time and which version(s) are recommended to be installed on a prod cluster? I went through the documentation but could not find this information.
I would be grateful if someone could please guide me on this ^_^
The text was updated successfully, but these errors were encountered: