done http://svn.apache.org/repos/asf/openmeetings/branches/2.1/ https://builds.apache.org/view/M-R/view/OpenMeetings/job/Openmeetings%202.1/
On Mon, Mar 18, 2013 at 1:10 PM, seba.wag...@gmail.com < seba.wag...@gmail.com> wrote: > That would be great! > And if you need to branch, just do it. > > Thanks, > Sebastian > Am 18.03.2013 19:03 schrieb "Maxim Solodovnik" <solomax...@gmail.com>: > > You are right :( >> I'll create the branch and set up the build. >> >> according to the logs demo is up for 10 hours so far (it is being used in >> testing SIP so it is reloaded from time to time) >> I'll ask others if we can deploy the next RC to it for the tests. >> >> >> On Mon, Mar 18, 2013 at 12:47 PM, seba.wag...@gmail.com < >> seba.wag...@gmail.com> wrote: >> >>> Even if you start the vote by today it takes 72 hours to vote. >>> And even if that vote passes it will take another day to release. >>> So the earliest day when its safe to commit new things to trunk will be >>> Friday or Saturday. >>> >>> And I still think it would be worth doing some more tests. >>> I have not been able to really test everything that I would like to test. >>> I did not test yet: >>> - backup feature / changes >>> - Mail queue on a server that has some valid mail settings >>> - Some basic server load, verification that the app runs stable for a >>> while >>> >>> The last point could be possible verified by the demo server at dataved. >>> Is there a report on that at dataved? >>> >>> The other things are also relatively new, but potential issues could be >>> resolved by doing a 2.1.1 release. But basically the new device settings >>> have been tested by only 3 users so far: Me, you, marius. And thats it. >>> >>> Can't we at least do the following: >>> Set up exactly the potential RC somewhere and really ask everyone on the >>> mailing list to test it before we start a new vote ? >>> It would be really useful and a chance to get some more activity around >>> our project. >>> >>> Sebastian >>> >>> >>> >>> 2013/3/18 Maxim Solodovnik <solomax...@gmail.com> >>> >>>> Hello Sebastian, >>>> I was hoping we can release today/tomorrow? >>>> Maybe we can name our current blockers? (currently there is no >>>> unresolved issues for 2.1) >>>> >>>> Separate branch means additional build target, double commits, etc. >>>> I would release in nearest couple of days with no additional branch >>>> >>>> what do you think? >>>> >>>> >>>> On Mon, Mar 18, 2013 at 12:28 PM, seba.wag...@gmail.com < >>>> seba.wag...@gmail.com> wrote: >>>> >>>>> Hi Maxim, >>>>> >>>>> I wonder if the release does lock you from committing improvements to >>>>> trunk. For example the red5 update that you mentioned to be already >>>>> somewhere in your pipe. >>>>> >>>>> Do you think it makes sense to create a branch for the 2.1 release? >>>>> So that you can commit changes to trunk (that would not got into the >>>>> 2.1 branch anyway) >>>>> I guess any kind of fixes that will be committed to branch 2.1 might >>>>> be minor enhancements or security / bug fixes anyway. But I guess the >>>>> process will take several days. And creating a TAG in the SVN for the Vote >>>>> does not mean that trunk is available to commit new things again. Actually >>>>> you would need to wait until there is really a release approved and done. >>>>> So by optimistic estimation might be next week, pessimistic estimation >>>>> might be 2-3 weeks. >>>>> >>>>> Sebastian >>>>> >>>>> -- >>>>> Sebastian Wagner >>>>> https://twitter.com/#!/dead_lock >>>>> http://www.webbase-design.de >>>>> http://www.wagner-sebastian.com >>>>> seba.wag...@gmail.com >>>>> >>>> >>>> >>>> >>>> -- >>>> WBR >>>> Maxim aka solomax >>>> >>> >>> >>> >>> -- >>> Sebastian Wagner >>> https://twitter.com/#!/dead_lock >>> http://www.webbase-design.de >>> http://www.wagner-sebastian.com >>> seba.wag...@gmail.com >>> >> >> >> >> -- >> WBR >> Maxim aka solomax >> > -- WBR Maxim aka solomax
