-
Notifications
You must be signed in to change notification settings - Fork 101
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
Release v0.22.0 #468
Comments
I never did a release in provider-gcp before, maybe @hasheddan or @turkenh can help me defining all steps necessary to consider the |
@Feggah happy help out here :) |
Thanks @hasheddan! I didn't see any issue in the past that were tracking the release of this provider. Do you know the process in the top of your mind? If so, could you edit the issue description and fill the "Steps needed for the release" subsection? |
@Feggah the general release process follows the same as Crossplane as defined in https://crossplane.io/docs/v1.9/contributing/release-process/. Happy to help run this on Monday -- what are the status of the PRs you linked / are they hard blockers? |
@hasheddan Got it. They are not hard blockers, just something nice to have in the release. They are all reviewed and waiting for some requested changes. The PR #440 is just waiting an approval and merge, I solved the requested issues and it is waiting for the second review. Can you have a look? I believe we can proceed without the rest because I don't know how much time contributors will need to solve the requested changes. |
Release v0.22.0
This is a tracking issue for the release
v0.22.0
.I would love to include in this release the following PRs:
They are almost ready to merge, I expect to merge them until next week and then we are ready to cut the release.
Steps needed for the release
Follow the steps defined in the Release Process documentation
The text was updated successfully, but these errors were encountered: