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

Document the release process #51

Open
mkumatag opened this issue Dec 8, 2020 · 1 comment
Open

Document the release process #51

mkumatag opened this issue Dec 8, 2020 · 1 comment
Labels
kind/documentation Categorizes issue or PR as related to documentation. kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@mkumatag
Copy link
Member

mkumatag commented Dec 8, 2020

This task is for documenting the release process which involved tagging and publishing the release

/kind feature
/priority important-longterm

@ltccci ltccci added kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Dec 8, 2020
@mkumatag
Copy link
Member Author

mkumatag commented Dec 8, 2020

commands used for tagging:

git tag v0.1-alpha.8
git push origin v0.1-alpha.8

The command for getting the commits:

git log v0.1-alpha.8..v0.1-alpha.9 --oneline | grep -v "Merge pull"

For listing the contributors(used only for the released versions):

git log --pretty=format:"%cN; %ce" v0.1..v0.1.1 | grep -v "Merge pull" | sort | grep -v GitHub | uniq

@mkumatag mkumatag added the kind/documentation Categorizes issue or PR as related to documentation. label Dec 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Categorizes issue or PR as related to documentation. kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

No branches or pull requests

2 participants