pinchord-22 Versioning
Pinchord · pinchord.git · Tickets · Changelog
A Pinchord Ticket (Closed):
Ticket · History
- September 9, 2026 Created (title: Versioning)
Changes
@@ -0,0 +1,12 @@+---+title: Versioning+permalink: pinchord/versioning/+ticket: open+---++*A [[pinchord-tickets|Pinchord Ticket]] (Open):*++Symptoms:+- Pinchord has followed the same `major.minor.system-minor` versioning schema since the start, and it is a mismatch to the actual semantics of Pinchord releases in [[Pinchord Pre-release|pre-release]]+- The current versioning schema will not work come [[pinchord-release]]. Pinchord will receive canonical updates across all of its release versions, and the current versioning schema has no way to express these updates.+- Pinchord versioning names are a critical part of Pinchord's implementation. See [[pinchord-undocumented-versioning]]. - September 9, 2026 Edited
Changes
@@ -6,7 +6,24 @@ *A [[pinchord-tickets|Pinchord Ticket]] (Open):* -Symptoms:-- Pinchord has followed the same `major.minor.system-minor` versioning schema since the start, and it is a mismatch to the actual semantics of Pinchord releases in [[Pinchord Pre-release|pre-release]]-- The current versioning schema will not work come [[pinchord-release]]. Pinchord will receive canonical updates across all of its release versions, and the current versioning schema has no way to express these updates.+## Symptoms++- Pinchord has followed the same `x.y.system` versioning schema since the start of [[Pinchord Pre-release|pre-release]], but it fails to make clear that versions of `x` may be incompatible with each other.+- The current versioning schema will not work come [[pinchord-release|release]]. Pinchord will receive canonical updates across all of its release versions, and the current versioning schema has no way to express these updates. - Pinchord versioning names are a critical part of Pinchord's implementation. See [[pinchord-undocumented-versioning]].++## Problem++There is a mismatch between how Pinchord is versioned and how releases of Pinchord actually work.++Several incompatible pre-release iterations of Pinchord have been shipped under the same name "Pinchord", despite being different systems that are incompatible with each other.++## Potential Solution++Adopt the naming scheme "Pinchord Pre-release X", and use compatible versions of these systems, either as increasing numbers, or another format.++### File Names++As mentioned in [[pinchord-undocumented-versioning]], file names dictate whether Plover will replace existing dictionaries when the Plover plugin updates. Files with the same name will not be replaced.++Even though versions under the same name are compatible, updating should still have the expectation of old files being shadowed in favor of new files. - October 20, 2026 Change formatting
Changes
@@ -10,7 +10,7 @@ - Pinchord has followed the same `x.y.system` versioning schema since the start of [[Pinchord Pre-release|pre-release]], but it fails to make clear that versions of `x` may be incompatible with each other. - The current versioning schema will not work come [[pinchord-release|release]]. Pinchord will receive canonical updates across all of its release versions, and the current versioning schema has no way to express these updates.-- Pinchord versioning names are a critical part of Pinchord's implementation. See [[pinchord-undocumented-versioning]].+- Pinchord versioning names are a critical part of Pinchord's implementation. See [[pinchord-undocumented-versioning|undocumented versioning]]. ## Problem @@ -24,6 +24,6 @@ ### File Names -As mentioned in [[pinchord-undocumented-versioning]], file names dictate whether Plover will replace existing dictionaries when the Plover plugin updates. Files with the same name will not be replaced.+As mentioned in [[pinchord-undocumented-versioning|undocumented versioning]], file names dictate whether Plover will replace existing dictionaries when the Plover plugin updates. Files with the same name will not be replaced. Even though versions under the same name are compatible, updating should still have the expectation of old files being shadowed in favor of new files. - October 21, 2026 Update the rest of the ticket pages to use numbers (renamed from pinchord-versioning.md, status: none → open, category: none → triaged, type: none → addition)
Changes
@@ -1,16 +1,17 @@ --- title: Versioning-permalink: pinchord/versioning/-ticket: open+status: open+category: triaged+type: addition+redirect_from:+ - pinchord/versioning/ --- -*A [[pinchord-tickets|Pinchord Ticket]] (Open):*- ## Symptoms - Pinchord has followed the same `x.y.system` versioning schema since the start of [[Pinchord Pre-release|pre-release]], but it fails to make clear that versions of `x` may be incompatible with each other.-- The current versioning schema will not work come [[pinchord-release|release]]. Pinchord will receive canonical updates across all of its release versions, and the current versioning schema has no way to express these updates.-- Pinchord versioning names are a critical part of Pinchord's implementation. See [[pinchord-undocumented-versioning|undocumented versioning]].+- The current versioning schema will not work come [[pinchord@9|release]]. Pinchord will receive canonical updates across all of its release versions, and the current versioning schema has no way to express these updates.+- Pinchord versioning names are a critical part of Pinchord's implementation. See [[pinchord@20|undocumented versioning]]. ## Problem @@ -24,6 +25,6 @@ ### File Names -As mentioned in [[pinchord-undocumented-versioning|undocumented versioning]], file names dictate whether Plover will replace existing dictionaries when the Plover plugin updates. Files with the same name will not be replaced.+As mentioned in [[pinchord@20|undocumented versioning]], file names dictate whether Plover will replace existing dictionaries when the Plover plugin updates. Files with the same name will not be replaced. Even though versions under the same name are compatible, updating should still have the expectation of old files being shadowed in favor of new files. - October 21, 2026 Edited
Changes
@@ -28,3 +28,7 @@ As mentioned in [[pinchord@20|undocumented versioning]], file names dictate whether Plover will replace existing dictionaries when the Plover plugin updates. Files with the same name will not be replaced. Even though versions under the same name are compatible, updating should still have the expectation of old files being shadowed in favor of new files.++### Notes++- Pinchord's README also needs to change for this :p - October 21, 2026 Edited
Changes
@@ -29,6 +29,10 @@ Even though versions under the same name are compatible, updating should still have the expectation of old files being shadowed in favor of new files. +### Potential Problems++- Does Python have a strong opinion about version names?+ ### Notes - Pinchord's README also needs to change for this :p - October 21, 2026 Edited
Changes
@@ -31,7 +31,7 @@ ### Potential Problems -- Does Python have a strong opinion about version names?+- https://packaging.python.org/en/latest/specifications/version-specifiers/#version-specifiers has a specific regex for version names, so release names will have to be wrangled into this format (please stop doing things like this) ### Notes - October 23, 2026 Remove trailing slashes
Changes
@@ -4,7 +4,7 @@ category: triaged type: addition redirect_from:- - pinchord/versioning/+ - pinchord/versioning --- ## Symptoms - October 24, 2026 Rename tickets to <project>-<number> <title> (renamed from pinchord@22.md, title: Versioning → none)
Changes
@@ -1,5 +1,4 @@ ----title: Versioning status: open category: triaged type: addition@@ -10,8 +9,8 @@ ## Symptoms - Pinchord has followed the same `x.y.system` versioning schema since the start of [[Pinchord Pre-release|pre-release]], but it fails to make clear that versions of `x` may be incompatible with each other.-- The current versioning schema will not work come [[pinchord@9|release]]. Pinchord will receive canonical updates across all of its release versions, and the current versioning schema has no way to express these updates.-- Pinchord versioning names are a critical part of Pinchord's implementation. See [[pinchord@20|undocumented versioning]].+- The current versioning schema will not work come [[pinchord-9 Release]]. Pinchord will receive canonical updates across all of its release versions, and the current versioning schema has no way to express these updates.+- Pinchord versioning names are a critical part of Pinchord's implementation. See [[pinchord-20 Undocumented Versioning]]. ## Problem @@ -25,7 +24,7 @@ ### File Names -As mentioned in [[pinchord@20|undocumented versioning]], file names dictate whether Plover will replace existing dictionaries when the Plover plugin updates. Files with the same name will not be replaced.+As mentioned in [[pinchord-20 Undocumented Versioning]], file names dictate whether Plover will replace existing dictionaries when the Plover plugin updates. Files with the same name will not be replaced. Even though versions under the same name are compatible, updating should still have the expectation of old files being shadowed in favor of new files. - October 24, 2026 Replace ticket status, category and resolution with ticket (status: open → none, category: triaged → none)
Changes
@@ -1,6 +1,5 @@ ----status: open-category: triaged+ticket: triaged type: addition redirect_from: - pinchord/versioning - November 4, 2026 Edited
Changes
@@ -1,5 +1,5 @@ ----ticket: triaged+ticket: closed type: addition redirect_from: - pinchord/versioning