March 2026 Release Roadmap Review

[jgmcl]

This is a draft for review before converting to formal GitHub Issues (as per my conversation with John Beverley regarding a tentative workflow)
Feedback welcome from: @johnbeve @neilotte @mark-jensen @APCox

Issue 1
Title: March 2026 Release Roadmap (PM View)
Description: This issue tracks the overall plan for the March CCO release.

Phase 1A — Initial Transition & Baseline Delivery (Jan–Mar)

• Repository and issue tracker cleanup
• CI / testing foundations
• Stakeholder engagement startup
• Delivery of an initial stable domain extension
• Establish clear release process for March

Issue 2
Title: Clean up and standardize GitHub labels for CCO
Label: documentation or devops

Issue 3
Title: Document current CCO release process
Label: devops
Goal: clarify the current CCO release process so the March 2026 release is repeatable.
Note: input required from Mark Jensen; likely requires multiple follow-ups.

Issue 4
Title: Improve CI build reliability for ontology releases
Assign to: Shanmukh
Label: devops

Issue 5
Title: Deliver stable domain extension for March release (tracking issue)
Label: design
Description: This issue tracks progress toward delivering the Phase 1A stable domain extension
needed for the March 2026 release. Technical design is led by the ontology team.

Issue 6
Title: Define process for collecting community competency questions
Label: community

[johnbeve]

@neilotte @APCox @mark-jensen did you get an alert for this?

[neilotte]

@johnbeve I did not.

[APCox]

March is going to be a push for Issue 5, but let's try to make it happen.

[mark-jensen]

Yeah, I missed this too.

[neilotte]

Looks good.

[mark-jensen]

We need to discuss this in detail at an upcoming meeting and set up a plan for what is reasonable. Where did the March deadline come from?