No subject

till September. We have a lot of modules we have not even began to
discuss, we have completely different DB schemes a.s.o.

So while the goal is to completely merge kamailio and ser under
sip-router (with perhaps some duplicate modules), it will take a while
(hopefully 1 extra release cycle will be enough).

> 
> if that will not be the case, it would have made no sense to start
> putting all kinds of migration documentation there.  we should have
> simply kept on using the k site and update the docs there.
> 
> if you plan to keep on using name kamailio, then you can do whatever
> name changes you want there when you package next version of kamailio.
> i'm not going to be any part of that, but keep on using and contributing
> only to sip router project.
> 
> regarding modules, everyone can pick from modules subdirs whatever
> modules they like to use.  over time it would make sense to try to unite
> k and ser modules when feasible in order to save maintenance resources.

Yes, there is a lot of work ahead of us (discuss on a module by module
basis, decide on the DB schema, new module interface a.s.o.) but we'll
slowly get there. So far at least from my point of view the priority is
to be able to build a stable kamailio and ser distributions out of
sip-router.


Andrei