Hi Paul,
I understand your concern, but seems to me that your answer is selfish. What about your comrades who have based their work on R13.07? They are in the
same situation than you!
OK this is kind of kidding, but see my point? ;)
A last point I always want to mention is, IMO, it's always better to use a branch by directly connecting your work with svn than using a packaged
version. So a compromise would be that instead of using the packaged release, people in your situation could consider connecting their work to svn at
the point (revision) the package they use was created. They would then get the same situation but iwould be able to easier follow the work done by the
community. We would then continue to backport in these branches, opinions?
Cheers
Jacques
Le 28/06/2016 à 22:58, Paul Piper a écrit :
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.
