Re: First migration steps from Plone 4.2 to Plone 4.3 not run because of 4.2 service releases

>> Auch. Sending this to the developers list as people here might be doing more migrations than usual so if
>> you have done migrations recently, maybe check again if these steps have been executed. Filed a ticket
>> as well under https://dev.plone.org/ticket/17336
>> 
>> Would it be enough to put a * in plone.app.upgrade's first UpgradeSteps source to fix this?
>> 
>> 
> Yeah, this looks like a bug in plone.app.upgrade. The source for that 
> step needs to be updated whenever the profile on the 4.2 branch is 
> incremented. Please feel welcome to fix it.
> 
> We can't use * because then it will run on every upgrade (IIRC).

Checking the versions in plone.app.upgrade for v4.2 and the metadata.xml on Products.CMFPlone 4.2.x branch
there's another twist. A clean install of 4.2.7 would set the version to 4213 but if I follow the upgrade steps in

https://github.com/plone/plone.app.upgrade/blob/master/plone/app/upgrade/v42/configure.zcml

the last upgrade step in plone.app.upgrade ends at 4211. Or is the metadata.xml from the installed
Products.CMFPlone always applied as last? In my particular case I was upgrading from 4.2.6 to 4.3.X
where the upgrade log did specify "starting from 4212". 

V41 to V42 does have a continuous numbering, last step in p.a.upgrade (destination=4115) is also the metadata.xml in 
Products.CMFPlone (4115).

With kind regards,

Fred van Dijk
--
Zest - www.zestsoftware.nl
Vasteland 78
3011 BN Rotterdam
Tel: +31 (0)10 2959251


------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk