Closed petschki closed 2 years ago
@petschki splitting the commits into 2 releases "breaks" the upgrade step 😝
gosh ... I'll fix that in the new 2.x
branch and make a new release 2.2.3
gosh ... I'll fix that in the new
2.x
branch and make a new release2.2.3
the 2.2.2
release & branch are good, don't worry 👍
The problem is for the next version : we need to declare a new upgrade step & version profile (the old step was just updated by a new commit).
gosh ... I'll fix that in the new
2.x
branch and make a new release2.2.3
the
2.2.2
release & branch are good, don't worry 👍 The problem is for the next version : we need to declare a new upgrade step & version profile (the old step was just updated by a new commit).
I think the upgradestep will break the 5.2 configlet because it places puzzle
into icon_expr
... I'll bump the profile version here up to 2000
and re-target the upgradestep for the configlet.
I think the upgradestep will break the 5.2 configlet because it places
puzzle
intoicon_expr
...
puzzle
icon is not put in the 2.2.2
release/branch (only permission is) :+1
https://github.com/collective/collective.taxonomy/blob/2.x/src/collective/taxonomy/profiles/default/controlpanel.xml
I think now I got it 🙈 sorry for the noise ...
@petschki we should clarify the branches / versions compatibility in README, but otherwise, LGTM 👍
@petschki splitting the commits into 2 releases "breaks" the upgrade step :stuck_out_tongue_closed_eyes: