Hello,
as both SIP Express Router (SER) and Kamailio (OpenSER) projects have now the sources in the same GIT repository hosted by http://sip-router.org, next week the devel lists specific for each project (serdev@lists.iptel.org and devel@lists.kamailio.org) will be unified with sr-dev@lists.sip-router.org.
In this way, new commits to the code, discussions about present and future development versions will be in one place. Current ML addresses will be aliased to sr-dev@lists.sip-router.org, so they will still be reachable. The archives to the date will stay independent, new registration will be directed to sr-dev.
The whole process should be transparent to all existing subscribers, however, if you experience downtime, please be patient a bit, but if the issues last for long time, please report to me. The planned time for migration is Monday/Tuesday next week. .
Cheers, Daniel
Hello,
just a reminder ...
Cheers, Daniel
On 05/21/2009 12:43 PM, Daniel-Constantin Mierla wrote:
Hello,
as both SIP Express Router (SER) and Kamailio (OpenSER) projects have now the sources in the same GIT repository hosted by http://sip-router.org, next week the devel lists specific for each project (serdev@lists.iptel.org and devel@lists.kamailio.org) will be unified with sr-dev@lists.sip-router.org.
In this way, new commits to the code, discussions about present and future development versions will be in one place. Current ML addresses will be aliased to sr-dev@lists.sip-router.org, so they will still be reachable. The archives to the date will stay independent, new registration will be directed to sr-dev.
The whole process should be transparent to all existing subscribers, however, if you experience downtime, please be patient a bit, but if the issues last for long time, please report to me. The planned time for migration is Monday/Tuesday next week. .
Cheers, Daniel
On Thursday 21 May 2009, Daniel-Constantin Mierla wrote:
as both SIP Express Router (SER) and Kamailio (OpenSER) projects have now the sources in the same GIT repository hosted by http://sip-router.org, next week the devel lists specific for each project (serdev@lists.iptel.org and devel@lists.kamailio.org) will be unified with sr-dev@lists.sip-router.org.
In this way, new commits to the code, discussions about present and future development versions will be in one place. Current ML addresses will be aliased to sr-dev@lists.sip-router.org, so they will still be reachable. The archives to the date will stay independent, new registration will be directed to sr-dev.
The whole process should be transparent to all existing subscribers, however, if you experience downtime, please be patient a bit, but if the issues last for long time, please report to me. The planned time for migration is Monday/Tuesday next week. .
Where are sourceforge's tracker mails headed? I reported a bug 25 min ago, but no tracker mail shows up on the sr-dev nor devel@kamailio lists.
On 05/28/2009 05:19 PM, Alex Hermann wrote:
On Thursday 21 May 2009, Daniel-Constantin Mierla wrote:
as both SIP Express Router (SER) and Kamailio (OpenSER) projects have now the sources in the same GIT repository hosted by http://sip-router.org, next week the devel lists specific for each project (serdev@lists.iptel.org and devel@lists.kamailio.org) will be unified with sr-dev@lists.sip-router.org.
In this way, new commits to the code, discussions about present and future development versions will be in one place. Current ML addresses will be aliased to sr-dev@lists.sip-router.org, so they will still be reachable. The archives to the date will stay independent, new registration will be directed to sr-dev.
The whole process should be transparent to all existing subscribers, however, if you experience downtime, please be patient a bit, but if the issues last for long time, please report to me. The planned time for migration is Monday/Tuesday next week. .
Where are sourceforge's tracker mails headed? I reported a bug 25 min ago, but no tracker mail shows up on the sr-dev nor devel@kamailio lists.
it comes to sr-dev, but it was bounced, some filter rule not updated to allow noreply@sourceforge.net...
Should be fixed, Daniel
-
Alex Hermann -
Daniel-Constantin Mierla