Hi Pierre Thanks for starting the discussion. I had expected to start it this week, giving us time to continue stabilising and consolidating the gradle work in the trunk from last week. (Also a minor correction â I 'suggested' not 'promised').
Anyway my suggestion was to take the discussion to this list to talk about the next steps. So just as a recap from the user mailing list, my summary of the discussion there included the following points that are relevant to the 14.12 and 15.12 unreleased branches. 1) - We would not backport any of the gradle changes into the 14.12. or 15.12 branches because it would cause instability 2) - We would leave 14.12 and 15.12 as unreleased branches as they are now (and not make them into releases as to do that we would need to remove all the jar files and this would create instability). 3) - The benefits for our community are that developers and service providers will still have access to the complete codebase for 14.12 and 15.12 including the special purpose components to be able to support their client base. My understanding was that the community did reach a consensus on these points. No-one responded to correct, update nor oppose any of these points. Both of your questions are answered by the second point. So based on this the responses to your questions are: - No, we are not going to delete the external libraries from the unreleased branches 14.12 and 15.12 (if they remain as unreleased branches the there is no need to remove the external jars) - No, we are not going to delete the entire unreleased branches 14.12 and 15.12 (we are leaving these available so that our community will still have access to the complete codebase including the special purpose components) In fact the main discussion that I wanted to start here was more related to support for 14.12 and 15.12. As we are in transition to gradle, we need to define a time period for backporting bug fixes into these unreleased branches. As an initial suggestion â would 12 months be a good timeframe to work with. What do other people think? Thanks Sharan On 2016-07-10 10:48 (+0200), Pierre Smits <pierre.sm...@gmail.com> wrote: > Hi all, > > Sharan promised the greater community in the '[*[DISCUSSION]* *Anticipate* > the *end* of *life* of the *13.07* branch and backport some non-bug > related changes to the 14.12 and 15.12 branches > <http://markmail.org/message/nqo5xacngpspytvf>' starting via > http://ofbiz.markmail.org/message/nqo5xacngpspytvf ) that the discussion > would continue in the dev ml. > > As I haven't seen her start that discussion, I will: > > Given that Sharan made clear that external libraries as per ASF guidelines > and rulings, we need to decide what to do with the r14.x and the r15.x > branches, as these hold all the external libraries required to build, test > and/or run a copy from that branch in a separate environment. > > > So the questions are: > > > - are we going to delete the external libraries from the branches, or > - are we going to delete the entire branches? > > > I believe we should have this addressed in order to provide the greater > community with a clear answer as what to expect regarding future adoptions > and/or upgrades. > > Best regards, > > > Pierre Smits > > ORRTIZ.COM <http://www.orrtiz.com> > OFBiz based solutions & services > > OFBiz Extensions Marketplace > http://oem.ofbizci.net/oci-2/ >
