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

Switch to using standard-version (or even semantic-release) #3503

Closed
gkatsev opened this Issue Aug 5, 2016 · 1 comment

Comments

Projects
None yet
1 participant
@gkatsev
Member

gkatsev commented Aug 5, 2016

Description

standard-version handles versioning, changelog generation, and git tagging automatically. It does so by looking at the commit messages which follow this standard.
This would make it a lot easier for contributors to help out with landing patches because we could use the big green button on github with the "squash and merge" option and then the changelog will be made when we release.

There's also a more involved/hands off method: semantic-release. It's like standard-version, except it will automatically version for you when a commit is merged. This is kind of nice because we won't need to think about what a release is, it just happens based on the commit message, which follows the same standard. Also, it can publish to an npm tag by default so we can promote it to latest on our own time.

What are your thoughts @videojs/core-committers?

@gkatsev gkatsev added this to the 3.12 build-improvements milestone Aug 5, 2016

@gkatsev

This comment has been minimized.

Show comment
Hide comment
@gkatsev

gkatsev Aug 15, 2016

Member

Everyone is in agreement that we want to move towards this because it would make it easier for everyone.

Member

gkatsev commented Aug 15, 2016

Everyone is in agreement that we want to move towards this because it would make it easier for everyone.

@gkatsev gkatsev closed this Aug 15, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment