-
Notifications
You must be signed in to change notification settings - Fork 122
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
Separate releasing/semver for provider and consumer #1216
Comments
Just tried some things out and it'd be better to slightly alter the release paradigm to look like |
I might have missed it, but should there also be an ADR for this to supercede #897? It might be worth it to get a better summary of benefits/costs associated with this, and to get the context collected in one place. |
I can convert the comment mentioned in this issue to an ADR if you'd like? This topic got to a point that it has been talked about all year (too much discussion imo) and never solved, so I skipped ADR :) |
I think that comment could almost verbatim become an ADR, yes! |
Sounds good 👍 #1229 |
Problem
We're going to ditch the idea of "go.mod split" in favor of keeping one go.mod and separating releasing/semver for consumer and provider with tags. See #801 (comment)
Closing criteria
Problem details
The text was updated successfully, but these errors were encountered: