Henning Westerholt writes:
i already commited the patch to the trunk, but if you'd like you can
take care
of the backport to the stable branch.
ok, juha
___
Devel mailing list
Devel@lists.openser.org
Bayan Towfiq writes:
The privacy parser is case sensitive, only accepting lowercase privacy
values which causes problems for headers such as:
Privacy: Id
or
Privacy: ID
only
Privacy: id
would be accepted.
can you point to an rfc that tells that case of privacy value does
many of the bugs are dialog module related. i remember also in the past
that dialog module has had lots of issues. what is the conclusion? is
it really a good idea for proxy to know about dialogs?
-- juha
___
Devel mailing list
Henning Westerholt writes:
according to RFC 2234, section 2.3 are terminal values enclosed in strings
defined as case-insensitive. Both 3261 and 3325 referring to this syntax
definition. I also read some discussion on sip-implementors about this [1].
So i thought the patch is correct.
Dan Pascu writes:
I'm really intrigued by this stance. If something has/had bugs, it means
it is a bad idea?
dan,
my post was not intended to offense anyone. i just noticed a fact and
was wondering why dialog module has had more problems than other
modules.
-- juha
Revision: 4454
http://openser.svn.sourceforge.net/openser/?rev=4454view=rev
Author: juhe
Date: 2008-07-07 11:21:23 -0700 (Mon, 07 Jul 2008)
Log Message:
---
* Turned no information available for dpid message from error to debug.
Modified Paths:
--
Revision: 4455
http://openser.svn.sourceforge.net/openser/?rev=4455view=rev
Author: juhe
Date: 2008-07-07 11:24:47 -0700 (Mon, 07 Jul 2008)
Log Message:
---
* Added example on module README generation.
Modified Paths:
--
trunk/INSTALL
This was sent by
Henning Westerholt writes:
2) Review all existing issues reported on the tracker and fix them. Release
1.4.0 when ready.
i like this one, i.e., do not set a fixed date. we could classify,
which items (bugs, missing documentation) are release critical and then
release 1.4, when those are
Raúl Alexis Betancor Santana writes:
IHMO, no fixed date to relase means ... no release, because there are
allways bugs to solve.
sure, but there should not be release critical (severe) ones that we are
aware of.
- juha
___
Devel mailing list
Klaus Darilion writes:
do it need a certain library/debian package?
# make modules-readme modules=tlsops
docbook xml to html: tlsops.xml
warning: failed to load external entity
/usr/share/xml/docbook/stylesheet/nwalsh/html/docbook.xsl
yes it does. go to debian packages web site
Daniel-Constantin Mierla writes:
- move radius_config out of the rad_acc define
- set radius_config parameter to null by default, forcing in this way
the set of it in config.
second option is fine with me. i don't see any reason to have defaults
for any parameters of any modules
Daniel-Constantin Mierla writes:
- when use_domain is 1 - if '@' is missing from AoR, consider all the
time to be just the domain, accept to load records with empty
username
i personally don't have a situation where userpart could be empty.
reading usrloc documentation, i get impression
SourceForge.net writes:
I can fix this by myself, but I want to understand why the default
PATTERN was set to ^sip:.*$.
ovidiu,
i don't know how the above default has been determined, but it does not
have the same effect as NULL from_column value, which matches ANY from
uri.
-- juha
try sending 100 Trying immediately when your proxy receives initial
invite and then later t_relay without it.
-- juha
___
Devel mailing list
Devel@lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/devel
Anatoly Pidruchny writes:
The problem can still occur if UAC manages to send a retransmission for
whatever reason. May be, as suggested by Klaus, a better solution would
be to call t_newtran() before doing time-consuming operations.
yes, you can do that too. in my environment i have
Henning Westerholt writes:
If we include something to insert data in the tables, then we should
go for a generic way like this instead of just using SQL, that only
work for SQL based DBs.
that would be ok with me. each table schema file could then be
associated with an optional data
i did several dialplan tests and so far everything has worked fine.
thanks for a useful module.
one issue came up. is there an official way to insert dialplan
entries to dialplan table when 'openserdbctl create' is executed? i did
a hack and patched scripts/mysql/dialplan-create.sql after
is it ok if i add unique index on table_name to version table?
-- juha
___
Devel mailing list
Devel@lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/devel
Raúl Alexis Betancor Santana writes:
IHMO it have no sense, just because version table is only checked at module
load, any speedup will ocur.
my reason was not speedup, but never mind.
-- juha
___
Devel mailing list
Devel@lists.openser.org
Raúl Alexis Betancor Santana writes:
Ah!, ok .. so .. what other reason is needed to use index over a database
table ? apart from uniqness
in my case it was guaranteeing uniqueness. my script that upgrades
database would have been a bit simpler, but i already made it a bit more
Daniel-Constantin Mierla writes:
I haven't added description about all these broken situations because it
will be long description, but I can provide if someone feels I am not
right (and yes, I may not be right). It is what I found so far, but
fixing it is no longer simple. Let's see
here is one simple example that i would like to know how to write
repl_exp for:
match_exp repl_exp result
^0[1-9]? +358[1-9]
i.e., if number starts with 0[1-9], replace 0 it with +358. currently
dialplan README does not give a glue.
-- juha
Bogdan-Andrei Iancu writes:
This is fine with me - should we split new modules versus design and
arch changes? or keep them together under the same umbrella ?
i would like to keep core design changes at1 month. a new module is not
so critical since it is not mandatory to use it.
-- juha
Revision: 4350
http://openser.svn.sourceforge.net/openser/?rev=4350view=rev
Author: juhe
Date: 2008-06-09 08:43:55 -0700 (Mon, 09 Jun 2008)
Log Message:
---
* Fixed copy/paste error.
Modified Paths:
--
trunk/modules/peering/peering.c
This was sent by the
Bogdan-Andrei Iancu writes:
How much a developer gets involved in the project is his own decision -
but we should not bring everything to a stale just because we need to go
to each developer to ask for an opinion.
IMO this must work like a PUSH and not like PULL.
i didn't propose
Bogdan-Andrei Iancu writes:
- Major commits (new modules, design and architectural changes) no
sooner then one month before the freeze
i propose a shorter time (2 weeks) for new modules.
-- juha
___
Devel mailing list
Devel@lists.openser.org
Dan Pascu writes:
What exactly does not work?
mediaproxy-dispatcher package depends on mediaproxy-common package and
mediaproxy-common depends on, for example, on python-application package
that does not exist in debian etch. this means that
mediaproxy-dispatcher package cannot be installed
Dan Pascu writes:
As for the dependencies, all used packages are publicly available on
cheeseshop.python.org and can be installed, or made packages for debian
etch by those interested to do so.
i have tried that by starting to build the packages from lenny sources
on etch and it does not
when i start twinkle, user sip:[EMAIL PROTECTED] registers itself and subscribes
presence of sip:[EMAIL PROTECTED]
at this point sip:[EMAIL PROTECTED] has not been registered. openser,
however, correctly send notify to sip:[EMAIL PROTECTED] that contains
Subscription-State: active;expires=3600
Dan Pascu writes:
Removing a certain module because someone could not make a debian
package for debian etch (one distribution amongst many), makes little
sense to me, especially when it can be done.
i guess i was not clear. my suggestion was to not include mediaproxy
module to openser
Henning Westerholt writes:
2. Code - regexp
Are there any special reasons that you've included a special regular
expression library in the module? Are there any issues with the posix regexp
support we're using in the core at the moment?
i don't know about anca's reasons, but surely
Bogdan-Andrei Iancu writes:
Yes, that was the main reason for using the trex lib - it was easier to
hack to use shared mem from openser. Otherwise, we could not reload data
at runtime. Also, trex is much simpler (and faster) as posix regexp - it
does not have all the functionalities of
Bogdan-Andrei Iancu writes:
The errors you are seeing are a result of the new nonce security check
that was added in trunk. See:
http://lists.openser.org/pipermail/users/2008-June/017719.html
Probably you have in the network some UACs that tries to reuse a nonce
for multiple
Anca Vamanu writes:
It was a bug I introduced when adding the feature of not sending
Notifies on Publish for users that were polite-blocked. I have just
committed a patch. Could you update and test again?
anca,
thanks for your fast fix. now notifies are ok.
-- juha
Bogdan-Andrei Iancu writes:
I'm not saying that re-using the nonce is against RFC and that the phone
is broken - I'm saying it is a security issue (stolen credentials) and
rejecting such auth requests does not break anything.
in that case i would say that ERROR level messages should be
trex home age has:
T-Rex is a minimalistic regular expression library written in ANSI C,
supports the following POSIX expressions: ?,*,+,^,$,.,[a-b],() plus the
perl style greedy closures {n} .
does this mean that a list of chars in [] is not supported, e.g.,
one of finnish emergency number
perhaps i should wait for the examples, but i added a single row in
dialplan table:
1 1 10 0 ^0[235689]112 0 112emergency
and then tried
openserctl fifo dp_translate 1 02112
that resulted in
500 command 'dp_translate' failed
and in syslog
localhost /usr/sbin/openser[1563]:
Bogdan-Andrei Iancu writes:
Also, note you are using the wrong match_op value - 1 is for
regexp. Try:
bogdan,
i used 0 because of dialplan.xml:
column id=match_op
namematch_op/name
typeint/type
size11/size
descriptionMatching operator for rule (0-regexp,
Bogdan-Andrei Iancu writes:
Also, note you are using the wrong match_op value - 1 is for
regexp. Try:
it works now. thanks, juha
___
Devel mailing list
Devel@lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/devel
Daniel-Constantin Mierla writes:
I want to ask for one more week of development before freezing 1.4. It
was already postponed 2 days, but last day changes makes me
uncomfortable about this major release.
i have nothing against extending the freeze if that results in a
solution that
i tried new mediaproxy 2.0 and got over 300 MB of warnings (below) to
syslog before i was able to kill media-relay. kill and kill -HUP didn't
work. only kill -KILL finally did it.
no matter what mistake i made, this kind of sysloging does not sound
like a good idea.
-- juha
when i boot my ubuntu pc, media-relay does not start because of this:
Jun 5 12:01:19 localhost media-relay[5837]: [-] fatal error: failed to
create MediaProxy Relay: IP forwarding is not available or not enabled (check
/proc/sys/net/ipv4/ip_forward)
is there some reason why
Henning Westerholt writes:
to be correct, i reverted the commit from Juha that changed the log
level from INFO to DBG. So it should be fine for your requirements.
the real issue behind openser generated infos is still not resolved. as
i have said, there is no limit to the amount of all kind
after adding
echo 1 /proc/sys/net/ipv4/ip_forward
to /etc/init.d/mediaproxy-relay start case media-relay started at boot.
when i made the fist test call i got the errors below. after restarting
relay and dispatcher, the test call worked without problems.
-- juha
Jun 5 12:46:37 localhost
Adrian Georgescu writes:
We though about this and while you could do this by default to make it
easier, it has implications beyond the use of mediaproxy. Enabling ip
forward might conflict with other software or policy (e.g. firewall)
and it might be better or sane to let the
sometimes openser mediaproxy module request times out like this:
Jun 5 14:14:18 localhost media-dispatcher[7180]: [OpenSERControlProtocol,1,]
Issuing update command to relay at 127.0.0.1
Jun 5 14:14:18 localhost media-relay[7196]: [RelayClientProtocol,client]
Received new SDP offer
Jun 5
Iñaki Baz Castillo writes:
Probably because otherwise you get an error with Debian if you do apt-
get install
And the package will remain wrongly installed. I've never seen a deb package
that requires a system configuration option to be installed properly.
perhaps then installing
Dan Pascu writes:
There is a module parameter on the openser mediaproxy module to
configure how much to wait for an answer from the dispatcher. The
default is 500ms, but you can increase that.
ok, i'll do that if i see more timeouts. i have openser, dispatcher and
relay all running on
Henning Westerholt writes:
in order to specify an permant usrloc entry in the database one
should set the expires colum to zero. This is equivalent to a
datetime value of '-00-00 00:00:00' (at least in mysql).
does it matter what the expires date for permanent contacts is because
a
Henning Westerholt writes:
in the past there were some flags defined for this purpose (FL_PERMANENT).
But now its just
#define VALID_CONTACT(c, t) ((c-expirest) || (c-expires==0))
in that case, i suggest that we go back to the flag, because having a
special expire value to indicate a
Henning Westerholt writes:
i agree. But this was changed in rev1242 on 2006-11-2. I don't think
its easy to going now back to this implementation.
but as you show, this hack has bitten you and may bite again. better to
do a proper fix instead.
changing the date value means changing the
Bogdan-Andrei Iancu writes:
-new type of route added (local_route) ; this will be triggered by TM each
time a new internal request is generated.
(still work on progress)
bogdan,
so this will solve the logging issue we are having with presence module,
because then the info message can be
Dan Pascu writes:
Apparently the media-relay output is missing 2 log lines. After it says
that is is listening on the 4 ports, it should also say it has added an
audio stream and started a new session. So from the logs it looks like
the relay started to do something and then just
here is what happens when i reboot my laptop.
distpatcher and relay are started:
Jun 5 19:51:14 localhost media-dispatcher[5828]: [-] Log opened.
Jun 5 19:51:14 localhost media-dispatcher[5828]: [-] Starting MediaProxy
Dispatcher 2.0.1
Jun 5 19:51:14 localhost media-relay[5841]: [-] Log
Dan Pascu writes:
This error and another one you posted, look like you do not have a
default route.
that is correct. default route gets installed by pppd, when i make
connection over gprs to internet. there is no default route before
that, which i think should be ok.
We made some
Dan Pascu writes:
As for bind being started when the relay starts, in debian bind starts
at index 15 while the relay starts at index 21
yes i know, but my bind is using mysql and in debian mysql starts at
index 19 so there is a chicken and egg problem.
-- juha
Dan Pascu writes:
If the default route is missing and there is no explicit relay IP set,
it will not start, instead give you an error message and explain what
you should do.
that is ok, since i'll set relay ip explicitly.
In your case you should probably set the relay IP
Dan Pascu writes:
I have uploaded a new version (2.0.2) which should allow you to set the
relay IP yourself, and also give better error messages if it's not set
and the default IP cannot be determined correctly.
thanks, so far i have not seen any problems with this new release.
-- juha
when i cancel invite, i dispatcher reports error.
-- juha
at invite (use media_proxy):
Jun 5 22:09:45 localhost media-dispatcher[5827]: [OpenSERControlProtocol,3,]
Issuing update command to relay at 127.0.0.1
Jun 5 22:09:45 localhost media-relay[5840]: [RelayClientProtocol,client]
Received
Juha Heinanen writes:
when i cancel invite, i dispatcher reports error.
sorry about that, it was an error in my script. i called
end_media_session twice on cancel.
-- juha
___
Devel mailing list
Devel@lists.openser.org
http://lists.openser.org/cgi
Dan Pascu writes:
If you do not need to do fancy stuff with starting/stopping mediaproxy
for a new branch after a failure, you can use engage_media_proxy() which
works behind the scenes and does all the stuff without you worrying when
and what to call.
i don't find
new mediaproxy module in trunk has replaced the old module. i'm not
sure if this is a good idea, because it makes impossible to use
mediaproxy in current stable debian distribution (etch). the module
itself, of course, works, but dispatcher, which requires local socket to
talk to openser, does
Revision: 4298
http://openser.svn.sourceforge.net/openser/?rev=4298view=rev
Author: juhe
Date: 2008-06-03 01:00:37 -0700 (Tue, 03 Jun 2008)
Log Message:
---
* Fixed AVP in example.
* Added branch_route to route blocks, where verify_destination() and
verify_source() can
Henning Westerholt writes:
If you run openser with debug=3 then all info, notice and other debug
statements will be end up in your log.
henning,
you are right. i was too busy when i wrote the email. debug level of
openser generated info's should be between info and debug level. then i
Bogdan-Andrei Iancu writes:
If you do not want to split, that you have to accept that the C code may
log different messages you are not in control of. And as said, the only
working solution will be to play with the log level and to try to use
from script a higher level in order to
Henning Westerholt writes:
then lets go with notice in this case. But there are also quite a lot of
module that uses info for similar statements. I don't like the idea of
artificially separating the logging from script and code. We use for example
different log levels even in the
dan,
thanks for the new mediaproxy module and media proxy. one problem:
You don't have permission to access
/MediaProxy/debian/mediaproxy_2.0.0.tar.gz on this server.
-- juha
___
Devel mailing list
Devel@lists.openser.org
Adrian Georgescu writes:
This proxy replaces the need for OpenSER built-in xml-rpc server,
which has
no access list and is prone to crash the server.
adrian,
we earlier had fifo_relay, which i didn't like at all because it
introduced yet another single point of failure to the system. i
Adrian Georgescu writes:
Try now again
got it now. i noticed that build dependency on
libnetfilter-conntrack-dev
was missing. perhaps you could add it. there may be corresponding
install dependencies also missing, but i'm not that far yet.
-- juha
dan,
i also noticed that without debian/pyversions file, ubuntu hardy makes
these kinds of complains:
pyversions: missing XS-Python-Version in control file, fall back to
debian/pyversions
i got rid of them by creating debian/pyversions containing a single line
2.5
-- juha
Revision: 4282
http://openser.svn.sourceforge.net/openser/?rev=4282view=rev
Author: juhe
Date: 2008-05-30 03:33:45 -0700 (Fri, 30 May 2008)
Log Message:
---
* Introduced peering module (see README).
* Removed V_EMERGENCY_CALL radius.h value which is not used by any
Henning Westerholt writes:
INFO:
used for informational messages that are emmited during normal operation,
should be understandable from users, to give an indicator about the
performed operations of the server, e.g. proceeded messages, routing
descisions, startup informations
i agree
Revision: 4284
http://openser.svn.sourceforge.net/openser/?rev=4284view=rev
Author: juhe
Date: 2008-05-30 04:32:47 -0700 (Fri, 30 May 2008)
Log Message:
---
* Added peering module to debian packages.
Modified Paths:
--
trunk/packaging/debian/rules
Henning Westerholt writes:
I understand your requirement, but there is a lot of code in the server that
does already the same. So this change is not the first one that would affect
your clean setup, if you would use a different set of modules.
it was the first one that hit me.
I
Dan Pascu writes:
This is already possible using the MI debug function.
node04:~# openserctl fifo debug 7
DEBUG:: 7
node04:~# openserctl fifo debug 3
DEBUG:: 3
node04:~#
thanks dan. any idea where this fifo command is documented or by which
module it is implemented?
-- juha
Dan Pascu writes:
I don't know if it's documented or where, but is implemented in MI core
mi/mi_core.c
ok, i'll add a note about it to core cookbook.
-- juha
___
Devel mailing list
Devel@lists.openser.org
Bogdan-Andrei Iancu writes:
my bad - I have to admit sometime I forget about the documentation
after writing the code - I will take care of this and see if the
docs needs to be updated.
bogdan,
i added Core MI Functions section into core cookbook and but debug
there.
-- juha
i would have liked to add an extra header to publish request sent using
pua_publish of pua_mi module, but noticed that the interface doesn't
support it:
1.5.1. pua_publish
Command parameters:
* presentity_uri - e.g. sip:[EMAIL PROTECTED]
* expires - Relative expires time in seconds
Revision: 4261
http://openser.svn.sourceforge.net/openser/?rev=4261view=rev
Author: juhe
Date: 2008-05-28 03:55:37 -0700 (Wed, 28 May 2008)
Log Message:
---
* Noise reduction.
Modified Paths:
--
trunk/modules/presence/notify.c
This was sent by the
Revision: 4260
http://openser.svn.sourceforge.net/openser/?rev=4260view=rev
Author: juhe
Date: 2008-05-28 03:10:18 -0700 (Wed, 28 May 2008)
Log Message:
---
* Added extra_headers parameter to pua_mi/pua_publish function.
Modified Paths:
--
Iñaki Baz Castillo writes:
Hi Juha, could you please explain a little which headers will you add
and the purpose of them? Just curiosity.
for example, that publish is generated internally by sems application
server.
-- juha
___
Devel mailing list
while doing performance tests, i tried to look for a way to change debug
level on the fly using a mi function, but didn't find any. did i
somehow managed to miss such a mi function? description on debug
keyword in core cookbook does not mention about a way to change debug
level.
i know that i
Edson writes:
It would be even better if this control could be done not only through MI
commands, but also through script commands/variable. It would permit
increase and decrease debug level based on script logic given a more
granular control over debug info.
that should be possible if
if entry proxy, e.g., load balancer, needs to forward request using
t_relay to a backend proxy that actually handles the request, doesn't
that cause a bottleneck at the load balancer, because it now ties up a
process at the load balance until reply comes back from the backend
proxy?
-- juha
347module keeps its internal state about endpoints that need
348keepalive, state that is build while messages are processed by
349the proxy and thus it doesn't need to transfer any information
350from the usrloc module, which should also improve its
351efficiency.
Dan Pascu writes:
IMO this is a poor design to have the internal consistency of the program
depend on the way an external MI command is issued.
i agree that there those operations should be locked. i just have not
had any need for locking in the environment where i use those modules.
Henning Westerholt writes:
If we can't improve the API for 1.4, then the easiest thing would be to
introduce a small #ifdef around this statement, revert to the previous state
and remove the mysql wrapper function.
henning,
i was also thinking this morning an #ifdef to solve this
Dan Pascu writes:
My idea was that each db module can offer functions like:
inline str bitand(int a, int b)
{
}
for mysql and postgres they can return a b for oracle they can
return bitand(a, b) and so on.
this sounds good to me.
-- juha
while testing usrloc db_mode=3, i'm getting these kind of errors:
May 13 00:31:25 Etch-3 /usr/sbin/openser[3985]:
ERROR:db_mysql:db_mysql_submit_query: driver error on query: FUNCTION
ser.bitand does not exist
May 13 00:31:25 Etch-3 /usr/sbin/openser[3985]: ERROR:core:db_do_raw_query:
error
Juha Heinanen writes:
while testing usrloc db_mode=3, i'm getting these kind of errors:
May 13 00:31:25 Etch-3 /usr/sbin/openser[3985]:
ERROR:db_mysql:db_mysql_submit_query: driver error on query: FUNCTION
ser.bitand does not exist
the query looks like this:
select received, contact
wrong bitand function was introduced here:
http://openser.svn.sourceforge.net/viewvc/openser?view=revrevision=3973
i don't know bitand could be changed to bit_and or would the change
break some other db?
-- juha
___
Devel mailing list
Iouri Kharon writes:
May 13 00:31:25 Etch-3 /usr/sbin/openser[3985]:
ERROR:db_mysql:db_mysql_submit_query: driver error on query: FUNCTION
ser.bitand does not exist
You must recreate base. See scripts/openserdbctl.mysql line ~135.
iouri,
i'm not sure i like this. this select is
Revision: 4131
http://openser.svn.sourceforge.net/openser/?rev=4131view=rev
Author: juhe
Date: 2008-05-08 03:15:19 -0700 (Thu, 08 May 2008)
Log Message:
---
* Privacy values are separated by semicolon instead of comma.
Modified Paths:
--
Iñaki Baz Castillo writes:
What about SIP TCP signalling? does the new module implement any way to
mantain the keepalive in a TCP connection using CRLF or anything?
i don't think that is necessary, because tcp keepalives are handled by
the core once the patch that klaus submitted is
Iñaki Baz Castillo writes:
I didn't know about it. Please, could you point me to that patch or its
description? (or just revision number).
http://sourceforge.net/tracker/index.php?func=detailaid=1920843group_id=139143atid=743023
-- juha
___
Revision: 4125
http://openser.svn.sourceforge.net/openser/?rev=4125view=rev
Author: juhe
Date: 2008-05-07 10:46:33 -0700 (Wed, 07 May 2008)
Log Message:
---
* Added group_id parameter to allow_address function, which is now
possible when there can be more that two
Bogdan-Andrei Iancu writes:
I found it more natural to be on (as if there is no TCP ping, openser
will not do anything more). Also it will much easier for the users to
use TCP as they do not have to get into dirty details to make it
work.
bogdan,
my wording was not clear. i meant to
Henning Westerholt writes:
yes, this was possible before the migration. I did not wanted to introduce
some sed hacks to emulate the past behaviour, as i don't considered this
functionality that much important/ widely used this time. If someone
want
change the default table type, all
i had in openser.cfg
alias=etch-2.test.fi:5060
and got syntax errors:
May 6 13:55:45 [3652] CRITICAL:core:yyerror: parse error in config file, line
291, column 12-13: syntax error
May 6 13:55:45 [3652] CRITICAL:core:yyerror: parse error in config file, line
291, column 12-13: hostname
Henning Westerholt writes:
we've agreed some time ago that the feature freeze for 1.3.0 will be begin
at end of may. Just to have a more exact date i propose that we
freeze the svn trunk and start the testing period on the 3th June
(four weeks from now).
sounds fine to me.
-- juha
1 - 100 of 205 matches
Mail list logo
