20 Oct
2009
20 Oct
'09
11:44 p.m.
On 20.10.2009 21:48 Uhr, Andrei Pelinescu-Onciul wrote:
Andrei
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
Daniel-Constantin Mierla
* Kamailio SIP Masterclass, Nov 9-13, 2009, Berlin
* http://www.asipto.com/index.php/sip-router-masterclass/
On Oct 20, 2009 at 22:10, Juha Heinanen
<jh(a)tutpro.com> wrote:
I think will complicate the life right now for something that does not
bring a major benefit, considering we are in freeze state. It is a long
debate to start right now. Next release that should be a better
integrated one, hopefully with some modules merged (sl, rr, and some
other like them) will take care of having unique modules moved.
Therefore I prefer that sr_3.0 and k_3.0 stay in this state.
Cheers,
Daniel
Andrei Pelinescu-Onciul writes:
Well, it might break packaging scripts and who knows what else.
I personally have nothing against moving it, but everybody working on
sr_3.0 or k3.0 should agree (it won't be nice to break packaging on k3.0
the next time it is merged from sr_3.0).
We are in freeze and this would complicate merges
from master to sr_3.0
a little (unless we want to propagate the change in sr_3.0 which I
don't think it's a good idea at this point).
i meant that the move is done in sr_3.0, not in master and then
propagated from sr_3.0 to master.
Apart from that IMHO k developer should decide if pv
is ready/should be
moved.
yes, if developer is still around.