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

Code cleanup, add 'volto.blocks' behavior to Plone Site GS types info… #43

Merged
merged 4 commits into from
Jan 20, 2022

Conversation

sneridagh
Copy link
Member

…. Remove 'Collection' from types in GS. Remove 'plone.richtext' behavior from Plone Site, Document, News Item, Events.

…. Remove 'Collection' from types in GS. Remove 'plone.richtext' behavior from Plone Site, Document, News Item, Events.
@sneridagh sneridagh requested a review from tisto January 17, 2022 18:58
@mister-roboto
Copy link

@sneridagh thanks for creating this Pull Request and help improve Plone!

To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass.

Whenever you feel that the pull request is ready to be tested, either start all jenkins jobs pull requests by yourself, or simply add a comment in this pull request stating:

@jenkins-plone-org please run jobs

With this simple comment all the jobs will be started automatically.

Happy hacking!

@sneridagh sneridagh mentioned this pull request Jan 17, 2022
29 tasks
@sneridagh
Copy link
Member Author

@jensens @tisto meh, I added the blocks behavior to Plone Site and GS is complaining in 5.2 because it does not know about it :/

We could make 4.0.0 Plone 6 only. Wasn't that the idea? I can't remember now.

@tisto
Copy link
Member

tisto commented Jan 17, 2022

@sneridagh I would prefer to keep things working for both versions, if that is possible with reasonable effort. Maintaining multiple branches of multiple packages (plone.volto, plone.restapi, Volto) will not end up well, we saw this in the past (p.a.contenttypes & plone.app.event, plone.app.discussion & dexterity). Plone 5.2 won't go away anytime soon.

@tisto
Copy link
Member

tisto commented Jan 17, 2022

@sneridagh zcml condition won't work for gs. A separate profile for Plone 6 seems overkill but might be the only option. What if we register the behavior via Python code and make it conditional?

@sneridagh
Copy link
Member Author

I agree, let's keep them compatible although it's ugly. It can be done programmatically, of course. I'll prepare it.

@sneridagh
Copy link
Member Author

@jenkins-plone-org please run jobs

@sneridagh sneridagh added this to the 4.0.0 milestone Jan 19, 2022
@tisto
Copy link
Member

tisto commented Jan 19, 2022

@sneridagh can you resolve the conflict? I guess this should go into the first 4.0.0a1 as well, right?

@sneridagh
Copy link
Member Author

@tisto Yep

* main:
  Remove c.folderishtypes dependency. (#36)
@sneridagh
Copy link
Member Author

@tisto Done! Take a final look before merging.

@sneridagh
Copy link
Member Author

@jenkins-plone-org please run jobs

@tisto
Copy link
Member

tisto commented Jan 19, 2022

@sneridagh LGTM! Feel free to hit the merge button once Jenkins is happy.

@sneridagh
Copy link
Member Author

@jenkins-plone-org please run jobs

@sneridagh sneridagh merged commit 7e01029 into main Jan 20, 2022
@sneridagh sneridagh deleted the cleanupbefore4.0.0 branch January 20, 2022 10:15
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.

3 participants