[integration][release] code freeze - lock/unlock branch during MRI/releases
There seems to be some confusion on the process followed while we lock/unlock branches between MRI version bumps and during our releases. Since these MRI version bumps are happening after the code freeze on the same branch, and multiple support tickets are being opened to lock/unlock the same branch. Once the MRI version bump is complete the branch is getting unlocked amidst the release.
Going forward, I recommend adding a "note" in the support ticket requesting the ticket to be assigned to me. I'll also notify the LF team internally to reassign these tickets to me.