Skip to content

Commit

Permalink
CLDR-16883 v44: fix commit metadata (#3329)
Browse files Browse the repository at this point in the history 
- 2eef76b should be CLDR-16883
  • Loading branch information
@srl295
srl295 authored Oct 9, 2023
1 parent 9b70968 commit f904cc6
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions .github/COMMIT_METADATA.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@
- 7c8c8bb83ca253f499d4d5c08f968327611a6a70 CLDR-16437 v44 dep fix
- f0324b82d27695306d1126c54a6de381cfbd9bcc CLDR-16564 v44 version number fix
- b0a6207ff224a6cd8ca7f888c8a4740bacb83124 CLDR-16598 v44 Monitor SurveyTool server disk space
- 2eef76b58182ee16e12897df33094eafd18a1833 CLDR-16883 v44 ST: hide sideways inheritance

### The following are items to skip for a certain CLDR version.
### Format: `# SKIP v00` followed by a list of commits to skip for that version (same structure as above)
Expand Down

1 comment on commit f904cc6

@kloczek
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If it possible to change tagging convention from release-<version-with-bashes> to release-<version.with.dots>? 🤔
Using dashes in version forces release dashes by dots on packaging.

Second thing is that after release 44.betaN just released 44 version tag is lower so it creates some difficulties on packaging.
Better would tag that as release-44.0

More details about above versioning convention is possible to find on https://discourse.gnome.org/t/new-gnome-versioning-scheme/4235

Please sign in to comment.