Preserve the emergency-fix exception for the frozen maintenance branch

Signed-off-by: Ralf W. Grosse-Kunstleve <rgrossekunst@nvidia.com>

Author: rwgk

.github/RELEASE-bindings.md

@@ -24,8 +24,10 @@ must continue while development advances, create a short release branch such
 as `release/bindings-12.9.11` from the chosen commit. For an emergency after a
 release, start from its exact tag, provided that tag contains the new package
 layout. For the first release after this transition, use a validated commit
-containing both roots; do not resume development on the historical `12.9.x`
-branch. Keep the package layout and release tooling together on the branch.
+containing both roots. Keep routine development on `main`; the historical
+`12.9.x` branch stays frozen except for emergency fixes using compatible
+historical tooling. Reconcile those fixes into the main-tree maintenance
+root. Keep the package layout and release tooling together on new release branches.
 
 Record the source commit, intended tag, selected package root, release owner,
 and accepted changes in the release checklist. A branch is a temporary scope

CONTRIBUTING.md

@@ -394,8 +394,9 @@ through the [CI tools](ci/README.md).
 `main` integrates changes for both supported majors. Short release branches
 can stabilize a selected release or carry urgent fixes while development
 continues. Return applicable fixes to `main` and assess both source roots.
-The historical `12.9.x` branch is retained for diagnosis of old releases;
-new main CI and releases do not fetch package artifacts from that branch.
+The historical `12.9.x` branch stays frozen except for emergency fixes,
+which must be reconciled into `main`. New main CI and releases do not fetch
+package artifacts from that branch.
 
 The [bindings release guide](.github/RELEASE-bindings.md) covers release scope,
 manual backport automation, source and control revisions, and validation.

ci/README.md

@@ -295,9 +295,10 @@ python -m ci.tools.bindings_config --check-package-metadata
 ## Maintaining Both Bindings Roots
 
 `main` is the integration branch for both bindings release lines. The old
-`12.9.x` branch remains available as a record of earlier releases; develop
-new CUDA 12 changes in `cuda_bindings_12/` on `main`. Short release branches
-may stabilize a selected version or carry urgent fixes while `main` advances.
+`12.9.x` branch stays frozen except for emergency fixes using compatible
+historical tooling; reconcile any such fix into `cuda_bindings_12/` on `main`.
+Routine CUDA 12 development belongs in that main-tree root. Short release
+branches may stabilize a selected version or carry urgent fixes while `main` advances.
 The [bindings release guide](../.github/RELEASE-bindings.md) describes branch
 creation, backport automation, independent release validation, and returning
 fixes to `main`. The

cuda_bindings_12/MAINTENANCE.md

@@ -9,10 +9,12 @@ SPDX-License-Identifier: Apache-2.0
 CUDA 13 bindings live in `cuda_bindings_13/`. The package roots and their release
 statuses are configured in [`ci/versions.yml`](../ci/versions.yml).
 
-Integrate both release lines on `main`. The former `12.9.x` branch is a record
-of past releases; new CUDA 12 fixes, tests, and documentation belong in
-`cuda_bindings_12/`. Short release branches may stabilize a release or carry
-an urgent fix; return such fixes to `main` and assess the CUDA 13 root too.
+Integrate both release lines on `main`. The former `12.9.x` branch stays
+frozen except for emergency fixes using compatible historical tooling;
+reconcile those fixes into `cuda_bindings_12/`. Routine CUDA 12 fixes, tests,
+and documentation belong in this main-tree root. Short release branches may
+stabilize a release or carry an urgent fix; reconcile such fixes into `main`
+and assess the CUDA 13 root too.
 
 Follow the [bindings release guide](../.github/RELEASE-bindings.md) for branch
 selection, patch-release scope, backports, and release validation.