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

BREAKING CHANGE label #71

Open
devlinjunker opened this issue Dec 29, 2020 · 2 comments
Open

BREAKING CHANGE label #71

devlinjunker opened this issue Dec 29, 2020 · 2 comments
Labels
build Improvements to the build process feature New Feature question Further information requested

Comments

@devlinjunker
Copy link
Owner

devlinjunker commented Dec 29, 2020

Describe the Improvement:
Add Label that Auto-merges with BREAKING CHANGE footer

  • ideally label appears at bottom of list (start with ~ like wiki?)
  • Include BREAKING CHANGE commits in changelog

Benefits:

  • enables automatic major releases

Drawbacks:

  • do we want to enable automatic major releases? or is it nice to have admin intervention

How to Compare:
Major Releases can be auto-merged

@devlinjunker devlinjunker added question Further information requested build Improvements to the build process feature New Feature labels Dec 29, 2020
@devlinjunker
Copy link
Owner Author

Questions

  • how does the next major release work?
  • Should we have develop-2.0 branch? (Would need to be upmerged from develop while still making 1.x releases)

@devlinjunker
Copy link
Owner Author

devlinjunker commented Dec 31, 2020

Breaking changes:

  • remove score labels?
  • better/proper use of git-mkver

I don’t think this (#71) is

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Improvements to the build process feature New Feature question Further information requested
Projects
None yet
Development

No branches or pull requests

1 participant