Hello,
I am thinking of planning to release Kamailio 3.0.0 next Wednesday or day after (October 28 or 29). With some delays, testing is going fine in my side, still some bits to be done, here is what I collected: - taking in consideration $du updates in branch route - import fixes from sr_3.0 branch - complete core statistics and handling of drop reply
I believe is feasible, in the worse case we can package it at respective date and allow a bit more time for testing, but we unfreeze code and can go for new development. I encourage people to start writing migration documents. Let's see other opinions as well.
Cheers, Daniel
On 21.10.2009 11:41 Uhr, Daniel-Constantin Mierla wrote:
Hello,
I am thinking of planning to release Kamailio 3.0.0 next Wednesday or day after (October 28 or 29).
since we still have to add migration documents plus some tweaks and I would like to do more testing before labeling it as stable release, I propose to do a RC tomorrow and delay final 3.0.0 with one week or so.
Cheers, Daniel
Daniel-Constantin Mierla writes:
since we still have to add migration documents plus some tweaks and I would like to do more testing before labeling it as stable release, I propose to do a RC tomorrow and delay final 3.0.0 with one week or so.
as long as $du setting in branch_router is not working, it makes no sense to make a release candidate.
-- juha
On 28.10.2009 10:25 Uhr, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
since we still have to add migration documents plus some tweaks and I would like to do more testing before labeling it as stable release, I propose to do a RC tomorrow and delay final 3.0.0 with one week or so.
as long as $du setting in branch_router is not working, it makes no sense to make a release candidate.
Andrei is working on that.
Daniel
On Oct 28, 2009 at 10:33, Daniel-Constantin Mierla miconda@gmail.com wrote:
On 28.10.2009 10:25 Uhr, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
since we still have to add migration documents plus some tweaks and I would like to do more testing before labeling it as stable release, I propose to do a RC tomorrow and delay final 3.0.0 with one week or so.
as long as $du setting in branch_router is not working, it makes no sense to make a release candidate.
Andrei is working on that.
It's ready, but I would feel more confident with more testing (and I won't be able to do anything about it for the rest of this week).
Do you need drop support for branch routes too?
Andrei
Andrei Pelinescu-Onciul writes:
It's ready, but I would feel more confident with more testing (and I won't be able to do anything about it for the rest of this week).
Do you need drop support for branch routes too?
andrei,
no, i don't need drop in branch routes. i'm myself badly connected after this week for about a month.
-- juha
Andrei Pelinescu-Onciul schrieb:
On Oct 28, 2009 at 10:33, Daniel-Constantin Mierla miconda@gmail.com wrote:
On 28.10.2009 10:25 Uhr, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
since we still have to add migration documents plus some tweaks and I would like to do more testing before labeling it as stable release, I propose to do a RC tomorrow and delay final 3.0.0 with one week or so.
as long as $du setting in branch_router is not working, it makes no sense to make a release candidate.
Andrei is working on that.
It's ready, but I would feel more confident with more testing (and I won't be able to do anything about it for the rest of this week).
Do you need drop support for branch routes too?
would be nice for compatibility reasons
regards klaus
-
Andrei Pelinescu-Onciul -
Daniel-Constantin Mierla -
jh＠tutpro.com -
Klaus Darilion