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

chore: mark v0.14.0 #1918

Merged
merged 1 commit into from
Apr 22, 2020
Merged

Conversation

aslushnikov
Copy link
Collaborator

@aslushnikov aslushnikov commented Apr 22, 2020

Note: this is a PR to be merged into the release-0.14 branch.

Once this is merged to the branch:

  • all test bots should kick in and run tests for this commit
  • publish_canary.yml will kick in and publish 0.14.0-next.XXXX version that can be tested manually

Once testing is complete:

  • If we are satisfied with the results, we can publish github release against this commit.
    Once release is published, the 0.14.0 will be published by publish_release.yml workflow.
  • if we are not satisfied, then we can either cherry-pick fixes into the branch, or re-create branch from a nicer point.

@yury-s
Copy link
Member

yury-s commented Apr 22, 2020

I wish it was more obvious from the GitHub UI that this is a change in a branch different than master, I wouldn't have known that if you hadn't mentioned that in the description.

@aslushnikov aslushnikov merged commit 797d278 into microsoft:release-0.14 Apr 22, 2020
@aslushnikov aslushnikov deleted the mark-0-14 branch April 22, 2020 19:07
aslushnikov added a commit that referenced this pull request Apr 23, 2020
Note: this is a PR to be merged into the `release-0.14` branch.

Once this is merged to the branch:
- all test bots should kick in and run tests for this commit
- `publish_canary.yml` will kick in and publish `0.14.0-next.XXXX` version that can be tested manually

Once testing is complete:
- If we are **satisfied** with the results, we can publish github release against this commit.
Once release is published, the `0.14.0` will be published by `publish_release.yml` workflow.
- if we are **not satisfied**, then we can either cherry-pick fixes into the branch, or re-create branch from a nicer point.
aslushnikov added a commit that referenced this pull request Apr 23, 2020
Note: this is a PR to be merged into the `release-0.14` branch.

Once this is merged to the branch:
- all test bots should kick in and run tests for this commit
- `publish_canary.yml` will kick in and publish `0.14.0-next.XXXX` version that can be tested manually

Once testing is complete:
- If we are **satisfied** with the results, we can publish github release against this commit.
Once release is published, the `0.14.0` will be published by `publish_release.yml` workflow.
- if we are **not satisfied**, then we can either cherry-pick fixes into the branch, or re-create branch from a nicer point.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants