<p dir="ltr">The core developers at the moment simply do not have the resources for more than two lines of "official" development:<br>
- one has to be production, the one you use in servers<br>
- one has to be development, the one that will be the next production</p>
<p dir="ltr">Because of effort put into allowong users time for transition, now the core developers are maintaining three lines: 1.6 (production), 1.6 (development), 1.4 (old prodution).</p>
<p dir="ltr">As obvious, in a short time will be necessary for core developers to begin working on next release (1.8).</p>
<p dir="ltr">Because resources are finite, is not possible to ask core developers for maintaining an LTS as part of the community project.</p>
<p dir="ltr">On the contrary, I believe this LTS thing can be a source of revenue for a maintainer, or a company.</p>
<p dir="ltr">Is a matter of taking care of security and bug fixes in a software version you would not use, because is stale. Someone else is making money from that version you would not use, and is asking you to help him milking.</p>
<p dir="ltr">I believe that if there is enough commercial, paying interest in an LTS, a single maintainer or a company will step out to take care of it. Or maybe this revenue stream can allow for the.core developers to hire someone for this purpose.</p>
<p dir="ltr">Anyway, I believe that the key is showing a paying interest.</p>
<p dir="ltr">So, how to do it? </p>
<p dir="ltr">Crowfounding, kickstarter, etc... I'm not an expert, but those days I believe is simple to assure there are money for a project.</p>
<p dir="ltr">-giovanni</p>
<p dir="ltr">sent from my mobile,<br>
Giovanni Maruzzelli<br>
cell: +39 347 266 56 18</p>
<div class="gmail_quote">Il 22/Nov/2015 09:12, "ik" <<a href="mailto:idokan@gmail.com">idokan@gmail.com</a>> ha scritto:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div><div><div><div>Hello,<br><br></div><br></div>It seems that every single year there is a new EOL (end of life) of FS version (e.g. 1.4 at this time) and a new version series that replaces it (e.g. 1.6).<br><br></div>The problem is that it's not a simple act to update production servers.<br></div>When you have a lot of servers (in different clients and locations) it's even harder.<br><br></div>Many products, including Linux, and even Asterisk have LTS versions, and newer releases versions.<br></div>The new releases has new features and way to do stuff, but the LTS get bug fixes and are stable for long period of time (usually 5 years).<br><br></div>What does it take to have LTS version with FS, that the new releases will not stop, but EOL will be much longer for some of it's versions?<br><br></div>Are there any plans for such things?<br>How we as a community can help?<br></div><br><br></div>Ido<br></div>
<br>_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
<a href="http://www.freeswitchsolutions.com" rel="noreferrer" target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a href="http://www.freeswitch.org" rel="noreferrer" target="_blank">http://www.freeswitch.org</a><br>
<a href="http://confluence.freeswitch.org" rel="noreferrer" target="_blank">http://confluence.freeswitch.org</a><br>
<a href="http://www.cluecon.com" rel="noreferrer" target="_blank">http://www.cluecon.com</a><br>
<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" rel="noreferrer" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" rel="noreferrer" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" rel="noreferrer" target="_blank">http://www.freeswitch.org</a><br></blockquote></div>