I don't think that my argument is a selfish one, Jacques. An end-of-life with R13 is not my proposal, and neither are end of life of either 14 and 15. But given the current direction of this conversation I am convinced that a proper release plan is required and beneficial to all.
The current release promoted up on the website is 13. Calling it quits on it before you even have as much as a next release is not only confusing but also quite unfair to all the people who are basing their work on it. I don't necessarily cling onto any of these versions (as i stated before, i don't see too much difference functionality wise between 9-13), but I do think that a migration plan is the decent thing to do. In particular if you promote the idea of people having to keep up with trunk or any of the svn repositories (which frankly is a matter of time&money) you should allow people a transition phase. Having seen the community promoted 14 and 15 as branches before (instead of the packages), i would argue that perhaps there is a way to keep a straight face while working on a grander release - namely version 16: 1) release 14 to get away from 13 2) use 15 for the gradle upgrade 3) work on 16 as a proper feature release -- 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-tp4686668p4686844.html Sent from the OFBiz - User mailing list archive at Nabble.com.
