Add a release cadence document for TeachLink Backend

[RUKAYAT-CODER]

Background

The Governance/ folder does not yet include a Governance/processes/RELEASE_CADENCE.md document. This is a governance gap: contributors and maintainers lack a clear, versioned reference for this area of governance. Adding the document closes the gap and keeps the change self-contained within the Governance folder.

Implementation Plan

• Create Governance/processes/RELEASE_CADENCE.md and document the release frequency.
• Specify the release train model.
• Define the freeze windows.
• Add regression tests where applicable
• Document the change

Acceptance Criteria

• Governance requirement is implemented successfully
• Scope is limited to a maximum of two files
• No changes are made outside the Governance folder
• No regression in existing functionality
• Tests pass and code follows project standards
• Change is documented

[OkeA-dev]

@OkeA-dev has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

I can work on this right away!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @OkeA-dev to this issue.

[Ade20000]

@Ade20000 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hey, please assign, i can fix this very fast

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ade20000 to this issue.

[244345]

@244345 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

I am a detail-oriented and reliable individual with strong skills in research, data entry, online tasks, and following instructions. I am committed to delivering accurate and high-quality work within deadlines and am available to start tasks immediately.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @244345 to this issue.

[xtrial01]

@xtrial01 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hi, I would like to work on this issue
I will get it done swiftly and diligently with a clean pr

ℹ️ Repo Maintainers: To accept this application, review their application or assign @xtrial01 to this issue.

[isiakaamusatobi59-jpg]

@isiakaamusatobi59-jpg has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

please maintainer i can work on this issue, assign please

ℹ️ Repo Maintainers: To accept this application, review their application or assign @isiakaamusatobi59-jpg to this issue.

[drips-wave]

Congratulations, @OkeA-dev! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.

🧑‍💻 @OkeA-dev: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊