On Mon, Nov 26, 2012 at 1:57 PM, Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@opensips.org" target="_blank">bogdan@opensips.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<u></u>
<div bgcolor="#ffffff" text="#000000">
<tt>Hi Ali,<br>
<br>
Thanks for feedback - regarding the support for previous releases,
Saul raised the same point as you, and I have to admit I didn't do
the math - 2 release ~= 1 year, which indeed is too short - I mean
this will force an upgrade each year.<br>
<br>
So, we need to somehow get to ~ 2 year lifetime for a release. My
suggestion is to actually set a life span for 2 years.<br>
<br>
Regards,<br>
</tt><div class="im">
<pre cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre></div></div></blockquote><div>What about adding a long term support branch that is released every two years and supported for 2 years, and then a release every 6 months for 'standard' releases. Each standard release would be supported for 1 year. <br>
<br>Something like this, assuming 1.10 is the first long term support:<br>1.10 - Long term support (2 years)<br>1.11 - Standard release (1 year)<br>1.12 - Standard release (1 year)<br>1.13 - Standard release (1 year)<br>1.14 - Long term support (2 years)<br>
<br>Those wanting new features can go for the standard releases, and those looking for stability and better support can stick with the long term support releases. It should strike a decent balance between getting features out the door and support. <br>
<br>Just a thought.<br><br>Regards,<br><br>Ryan<br></div></div>