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

Question regarding Brupop's Support Policy #548

Closed
mooneeb opened this issue Sep 12, 2023 · 4 comments · Fixed by #550
Closed

Question regarding Brupop's Support Policy #548

mooneeb opened this issue Sep 12, 2023 · 4 comments · Fixed by #550

Comments

@mooneeb
Copy link
Contributor

mooneeb commented Sep 12, 2023

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 ^_^

@cbgbt
Copy link
Contributor

cbgbt commented Sep 12, 2023

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.

@mooneeb
Copy link
Contributor Author

mooneeb commented Sep 13, 2023

@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.

Since v1.3.0 is the latest brupop release, v1.3 is considered supported and v1.3.0 (since it is the latest released version) is the one recommended to be installed (if v1.3.1 is released, then v1.3.1 will be recommended)

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
Copy link
Contributor

That's right @mooneeb!

I'll be very happy to make a PR if you'd like me to.

That would be great! If you have a chance to do that, @cbgbt and I will watch out for the PR and make sure it gets reviewed quickly. Thank you!

@mooneeb
Copy link
Contributor Author

mooneeb commented Sep 13, 2023

@stmcginnis @cbgbt I've created the PR: #550 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants