-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CKEditor 5 – Roadmap to 1.0.0 and beyond #172
Comments
Predicted ETA for 1.0.0 alpha is early Q2 2017. The scope of 1.0.0 alpha is pretty well defined now and we just don't know how long some of these things can still take. Even with the alpha version, we'd like to have a quite stable software and documentation which is complete enough to start tooling with the editor. Between the alpha and the final version we'll be working on stability, code cleanup refactoring (the goal is to get as stable API after 1.0.0 final as possible) and additional resources. Then... we're back to features :). |
I updated the first post to reflect the recent progress.
|
I update the first post to reflect the recent progress and decisions.
|
I update the first post to reflect the recent progress and decisions.
|
Good morning, |
Hi! Good morning (or evening ;))! The first beta release will be in Q1 2018. Perhaps even within a month, but I don't want to make promises. We're right now finishing the huge refactoring that we had planned before the first beta and are switching to polishing the release. |
@Reinmar - any update on the timing of this first beta release? |
We finished the refactoring and we're happy with the results. We focus now on some minor cleanup, bug fixing and docs. Which means that there's little that can go wrong, so we'll release the beta in March. Right now we're targetting the middle of March. |
@Reinmar will that include support for paste from MS Word and tables? |
No, PFW (paste from MS Word) and tables will be added later. We started working on tables recently and are going to start work on PFW soon. |
Happy Friday, Does it still seem like Middle of March as BETA release date? |
Yes :) |
Thank you! This is good to hear |
Good morning, Wanted to check in and see how things were with the Mid March BETA Release? Thank you :-) |
Good morning Reinmar! Wanted to check in and see if we should expect today or tomororw for BETA? Thank you so much! |
Good day, Thank you for this update! Where would we go to download this? Thank you! |
Just follow https://docs.ckeditor.com/ckeditor5/latest/builds/guides/integration/installation.html. And in case of issues, please report them on https://github.com/ckeditor/ckeditor5 to keep this thread clean. |
Good morning and thank you for your reply! Thank you |
Nope, you're right. We were meant to update the website today, but we also released CKEditor 4.9 and Easy Image for CKEditor Cloud Services yesterday and there's a queue of pending updates. We should have the download sections and demos updated on https://ckeditor.com on Monday. In the meantime, if you want to download beta.1 zip packages, you can do that from http://download.cksource.com/CKEditor/CKEditor5/1.0.0-beta.1/ |
We published release notes for beta.1+beta.2 in #184. And I updated the roadmap to best reflect the current status of things. |
We published beta.4 today: #185 (beta.3 was skipped). |
Finally! The first stable version of CKEditor 5 is out!
PS. It's not a mistake that it is |
I forgot to mention – together with CKEditor 5 v10.0.0 we released plugins enabling real-time collaborative editing in CKEditor 5 :) You can find out more in https://docs.ckeditor.com/ckeditor5/latest/features/collaboration/overview.html |
I updated the list in the first post with things that we introduced in: So this list now includes the following features:
|
The roadmap is divided into 3 parts:
We’ll be updating the roadmap to match the progress that we make.
Feedback, ideas, proposals are greatly welcomed (especially for the "after 1.0.0" part) :).
Done
<input>
, but for editable elements).In progress
To do
After 1.0.0
Of course, this is not a complete list of features and improvements that we could do. We'll be adding new items to the list and prioritise them based on the feedback from the community.
The text was updated successfully, but these errors were encountered: