+1
Am 06.03.2013 19:09 schrieb "Maxim Solodovnik" :
> Dear OpenMeetings Community,
>
> I would like to start a vote about releasing Apache OpenMeetings 2.1.0 RC1
>
> Main changes are covered in the
> Readme:http://svn.apache.org/repos/asf/openmeetings/tags/2.1RC1/README
>
> Full Changelog:
> http:
+1
On Mar 7, 2013 2:40 PM, "Sascha Xander"
wrote:
> +1
> Am 06.03.2013 19:09 schrieb "Maxim Solodovnik" :
>
> > Dear OpenMeetings Community,
> >
> > I would like to start a vote about releasing Apache OpenMeetings 2.1.0
> RC1
> >
> > Main changes are covered in the
> > Readme:http://svn.apache.or
+1
2013/3/6 Maxim Solodovnik
> Dear OpenMeetings Community,
>
> I would like to start a vote about releasing Apache OpenMeetings 2.1.0 RC1
>
> Main changes are covered in the
> Readme:http://svn.apache.org/repos/asf/openmeetings/tags/2.1RC1/README
>
> Full Changelog:
> http://svn.apache.org/rep
Hi,
I'd like to have 2 'sipusers' tables in 2 different databases. The content of
these tables could be different.
So in order to share both data sets between Asterisk and OpenMeetings I create
2 views like this:
echo "create view view_sipusers as select * from sipusers union select * from
${O
Hello Ivan,
I believe that the only "being" able to participate in conference in OM
room is "*user".
This concept is true for links created for "external users" during
integration with various 3rd party CMS systems.
So, as I said before: the best short term solution would be to disable
voting for
I believe it is impossible to rename DB table used by OM without recompiling
Also I'm not sure what is the purpose of such behavior?
You can have your data in OM table
additional rows and columns would not affect anything
On Thu, Mar 7, 2013 at 9:23 PM, Vieri wrote:
> Hi,
>
> I'd like to have 2
+1
07.03.2013 1:09, Maxim Solodovnik пишет:
Dear OpenMeetings Community,
I would like to start a vote about releasing Apache OpenMeetings 2.1.0 RC1
Main changes are covered in the
Readme:http://svn.apache.org/repos/asf/openmeetings/tags/2.1RC1/README
Full
Changelog:http://svn.apache.org/repo
Afaiu:
Allowing others to vote can lead to improper results - someone can vote
several times using hashes
07.03.2013 18:59 пользователь "Maxim Solodovnik"
написал:
> Hello Ivan,
>
> I believe that the only "being" able to participate in conference in OM
> room is "*user".
> This concept is true
+1
2013/3/6 Maxim Solodovnik :
> Dear OpenMeetings Community,
>
> I would like to start a vote about releasing Apache OpenMeetings 2.1.0 RC1
>
> Main changes are covered in the
> Readme:http://svn.apache.org/repos/asf/openmeetings/tags/2.1RC1/README
>
> Full
> Changelog:http://svn.apache.org/repo
@George: I will move that discussion to the vote thread on
dev@openmeetings.apache.org, I don't think that there is a need to put that
private.
About the release process, voting and potential fixes after the release:
A RC is a candidate for a release. If there is no negative vote then it
would be
Just forwarding this email:
The vote about a release happens @dev not on @private
I don't think splitting up into multiple branches in the SVN is needed.
Fixes can happen in trunk (as long as everybody agrees not to commit new
features / or in other words if everybody is happy with just fixing thi
That's a pity :(
I was sure all blocking issues are resolved. (There was mail thread with
"release" bug list)
@George can you create issues in JIRA?
@Sebastian currently I'm modifying Release guide "on the fly" I'll update
it with all my steps, so it will be up-to-date
On Fri, Mar 8, 2013 at 9:
12 matches
Mail list logo
