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

Consider using Semantic Releases and Conventional Commits #302

Open
xavez opened this issue Aug 5, 2019 · 3 comments
Open

Consider using Semantic Releases and Conventional Commits #302

xavez opened this issue Aug 5, 2019 · 3 comments

Comments

@xavez
Copy link
Contributor

xavez commented Aug 5, 2019

@Wolfr
Copy link
Contributor

Wolfr commented Aug 16, 2019

We can consider it, but these types of things only make sense if there is activity on the repo ;)

@Wolfr
Copy link
Contributor

Wolfr commented Nov 5, 2020

We seem to be moving towards a release system, where a version is defined in the minor part (major.minor.patch) still needs special care and could be considered breaking.

So in its current state, for example between Bedrock 1.20 and Bedrock 1.24 there are big internal changes. We could have technically called Bedrock 1.24 "Bedrock 1 2.0" but I think that would cause a lot of confusion (with Bedrock 2 also being a concept).

This is not using semantic versioning correctly (not at all), but I see no way to change this now without creating a lot of unnecessary problems.

@Wolfr
Copy link
Contributor

Wolfr commented Jul 19, 2021

I never read the explanation about Conventional Commits, interesting.

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