This repository has been archived by the owner on Dec 1, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 21
Future Release Branches Frozen For Merging | branch:release-4.19 branch:release-4.20 #238
Labels
Comments
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The following branches are being fast-forwarded from the current development branch (main) 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.
The text was updated successfully, but these errors were encountered: