Skip to content
This repository was archived by the owner on Oct 24, 2023. It is now read-only.

Commit 0ddc2a4

Browse files
committed
Update FoJS post to clarify how stable releases work
1 parent 588dece commit 0ddc2a4

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

pages/posts/future-of-json-schema.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -122,9 +122,9 @@ finalized, but here are some outcomes users can expect.
122122
you won't have to continue to update them as JSON Schema evolves.
123123
* Custom dialects and vocabularies will continue to be central concepts for
124124
customizing and extending JSON Schema.
125-
* Implementations only need to support the latest stable release. For example, a
126-
library that supports the 2025 release will automatically support the 2023 and
127-
2024 releases. The older releases will no longer need to be maintained as
128-
distinct versions. However, implementations that continue to support the
129-
"draft" releases would still need to maintain those as distinct versions from
130-
the current stable release.
125+
* Implementers won't need to maintain distinct code to support past stable
126+
releases. A library that supports the 2025 release will automatically support
127+
the 2023 and 2024 releases. The past stable releases will no longer need to be
128+
maintained as distinct versions. However, implementations that continue to
129+
support the "draft" releases would still need to maintain those as distinct
130+
versions from the current stable release.

0 commit comments

Comments
 (0)