-
-
Notifications
You must be signed in to change notification settings - Fork 182
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
Cleanup patterns settings #3765
base: master
Are you sure you want to change the base?
Conversation
@thet thanks for creating this Pull Request and helping to improve Plone! TL;DR: Finish pushing changes, pass all other checks, then paste a comment:
To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass, but it takes 30-60 min. Other CI checks are usually much faster and the Plone Jenkins resources are limited, so when done pushing changes and all other checks pass either start all Jenkins PR jobs yourself, or simply add the comment above in this PR to start all the jobs automatically. Happy hacking! |
is this addressing #3633 too? |
… ITinyMCESpellCheckerForm.
69ad4b4
to
d98f3ce
Compare
Does it need an upgrade step to remove existing entries from registry? |
This PR removes the "After the deadline" plugin, which is dead code.
It removes the relevant code parts without a deprecation warning, which is probably not acceptable.
How should I proceed here? Deprecate it for 6.0 and let it be removed for 6.1? Or should this breaking change to into 7.0?
It's not an urgent issue but would remove some code which is most probably unused.
Together:
#3765
plone/plone.base#33
plone/plone.api#504mergedJenkins:
https://jenkins.plone.org/job/pull-request-6.1-3.11/156/