Formalizing Release v1.0 -- Stable Baseline#245
Merged
Merged
Conversation
- Created CHANGELOG.md following Keep a Changelog format - Documented v1.0-beta.1 pre-release (2024-01-06) with all core tables - Promoted to v1.0 stable (2025-12-23) with no normative changes - Established baseline for tracking v2.0 normative changes
chrisyamas
added
📙 docs
Contributor
|
Documentation available at: |
jlstpaul
approved these changes
Dec 23, 2025
gabriel-korbato
approved these changes
Dec 24, 2025
evansiroky
approved these changes
Dec 26, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Promotes TIDES specification to
v1.0stable release. No normative changes fromv1.0-beta.1. This release establishes a stable baseline before introducingv2.0breaking changes.Changes
v1.0-beta.1pre-release (2024-01-06)v1.0stable (2025-12-23)[Unreleased]section for trackingv2.0changesWhy now?
As we close out an active year of TIDES implementations and community input, our current Issues Working Group has determined the details of several normative change proposals for
v2.0, including breaking changes (from issues #235, #237) and new features (#220, #240).- For reference, the Working Group's notes from the Fall 2025 meetings on December 1 and December 10.
Before merging those changes, we need a stable v1.0 reference point for implementations currently using
v1.0-beta.1, migration documentation for v2.0 breaking changes, as well as clear versioning per the change management policy.Release checklist
Per change management policy:
v1.0after merge