Sebastian,
I quite often find that when I download OpenMeetings 2.0 latest revision, there is something that was working before but is now broken. I understand that we are doing a lot of updates and changes but some stability would be greatly appreciated by those of us who are using/testing OpenMeetings 2.0 in production. Is the following suggestion possible? 1) Use svn to get the latest copy of OpenMeetings which has everyone’s change being applied to it. 2) Use https://builds.apache.org/job/openmeetings/ (i.e. Jenkins) for getting a copy of OpenMeetings that has pasted a set of basic testing. 3) Have a set of basic tests documented so that OpenMeetings can be tested against this set of tests before it is loaded into Jenkins ? OpenMeetings could be uploaded to Jenkins on a monthly basis? More frequently if people have time to go though the tests. Maybe there are other ways to manage rapid development and a stable version every so often which has been though some form of complete feature testing? Thanks, George Kirkham
