-
Notifications
You must be signed in to change notification settings - Fork 2
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
[META] What needs to be done to move this module to core #117
Comments
Everything else should be pulled over to the core queue I think. Other things: we should make a release that expresses a bit more confidence in its version number, i.e. I started a blog post to describe the whole upgrade/transition process but I haven't finished it yet. |
Blog post draft (unpublished): https://backdropcms.org/news/backdrop-cms-upgrade-from-ckeditor-4-to-5 |
Great to have an upcoming Blog post! Are there plans to publish it soon? Just read the post, looks great. Only suggestion: Make more clear in some text passages if they refer to the upcoming core version or to the contrib version of CKE 5. Also add a link to the contrib version. |
Ah, sorry I meant to add links. I'll revise that tomorrow. Thanks @olafgrabienski! And I'll clarify as you suggest. |
I added screenshots and published the blog post! https://backdropcms.org/news/upgrade-from-ckeditor-4-to-5 |
I considered making another Note we will still likely have additional releases 1.0.1, 1.0.2, etc. |
Per backdrop/backdrop-issues#4122, this module is now included in core! We did it! |
What's the status of this module and at which point is it ready to get moved to core?
It seems like almost (#76) all the potentially blocking issues known from Drupal have been addressed (#36).
Or did new ones pop up?
The module still has bugs, but on the other hand, it might get more attention and testing, if it's integrated in core.
The text was updated successfully, but these errors were encountered: