> For the complete documentation index, see [llms.txt](https://docs.oceanenterprise.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oceanenterprise.io/~/revisions/IKmS06jx6d2zQh2vmKN9/discover/governance/version-numbering-and-releases.md). # Version Numbering & Releases ## 1. Version Numbering Strategy #### Semantic Versioning Versions of OE software are named and numbered according to MAJOR.MINOR.PATCH format (e.g., 2.3.1): * MAJOR: Breaking changes, incompatible API modifications * MINOR: New features, backward-compatible additions * PATCH: Bug fixes, security patches ## 2. Release Cadence #### Feature-Based Releases * A new release will occur when specific features are complete, typically about every 6 months ## 3. Release Preparation Process #### Phase 1: Planning * Typically 3-4 months prioir to release * Roadmap review: Maintainer meeting to finalize features for release * Issue triage: Label and milestone assignment * Communication: Announce upcoming release and feature freeze date * Documentation planning: Identify docs needing updates #### Phase 2: Development Window * Active development: Contributors work on milestoned features * Regular check-ins: Progress updates in public channels, typically weekly * Pull request reviews: Prioritize release-targeted PRs * Testing infrastructure: Ensure Continuous Iteration (CI) / Continuous Delivery (CD) pipelines are healthy #### Phase 3: Feature Freeze * typically 1 month before scheduled release * Code freeze: No new features, only bug fixes * Beta release: Deploy beta version for community testing * Bug bash: Organized testing period with contributor participation * Translation updates: Coordinate with localization teams * Documentation completion: Finalize release notes, changelog, upgrade guides #### Phase 4: Release Candidate * Release Candidate deployment: Publish release candidate (RC) * Final testing: Regression testing, security audit * Sign-off process: Maintainer approval required * Announcement draft: Prepare blog posts, social media content #### Phase 5: Release Day * Tag creation: Create git tag with version number * Build artifacts: Generate and sign release binaries/packages * Distribution: Upload to package managers, registries, download sites * Announcement: Publish release notes, blog post, social media * Support preparation: Ensure maintainers are available for issues #### Phase 6: Post-Release Activities * Monitor issue tracker for critical bugs * Prepare hotfix releases if needed * Gather community feedback * Update documentation based on user questions * Retrospective meeting with contributors * Document lessons learned * Update release process based on feedback * Begin planning next release cycle --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.oceanenterprise.io/~/revisions/IKmS06jx6d2zQh2vmKN9/discover/governance/version-numbering-and-releases.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.