Hello,
Based on our project policy to support officially the last two stable branches, I was thinking of packaging kamailio 1.5.5 to mark its end. New fixes will go to svn if it is the case, but no new release in 1.5.x series will be done.
Also, since testing for 3.1.0 brought some fixes to 3.0.x, we should do as well 3.0.4. My proposal is next week, Wednesday, Oct 20.
Don't forget to report issues you are aware for these two branches.
Cheers, Daniel
2010/10/14 Daniel-Constantin Mierla miconda@gmail.com:
Hello,
Based on our project policy to support officially the last two stable branches, I was thinking of packaging kamailio 1.5.5 to mark its end. New fixes will go to svn if it is the case, but no new release in 1.5.x series will be done.
Hi, is it possible to commit some "featured" changes for 1.5.5? or just security fixes?
Regards.
On 10/14/10 10:19 AM, Iñaki Baz Castillo wrote:
2010/10/14 Daniel-Constantin Mierlamiconda@gmail.com:
Hello,
Based on our project policy to support officially the last two stable branches, I was thinking of packaging kamailio 1.5.5 to mark its end. New fixes will go to svn if it is the case, but no new release in 1.5.x series will be done.
Hi, is it possible to commit some "featured" changes for 1.5.5? or just security fixes?
stable branches are for bug fixes. New features can be committed in development branches, otherwise will introduce instability to stable branches for people relying on them.
Cheers, Daniel
2010/10/14 Daniel-Constantin Mierla miconda@gmail.com:
Hi, is it possible to commit some "featured" changes for 1.5.5? or just security fixes?
stable branches are for bug fixes. New features can be committed in development branches, otherwise will introduce instability to stable branches for people relying on them.
Sure, I just meant a very small change in a module (regex). I use it in production for long months with no problems, so I wonder if it could be commited in 1.5.5 so I wouldn't need to modify the sources in new deployments :)
El Thu, 14 Oct 2010 10:26:41 +0200 Iñaki Baz Castillo ibc@aliax.net escribió:
2010/10/14 Daniel-Constantin Mierla miconda@gmail.com:
Hi, is it possible to commit some "featured" changes for 1.5.5? or just security fixes?
stable branches are for bug fixes. New features can be committed in development branches, otherwise will introduce instability to stable branches for people relying on them.
Sure, I just meant a very small change in a module (regex). I use it in production for long months with no problems, so I wonder if it could be commited in 1.5.5 so I wouldn't need to modify the sources in new deployments :)
I think that's a bad idea. There are lots of running installations that have their standard kamailio and even their own patches. Including new features, or behaviour changes could affect running systems in ways we cannot anticipate.
Jon Bonilla (Manwe) writes:
Sure, I just meant a very small change in a module (regex). I use it in production for long months with no problems, so I wonder if it could be commited in 1.5.5 so I wouldn't need to modify the sources in new deployments :)
I think that's a bad idea. There are lots of running installations that have their standard kamailio and even their own patches. Including new features, or behaviour changes could affect running systems in ways we cannot anticipate.
i agree. what i do is that i build my own deb packages where i apply my own patches to the source if necessary to backport something.
-- juha
Hello,
I will start packaging these releases soon. Please write me first if you need to commit something to these branches.
Thanks, Daniel
On 10/14/10 9:52 AM, Daniel-Constantin Mierla wrote:
Hello,
Based on our project policy to support officially the last two stable branches, I was thinking of packaging kamailio 1.5.5 to mark its end. New fixes will go to svn if it is the case, but no new release in 1.5.x series will be done.
Also, since testing for 3.1.0 brought some fixes to 3.0.x, we should do as well 3.0.4. My proposal is next week, Wednesday, Oct 20.
Don't forget to report issues you are aware for these two branches.
Cheers, Daniel
-
Daniel-Constantin Mierla -
Iñaki Baz Castillo -
Jon Bonilla -
Juha Heinanen