Hi Taher, we do not have a precise strategy yet but one direction we could follow is to release specialpurpose components separately from releases. For example, the current svn layout is the following:
trunk/ trunk/applications/ trunk/framework/ trunk/specialpurpose/ release13.07/ release13.07/applications/ release13.07/framework/ We could switch to a layout like: trunk/ trunk/ofbiz/applications/ trunk/ofbiz/framework/ trunk/specialpurpose/ release13.07/ release13.07ofbiz/applications/ release13.07/ofbiz/framework/ release13.07/specialpurpose/ When we will issue an OFBiz release from 13.07, for example "apache-ofbiz-13.07.03", we will only include: release13.07ofbiz/ (i.e. applications and framework exactly as it is now in the 13.07 branch) But we could also release, if there is interest, individual specialpurpose components compatible with a given release; for example "apache-ofbiz-pos-13.07.03", including: release13.07/specialpurpose/pos Jacopo On Jan 11, 2014, at 7:11 AM, Taher Alkhateeb <[email protected]> wrote: > Hello everyone, > > Do we have a certain strategy with respect to the guarantee of > specialpurpose components' compatibility with any release given that they > only reside in trunk due to slim down? > > And if the guarantee is not there, do we have any tag on svn to checkout > the latest compatible version for a given release? I know we only have > 13.07 but I think it might get out of control in a few releases right? > > I would appreciate your thoughts on this. > > Taher Alkhateeb
