# The 3.15 branch is locked for RC1

**URL:** <https://discuss.python.org/t/the-3-15-branch-is-locked-for-rc1/108389>\
**Category:** Core Development\
**Tags:** release\
**Created:** [August 4, 2026, 8:49am UTC](https://discuss.python.org/t/the-3-15-branch-is-locked-for-rc1/108389 "2026-08-04T08:49:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![hugovk](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/hugovk/32/14505_2.png) [@hugovk](https://discuss.python.org/u/hugovk)\
**Post date:** [August 4, 2026, 8:49am UTC](https://discuss.python.org/t/the-3-15-branch-is-locked-for-rc1/108389/1 "2026-08-04T08:49:47Z")

</div>

The 3.15 branch is now locked for all (except release managers and admins) until the 3.15.0 final release ([scheduled for 2026-10-01](https://peps.python.org/pep-0790/)).

Reminder from the [devguide](https://devguide.python.org/developer-workflow/development-cycle/#release-candidate-rc):

> A branch preparing for an RC release can only have bugfixes applied that have been reviewed by other core team members. Generally, these issues must be severe enough (for example, crashes) that they deserve fixing before the final release. All other issues should be deferred to the next development cycle, since stability is the strongest concern at this point.
> 
> While the goal is to have no code changes between an RC and a final release, there may be a need for final documentation or test fixes. Any such proposed changes should be discussed first with the release manager.
> 
> You **cannot** skip the peer review during an RC, no matter how small! Even if it is a simple copy-and-paste change, **everything** requires peer review from a core team member.

As this worked so well last year, let’s repeat:

I don’t want to be the review bottleneck. Please pick someone who works in the same area to review your PR first, then I can more easily merge your approved PR. Reviewed PRs will be at the top of the queue for merge.

Thank you!

---

<div class="post-metadata">

**Author:** ![tjreedy](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/tjreedy/32/137_2.png) [@tjreedy](https://discuss.python.org/u/tjreedy)\
**Post date:** [August 8, 2026, 2:31pm UTC](https://discuss.python.org/t/the-3-15-branch-is-locked-for-rc1/108389/2 "2026-08-08T14:31:01Z")

</div>

Is the double review needed on the 3.15 PR as well as the main PR?

---

<div class="post-metadata">

**Author:** ![hugovk](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/hugovk/32/14505_2.png) [@hugovk](https://discuss.python.org/u/hugovk)\
**Post date:** [August 9, 2026, 5:58am UTC](https://discuss.python.org/t/the-3-15-branch-is-locked-for-rc1/108389/3 "2026-08-09T05:58:15Z")

</div>

A single peer review on the 3.15 PR from a core team member is needed.

- If you opened the `main` PR, find another core dev to review the 3.15 PR.
- If someone else opened the `main` PR, you can review the 3.15 PR.