CCO Release Candidate 2.2 Review

[johnbeve]

CCO 2.2 Release Details

The release/2.2 branch has been created and is now under formal review.

Review window: June 29 – July 12, 2026
Target release date: July 15, 2026

Please review the release branch and file any release-blocking issues by July 12.

Release branch:release/2026-07

Pull request: #917

Review categories:

• blocking: must be resolved before release
• non-blocking: can be addressed after release
• discuss: needs discussion before triage

After July 12, new issues will be triaged for the next development cycle unless they are genuine release blockers.

How to Contribute During the 2.2 Release Review

Contributors should not make changes directly to release/2.2. All changes should be made through separate branches and pull requests.

1. For release-blocking fixes

If your change fixes something that must be resolved before the 2.2 release, create a new branch from release/2.2.

Example:

git checkout release/2.2
git pull
git checkout -b fix/2.2-short-description

Make your changes, then commit and push:

git add .
git commit -m "Fix short description of release issue"
git push -u origin fix/2.2-short-description

Then open a pull request into:

fix/2.2-short-description → release/2.2

Use this route only for changes that are appropriate for the release candidate, such as:

QC failures
broken imports
missing annotations
incorrect labels or definitions
release-note corrections
documentation errors
broken links
other release-blocking problems

2. For non-blocking or future work

If your change is not required for the 2.2 release, create a branch from the normal development branch instead.

Usually this means:

git checkout develop
git pull
git checkout -b feature/short-description

Then open a pull request into:

feature/short-description → develop

Use this route for:

new modeling proposals
new classes or relations
large refactors
non-urgent documentation improvements
new ontology modules
changes needing broader discussion

These items should not be merged into release/2.2 unless they are explicitly approved as part of the release.