3.13 branch locked for the rc1 release

FYI, I’ve locked the 3.13 branch for the rc1 release, just so the history of the rc1 release is linear.

Due to real-life circumstances I’m not locking the branch between rc1 and rc2 this time. I just can’t promise timely merges at the moment, so instead I’ll review all PRs after the fact. Even so, please by very very conservative with changes in 3.13 from now on. I will probably lock the branch after rc2, however.

7 Likes

If I understand, you are locking 3.13 until the overdue .rc1 (hopefully to come soon), then unlocking after it is released, but after locking for the .rc2, you expect to keep it locked until the final release.

Yes. rc1 is now released (announcement incoming) and the branch is unlocked, and unless people let it go wonky I’ll keep it open until rc2, and then close it until the final release.

This topic was automatically closed after 365 days. New replies are no longer allowed.