Skip to content
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

Enable versioning for pages by default #169

Merged
merged 1 commit into from
Dec 11, 2024
Merged

Enable versioning for pages by default #169

merged 1 commit into from
Dec 11, 2024

Conversation

davisagli
Copy link
Member

Fixes #143

@davisagli davisagli added the 01 type: bug something does not work label Dec 11, 2024
@mister-roboto
Copy link

@davisagli 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!

@davisagli
Copy link
Member Author

The failing tests should be fixed by either plone/plone.app.contenttypes#715 or plone/Products.CMFEditions#117

@davisagli
Copy link
Member Author

@jenkins-plone-org please run jobs

@davisagli davisagli merged commit 61b1bab into main Dec 11, 2024
10 of 11 checks passed
@davisagli davisagli deleted the page-versioning branch December 11, 2024 23:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
01 type: bug something does not work
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Missing plone.versioning behavior for Pages
2 participants