Hi all, Not releasing 14 wouldn't make sense to me. Skipping releases never looks good, as it either means that there hasn't been enough contributions or that there are no proper release strategies in place. Neither make the community or the or the product look good to outsiders.
I can understand that one would want to drop support for 13, but i would argue that at least 14 should be kept as it seems stable and could act as a version that eases the transition to gradle. Then 15 would be 14 + gradle support and 16 a proper new release. The reason i argue for this is also that our client installations rely on some sort of migration plan. Just calling end-of-life on a product and then moving forwards is hell for them, as it practically means that they will have to pay for a more stressful migration if they want to keep receiving security bugfixes. So i hope i can convince the rest of you to think this over. Regards, Paul -- View this message in context: http://ofbiz.135035.n4.nabble.com/DISCUSSION-Anticipate-the-end-of-life-of-the-13-07-branch-and-backport-some-non-bug-related-changes-s-tp4686668p4686803.html Sent from the OFBiz - User mailing list archive at Nabble.com.
