Skip to content

7.0: Remove remaining deprecated Plone 5 resource registry records.#365

Draft
thet wants to merge 1 commit into
masterfrom
cleanup-resource-registry-70
Draft

7.0: Remove remaining deprecated Plone 5 resource registry records.#365
thet wants to merge 1 commit into
masterfrom
cleanup-resource-registry-70

Conversation

@thet

@thet thet commented Mar 7, 2026

Copy link
Copy Markdown
Member

This PR targets the yet-not-started Plone 7.0 release and cleans up resource registry records.

It's basically the same like in #363 which was reverted in #364 and saved for future use in this PR. This one has also the fix that plone.resources.development isn't deleted.

A precondition for that is also to clean up and remove the deprecated IBundleRegistry attributes and while at it also the IResourceRegistry interface from plone.base: https://github.com/plone/plone.base/blob/main/src/plone/base/interfaces/resources.py#L91

@mister-roboto

Copy link
Copy Markdown

@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:

@jenkins-plone-org please run jobs

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!

@thet thet marked this pull request as draft March 7, 2026 14:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants