-
Notifications
You must be signed in to change notification settings - Fork 469
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
Make decision on tagging strategy #10559
Comments
Quick update after discussing this more with maintainers: there's zero appetite for v0.x (for several, valid reasons), and there was merit to both the 1.x and 2.x options. Ultimately, we're leaning towards a 2.x version scheme given 1.) the reduced project scope and goals, 2.) moving towards a vendor neutral approach (e.g. removing solo.io references in GVKs) 3.) expected breaking changes in both API and behavior as we finalize the transition from the solo-io organization to this new organization. |
We will move forward with 2.x |
#10607 will track the implementation needed for this |
…as being unset (kgateway-dev#10559) Signed-off-by: Shashank Ram <[email protected]>
We need to get consensus on the right tagging strategy for this project going forward:
Psuedoblocks #10441.
The text was updated successfully, but these errors were encountered: