-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
doc: add a basic release process #1080
Conversation
aa0052c
to
0550396
Compare
1. A simple checklist. 2. A script to generate release notes. I'm explicitly ignoring anything like a branching model for the moment. We don't have a long RC process so that shouldn't be required (yet).
0550396
to
9d13654
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This pull request looks good to me, thanks for documenting the process.
I am approving as a review was requested from my side. I am not familiar with general Golang release best practices, nor am I familiar with the go-libp2p repository architecture. With that in mind, I don't think my review should be given much weight.
@@ -110,6 +110,10 @@ If you experience any issues migrating from gx to gomod, please [join the discus | |||
|
|||
`go test ./...` will run all tests in the repo. | |||
|
|||
### Releasing | |||
|
|||
Please start a release by opening a new [Libp2p Release](https://github.com/libp2p/go-libp2p/issues/new?assignees=&labels=kind/tracking&template=release.md) issue. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
(merging so I can create a release issue so we can test the process) |
I'm explicitly ignoring anything like a branching model for the moment. We don't have a long RC process so that shouldn't be required (yet).