<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'Lucida Console'; font-size:9pt; font-weight:400; font-style:normal;">On Montag, 6. Juli 2009, Alex Balashov wrote:<br>
> [..]<br>
> This seems fair enough, but it doesn't adequately explain who sip-router<br>
> is intended for and who Kamailio is intended for, and who should use which<br>
> and why and under what circumstances. It does also seem that most of the<br>
> development and documentation energy is being concentrated into sip-router<br>
> integration, which leaves open the question of what the future of Kamailio<br>
> is.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Hi Alex, Hi Geoffrey,<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>just one small addition with regards to eventual concerns about maintenance:<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>One reason that a lot of the development energy going to sr repository at the moment is that the merge broke some things, and also certain existing functionality from the core were not sufficient documented and such. But apart from the move from svn to git there is no real change with regards to the maintenance of the existing stable kamailio versions. It has always been more or less like that, stable branches should be, well stable. ;-)<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>The 1.5 and 1.4 branches will be maintained as usual, even 1.3 still got a few bug fixes in the last weeks i think. For example we (with our infrastructure) have not migrated to 1.5 yet.. So i don't think there are reasons to fear that this branches will be not maintained anymore, even if a new stable release is out.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Henning</p></body></html>