-
-
Notifications
You must be signed in to change notification settings - Fork 322
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
Status Of Project #288
Comments
There will almost certainly be some more breaking changes. It's hard to estimate. We hope that we're starting to stabilise, but the last release was pretty major. Expecting a certain amount of fallout. |
That said, changes will be documented in |
The API isn't stable yet (we're not 1.0!), but the basic ideas are mostly in place, especially for the API client ( As @clux mentioned, |
That said, it's a good discussion to raise. API breakage is one thing, but #286 shows that it might be worth starting to let releases bake for a bit longer. |
ok thanks I think I will use this anyway as I'm a big fan of rust and this library and just not upgrade as frequently as I generally do. I don't really require anything too fancy for what I'm doing. Just doing basic mariadb and cyrusimap operators that we use internally. Currently I'm using helm charts that I did. I find a lot of the prebuilt go operators are overkill for my needs. |
Awesome. I'll close this for now. We'll revisit stability guarantees and actually define what this entails once 1.0.0 is right on the horizon. Edit: #508 |
Hi,
I have used this library in the past for testing purposes. I would like to now build an operator that's ready for production but I am wondering how stable this project is and how many more breaking changes there will be until there is a stable release. If not I will have to use one of the go options but I prefer to use rust if possible.
The text was updated successfully, but these errors were encountered: