Prepare release 2.3.0

[petschki]

Note: if this all goes green, then mockup==5.4.0 will be released, before merging this. But there are likely some robottests breaking here right now.

@pgrunewald I put you in CC ... maybe you can take a look too.

[mister-roboto]

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

[petschki]

@jenkins-plone-org please run jobs

[pgrunewald]

I just tested it locally. It has all the changes and works. I just noticed a little visual glitch:

The icon somehow duplicates sometimes (not everytime) on initial load of folder_contents. I'm not aware that the new code does anything special. Maybe it's something on my setup/browser. Besides of that, functionally it works as expected and is already a good improvement.

[pgrunewald]

I leave my approval. Unless the visual glitch is just for me or is tolerable for the moment, it'd be good to go.

[pgrunewald]

@petschki The changelog entry is missing. Can you please add one for this release?

[petschki]

Yes of course. I just wanted to release a final mockup 5.4.0 before making this ready. Will do now.

[mauritsvanrees]

LGTM when I try it out.

Jenkins is green, except for one job which has one test error: "Could not connect to the playwright process at port 39747." That seems safe to ignore.

[petschki]

I'll release 2.3.0 now

[petschki]

Released 2.3.0 ... thanks @pgrunewald for this improvement. Really appreciated!