-
Notifications
You must be signed in to change notification settings - Fork 41
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
vote: v1.1.1 #408
Comments
LGTM |
1 similar comment
LGTM |
I have concerns about the process of generating the Therefore, I'd like to propose a more compliant way to generate the
|
@priteshbandi How about this: instead of cherry-picking each commit, we just revert #379 in |
To enable a safe way to create a release branch, we need to enable CI for the release branch as proposed in #408 Signed-off-by: Junjie Gao <junjiegao@microsoft.com>
LGTM |
I will create a new release vote based on the proposed steps. |
Release
This would mean tagging 8d3b7a2 as
v1.1.1
to release.Note
This release doesn't include the #379 as this is a patch release.
The commit 8d3b7a2 was generated by the following steps:
git checkout -b release-1.1 v1.1.0
release-1.1
branch.Vote
We need at least
4
approvals from6
maintainers to releasenotation-go v1.1.1
.Changes
The code changes compared to v1.1.0 include:
Full Changelog: v1.1.0...8d3b7a2
The text was updated successfully, but these errors were encountered: