# Proposal: Release branches in OpenUSD GitHub repository

**URL:** <https://forum.aousd.org/t/proposal-release-branches-in-openusd-github-repository/3043>\
**Category:** USD\
**Tags:** proposal\
**Created:** [September 14, 2026, 5:24pm UTC](https://forum.aousd.org/t/proposal-release-branches-in-openusd-github-repository/3043 "2026-09-14T17:24:09Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![sunya](https://avatars.discourse-cdn.com/v4/letter/s/9de053/32.png) [@sunya](https://forum.aousd.org/u/sunya)\
**Post date:** [September 14, 2026, 5:24pm UTC](https://forum.aousd.org/t/proposal-release-branches-in-openusd-github-repository/3043/1 "2026-09-14T17:24:09Z")

</div>

Hi all,

I’ve posted a new proposal on OpenUSD-proposals for adding release branches in the OpenUSD repository for each release, instead of relying on a single `release` branch and tags on that branch to label releases. This addresses a problem where updates to the `dev` branch are blocked during the period leading up to an OpenUSD release due to the single `release` branch. It would also make managing patch releases easier, opening the door to more frequent security patches to older releases in the future.

The proposal is here: [Proposal for version branches in OpenUSD repository by sunyab · Pull Request #113 · PixarAnimationStudios/OpenUSD-proposals · GitHub](https://github.com/PixarAnimationStudios/OpenUSD-proposals/pull/113)

We intend to implement this starting with the upcoming 26.11 release.

- Sunya