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

Make decision on tagging strategy #10559

Closed
Tracked by #10441
timflannagan opened this issue Jan 30, 2025 · 3 comments
Closed
Tracked by #10441

Make decision on tagging strategy #10559

timflannagan opened this issue Jan 30, 2025 · 3 comments

Comments

@timflannagan
Copy link
Member

timflannagan commented Jan 30, 2025

We need to get consensus on the right tagging strategy for this project going forward:

  • Start fresh: v0.x
  • Continue with the gloo fork cadence: v1.x
  • Lean into proper semver strategy: v2.x

Psuedoblocks #10441.

@timflannagan
Copy link
Member Author

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.

@lgadban
Copy link
Contributor

lgadban commented Feb 11, 2025

We will move forward with 2.x

@lgadban lgadban reopened this Feb 11, 2025
@lgadban
Copy link
Contributor

lgadban commented Feb 11, 2025

#10607 will track the implementation needed for this

@lgadban lgadban closed this as completed Feb 11, 2025
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

No branches or pull requests

2 participants