Large, first-digit version changes in a software system tend to be very disruptive to both the software provider and its users. Versions 2, 3, and 4 of Partner were all marked by major upgrade efforts and lots of frustrating issues as the software was deployed - often maturing during and after deployment.
In order to prevent or at least reduce this disruption, we are introducing 5.0 piecemeal as individual modules, running within a version 4.x Partner System. New software is developed within the 5.0 frameworks, and older, stable frameworks are migrated to 5.0 when appropriate and when resources are available to do so well. The remainder of v4.x remains unaffected and works alongside the new 5.0 code - indeed, the 5.0 code will use much of v4.x until it is ?self hosting? within a pure 5.x system - which may be some years off.
To distinguish these portions in Java, and to allow for better control of backwards compatibility in the future, all v5.x code is placed in Java packages prefixed by com.partnersoft.v5.
Thus, the Boots Platform is stored in the BootsPlatform module, which is compatible with both v4.4 and v4.5 branches of the main Partner system. And its root package in Java is com.partnersoft.v5.boots.