Remove wrong bundle with typo

petschki commented 3 years ago

fixes #121

petschki commented 3 years ago

p.staticresources 1.4.1 got released for Plone 5.2.3, so 5.2-latest should be on version 12 too ...

thet commented 3 years ago

@petschki you're right. In this case we can safely merge this PR to master and to 1.x at the same time. However the following is not solved, but also tangles not this PR:

We're missing an upgrade step for the barceloneta-lts changes on master. Okay-ish for now, as barceloneta-lts is a work in progress.
What should we do with profile version numbers when we maintain 2 branches of a package? If the barceloneta-lts upgrade step would for example get the version number 14, but profile version should a upgrade step in the 1.x branch get? Thinking about this, maybe we should increase the profile version of plone.staticresources in master branch after merging this PR to 100 or so? Or maybe we should use the same version numbers as for the pypi release? That's a more general question but just came up for me.

thet commented 3 years ago

Oh fine, I just found out that metadata versions were already out of sync in 1.x and master :grimacing: Both have upgrades for versions 12 but those are just different upgrades. I will fix that in anther PR.

petschki commented 3 years ago

@mauritsvanrees do you know why this master branch did not get checked with Jenkins PR 6.0 ?

mauritsvanrees commented 3 years ago

@mauritsvanrees do you know why this master branch did not get checked with Jenkins PR 6.0 ?

I think there is still stuff missing in Jenkins and/or mr.roboto, or the work is done and the servers need to be updated. See for example https://github.com/plone/jenkins.plone.org/issues/275

plone / plone.staticresources

Remove wrong bundle with typo #122