Opened 9 years ago
Closed 9 years ago
#10882 closed Task (fixed)
Start using Semantic Versioning
Reported by: | Piotrek Koszuliński | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | General | Version: | |
Keywords: | Cc: |
Description (last modified by )
We should tag our releases using Semantic Versioning (http://semver.org), because:
- it's becoming a standard,
- some tools (like http://bower.io/) may have problems with our non-standard tag names.
Places which we should change:
- tags in all repositories,
- CKEDITOR.version,
- other places related to code and development, but not guides, blog posts, etc.
Change History (5)
comment:1 Changed 9 years ago by
Status: | new → confirmed |
---|
comment:2 Changed 9 years ago by
comment:3 Changed 9 years ago by
Description: | modified (diff) |
---|
comment:4 Changed 9 years ago by
Agreed... all "computer readable" stuff should use Semantic Versioning. This touches git tags, CKEDITOR.version, etc.
In the other hand, "human readable" stuff can go with shorter versions. For example, CKEditor 4 or CKEditor 4.3. This touches blogs, social stuff, etc.
comment:5 Changed 9 years ago by
Resolution: | → fixed |
---|---|
Status: | confirmed → closed |
Starting with CKE 4.3.3 we've introduced semver compilant tags into ckeditor-dev, ckeditor-releases and ckeditor-presets repositories.
Additional topic related to versioning (https://github.com/ckeditor/ckeditor-releases/issues/6)