Hello,
it's being quite some time since we released 3.1.4, so I am thinking of packaging soon v3.1.5 out of stable branch 3.1. My plan is to release it Wednesday, September 14, 2011. Any other opinions?
Cheers, Daniel
El Thu, 08 Sep 2011 17:16:24 +0200 Daniel-Constantin Mierla miconda@gmail.com escribió:
Hello,
it's being quite some time since we released 3.1.4, so I am thinking of packaging soon v3.1.5 out of stable branch 3.1. My plan is to release it Wednesday, September 14, 2011. Any other opinions?
Cheers, Daniel
There's a bug in the dialog module (146) but I don't know if it will be handled in 3.1 branch. Don't think it's release critical neither.
http://sip-router.org/tracker/index.php?do=details&task_id=146
What I would check is how many of the critical-medium reported issues afect 3.1 branch. I would not release a stable version with medium+ reported issues opened.
http://sip-router.org/tracker/index.php?project=1&do=index
my 0.02€
On 13.09.2011 16:50, Jon Bonilla wrote:
El Thu, 08 Sep 2011 17:16:24 +0200 Daniel-Constantin Mierla miconda@gmail.com escribió:
Hello,
it's being quite some time since we released 3.1.4, so I am thinking of packaging soon v3.1.5 out of stable branch 3.1. My plan is to release it Wednesday, September 14, 2011. Any other opinions?
Cheers, Daniel
There's a bug in the dialog module (146) but I don't know if it will be handled in 3.1 branch. Don't think it's release critical neither.
http://sip-router.org/tracker/index.php?do=details&task_id=146
I had been working on this bug but got interrupted by other tasks. Once done, my plan is to push the finished work to both master and 3.1 as it qualifies as a bug fix IMHO. (The dialog module is violating the standard in this particular regards.)
It'll certainly take a little more time to finish though, so it's not going to be part of tomorrow's 3.1.5 release. In accordance with Jon's opinion, however, I agree that it isn't mission-critical. After all, people have been using the module with the bug as it was already there from the very start of the module's lifetime. :)
Cheers,
--Timo
On 9/13/11 5:10 PM, Timo Reimann wrote:
On 13.09.2011 16:50, Jon Bonilla wrote:
El Thu, 08 Sep 2011 17:16:24 +0200 Daniel-Constantin Mierlamiconda@gmail.com escribió:
Hello,
it's being quite some time since we released 3.1.4, so I am thinking of packaging soon v3.1.5 out of stable branch 3.1. My plan is to release it Wednesday, September 14, 2011. Any other opinions?
Cheers, Daniel
There's a bug in the dialog module (146) but I don't know if it will be handled in 3.1 branch. Don't think it's release critical neither.
http://sip-router.org/tracker/index.php?do=details&task_id=146
I had been working on this bug but got interrupted by other tasks. Once done, my plan is to push the finished work to both master and 3.1 as it qualifies as a bug fix IMHO. (The dialog module is violating the standard in this particular regards.)
It'll certainly take a little more time to finish though, so it's not going to be part of tomorrow's 3.1.5 release. In accordance with Jon's opinion, however, I agree that it isn't mission-critical. After all, people have been using the module with the bug as it was already there from the very start of the module's lifetime. :)
Indeed, this is not a show stopper, dialog module has several things at the border between required enhancement/bug, many from the first day. That's life in sip, sometimes must is shoud, should is may, may is june :-)
Cheers, Daniel
Daniel-Constantin Mierla writes:
Indeed, this is not a show stopper, dialog module has several things at the border between required enhancement/bug, many from the first day. That's life in sip, sometimes must is shoud, should is may, may is june :-)
especially with dialog module, which in my opinion should not be part of sip proxy at all. better to use sems for that kind of stuff.
-- juha
Hi Daniel, Would it be possible to backport the patch from trunk to fix via branch value in ack to 200 ok.
The specific commit is: ebb3b085c15b398192cd8e242d46914252278448
It seems that this would be fairly trivial and shouldn't break anything for 3.1.x users.
Thanks, Spencer
On Sep 8, 2011, at 10:16 AM, Daniel-Constantin Mierla wrote:
Hello,
it's being quite some time since we released 3.1.4, so I am thinking of packaging soon v3.1.5 out of stable branch 3.1. My plan is to release it Wednesday, September 14, 2011. Any other opinions?
Cheers, Daniel
-- Daniel-Constantin Mierla -- http://www.asipto.com Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat http://linkedin.com/in/miconda -- http://twitter.com/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Hello,
Ok, I will look over it.
Cheers, Daniel
On Sep 14, 2011, at 6:37 AM, Spencer Thomason spencer@5ninesolutions.com wrote:
Hi Daniel, Would it be possible to backport the patch from trunk to fix via branch value in ack to 200 ok.
The specific commit is: ebb3b085c15b398192cd8e242d46914252278448
It seems that this would be fairly trivial and shouldn't break anything for 3.1.x users.
Thanks, Spencer
On Sep 8, 2011, at 10:16 AM, Daniel-Constantin Mierla wrote:
Hello,
it's being quite some time since we released 3.1.4, so I am thinking of packaging soon v3.1.5 out of stable branch 3.1. My plan is to release it Wednesday, September 14, 2011. Any other opinions?
Cheers, Daniel
-- Daniel-Constantin Mierla -- http://www.asipto.com Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kat http://linkedin.com/in/miconda -- http://twitter.com/miconda
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-
Daniel-Constantin Mierla -
Daniel-Constantine Mierla
-
Jon Bonilla -
Juha Heinanen -
Spencer Thomason -
Timo Reimann