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

Future Release Branches Frozen For Merging | branch:release-4.19 branch:release-4.20 #714

Open
openshift-merge-robot opened this issue Aug 31, 2021 · 0 comments
Labels
tide/merge-blocker Denotes an issue that blocks the tide merge queue for a branch while it is open.

Comments

@openshift-merge-robot
Copy link
Contributor

openshift-merge-robot commented Aug 31, 2021

The following branches are being fast-forwarded from the current development branch (master) as placeholders for future releases. No merging is allowed into these release branches until they are unfrozen for production release.

  • release-4.19
  • release-4.20

For more information, see the branching documentation.

@openshift-merge-robot openshift-merge-robot added the tide/merge-blocker Denotes an issue that blocks the tide merge queue for a branch while it is open. label Aug 31, 2021
@openshift-merge-robot openshift-merge-robot changed the title Future Release Branches Frozen For Merging | branch:release-4.10 branch:release-4.9 Future Release Branches Frozen For Merging | branch:release-4.10 Sep 6, 2021
@openshift-merge-robot openshift-merge-robot changed the title Future Release Branches Frozen For Merging | branch:release-4.10 Future Release Branches Frozen For Merging | branch:release-4.10 branch:release-4.11 Nov 18, 2021
@openshift-merge-robot openshift-merge-robot changed the title Future Release Branches Frozen For Merging | branch:release-4.10 branch:release-4.11 Future Release Branches Frozen For Merging | branch:release-4.11 Jan 28, 2022
@openshift-merge-robot openshift-merge-robot changed the title Future Release Branches Frozen For Merging | branch:release-4.11 Future Release Branches Frozen For Merging | branch:release-4.11 branch:release-4.12 Feb 22, 2022
@openshift-merge-robot openshift-merge-robot changed the title Future Release Branches Frozen For Merging | branch:release-4.11 branch:release-4.12 Future Release Branches Frozen For Merging | branch:release-4.12 Jun 24, 2022
@openshift-merge-robot openshift-merge-robot changed the title Future Release Branches Frozen For Merging | branch:release-4.12 Future Release Branches Frozen For Merging | branch:release-4.12 branch:release-4.13 Jul 7, 2022
@openshift-merge-robot openshift-merge-robot changed the title Future Release Branches Frozen For Merging | branch:release-4.12 branch:release-4.13 Future Release Branches Frozen For Merging | branch:release-4.13 Oct 28, 2022
@openshift-merge-robot openshift-merge-robot changed the title Future Release Branches Frozen For Merging | branch:release-4.13 Future Release Branches Frozen For Merging | branch:release-4.13 branch:release-4.14 Nov 7, 2022
@openshift-merge-robot openshift-merge-robot changed the title Future Release Branches Frozen For Merging | branch:release-4.13 branch:release-4.14 Future Release Branches Frozen For Merging | branch:release-4.14 Mar 3, 2023
@openshift-merge-robot openshift-merge-robot changed the title Future Release Branches Frozen For Merging | branch:release-4.14 Future Release Branches Frozen For Merging | branch:release-4.14 branch:release-4.15 Mar 13, 2023
@openshift-merge-robot openshift-merge-robot changed the title Future Release Branches Frozen For Merging | branch:release-4.14 branch:release-4.15 Future Release Branches Frozen For Merging | branch:release-4.15 Sep 8, 2023
@openshift-merge-robot openshift-merge-robot changed the title Future Release Branches Frozen For Merging | branch:release-4.15 Future Release Branches Frozen For Merging | branch:release-4.15 branch:release-4.16 Sep 29, 2023
@openshift-merge-robot openshift-merge-robot changed the title Future Release Branches Frozen For Merging | branch:release-4.15 branch:release-4.16 Future Release Branches Frozen For Merging | branch:release-4.16 Dec 8, 2023
@openshift-merge-robot openshift-merge-robot changed the title Future Release Branches Frozen For Merging | branch:release-4.16 Future Release Branches Frozen For Merging | branch:release-4.17 Jan 3, 2024
@openshift-merge-robot openshift-merge-robot changed the title Future Release Branches Frozen For Merging | branch:release-4.17 Future Release Branches Frozen For Merging | branch:release-4.16 branch:release-4.17 Jan 31, 2024
@openshift-merge-robot openshift-merge-robot changed the title Future Release Branches Frozen For Merging | branch:release-4.16 branch:release-4.17 Future Release Branches Frozen For Merging | branch:release-4.17 May 17, 2024
@openshift-merge-robot openshift-merge-robot changed the title Future Release Branches Frozen For Merging | branch:release-4.17 Future Release Branches Frozen For Merging | branch:release-4.17 branch:release-4.18 May 23, 2024
@openshift-merge-robot openshift-merge-robot changed the title Future Release Branches Frozen For Merging | branch:release-4.17 branch:release-4.18 Future Release Branches Frozen For Merging | branch:release-4.18 Aug 9, 2024
@openshift-merge-robot openshift-merge-robot changed the title Future Release Branches Frozen For Merging | branch:release-4.18 Future Release Branches Frozen For Merging | branch:release-4.18 branch:release-4.19 Aug 13, 2024
@openshift-merge-robot openshift-merge-robot changed the title Future Release Branches Frozen For Merging | branch:release-4.18 branch:release-4.19 Future Release Branches Frozen For Merging | branch:release-4.19 Nov 25, 2024
@openshift-merge-robot openshift-merge-robot changed the title Future Release Branches Frozen For Merging | branch:release-4.19 Future Release Branches Frozen For Merging | branch:release-4.19 branch:release-4.20 Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tide/merge-blocker Denotes an issue that blocks the tide merge queue for a branch while it is open.
Projects
None yet
Development

No branches or pull requests

1 participant