I just wonder if CKEDITOR 4.5 should be considered as a major release instead of a point release. The development time for CKEDITOR 4.5 seems to be heading for the same timeline for any of the previous major releases. And due to the changes and amount of issues to be fixed and implemented it seems only fitting that it should be considered as a major release and the version number updated to 5.0 to reflect this.
If we are lucky with all the issues they are having with browser compatibility and other issues to be resolved it may be released in time for the arrival of Microsoft windows 10 and IE12.
What are your thoughts?
I don't think it makes any
I don't think it makes any difference to anybody whether this will be CKEditor 4.5.0 or 5.0.0. For most developers it's just a number. Perhaps from marketing perspective it would be good to release CKEditor 5.0.0, because we could attract more attention. But even though CKEditor 4.5.0 takes a lot of time to finish, it still contains mostly changes in one plugin (clipboard) plus some new, related features in the core and many new plugins. The rest of changes are very small. But don't get me wrong - for the copy&paste, drag&drop and files upload themselves these are ground breaking changes of course. But in the entire editor context the changes are not that significant. Comparing to 2.0->3.0 and 3.0->4.0 we've made maybe 10% of that. Of course there's a lot of new code, but mostly in new plugins. The core and existing plugins changed a little.
The one problem with the current versioning is that CKEditor doesn't really follow SemVer. I remember a discussion (I think it was this) that SemVer makes sense for libs, but not that much for entire projects and we agree with this. All our minor releases (I mean *.X.*) would need to become major releases (X.*.*), because in such a big code base you make some backwards incompatible changes much more often. Therefore, we decided to clarify the versioning scheme for CKEditor 5 (related discussion) and, most importantly, version modules separately (this time sticking to SemVer).
PS. As for the IE12, we remember about it and we will check the situation before releasing 4.5.0.
Piotrek (Reinmar) Koszuliński
CKEditor JavaScript Developer
--
CKSource - http://cksource.com
--
Follow CKEditor on: Twitter | Facebook | Google+
PS. As for the IE12, we
I reported a ticket.
Piotrek (Reinmar) Koszuliński
CKEditor JavaScript Developer
--
CKSource - http://cksource.com
--
Follow CKEditor on: Twitter | Facebook | Google+