Opened 6 years ago

Closed 5 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 Piotrek Koszuliński)

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 6 years ago by Jakub Ś

Status: newconfirmed

comment:2 Changed 6 years ago by Piotrek Koszuliński

Additional topic related to versioning (https://github.com/ckeditor/ckeditor-releases/issues/6)

Hey did you know that the lack of predictable version numbering is causing difficulties configuring your library? See this long running thread over at Drupal Org.

https://drupal.org/comment/7153730#comment-7153730

comment:3 Changed 6 years ago by Piotrek Koszuliński

Description: modified (diff)

comment:4 Changed 6 years ago by Frederico Caldeira Knabben

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 5 years ago by Marek Lewandowski

Resolution: fixed
Status: confirmedclosed

Starting with CKE 4.3.3 we've introduced semver compilant tags into ckeditor-dev, ckeditor-releases and ckeditor-presets repositories.

Note: See TracTickets for help on using tickets.
© 2003 – 2019 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy