Remove DeprecationWarning from a moved p.a.z3cform.widgets import

[jensens]

No description provided.

[mister-roboto]

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

[jensens]

@jenkins-plone-org please run jobs

[jensens]

@jenkins-plone-org please run jobs

[jensens]

@jenkins-plone-org please run jobs

[jensens]

@jenkins-plone-org please run jobs

[jensens]

@jenkins-plone-org please run jobs

[petschki]

CI tests for 6.0 should be dropped as this change targets Plone 6.1 only

[davisagli]

@petschki If there are changes which are for 6.1 only, then a new maintenance branch needs to be created from current master and set as the source in https://github.com/plone/buildout.coredev/blob/6.0/sources.cfg /cc @mauritsvanrees

Then something needs to happen to make mr.roboto notice the change -- is that manual or automatic @gforcada?

[petschki]

branches from sources.cfg are picked automatically by mr.roboto ... @jensens could you create a maintenance branch here?

[jensens]

@jenkins-plone-org please run jobs

[gforcada]

@davisagli (and everyone anyway), mr.roboto indeed updates the branches automatically.

You can see the matrix of plone version / package / branch used in the following page:

https://jenkins.plone.org/roboto/branches

Note: red means that the package is checked out in checkouts.cfg