OPENMEETINGS-404 <https://issues.apache.org/jira/browse/OPENMEETINGS-404> does not need to be fixed for v2.1 OPENMEETINGS-377 <https://issues.apache.org/jira/browse/OPENMEETINGS-377> should be minor (I thought it would be even fixed already) OPENMEETINGS-475 <https://issues.apache.org/jira/browse/OPENMEETINGS-475> I have to test that. F11 is a shortcut of the browser not of OpenMeetings from my point of view.
The only real issue open is OPENMEETINGS-270 <https://issues.apache.org/jira/browse/OPENMEETINGS-270> and I have no chance of debugging or reviewing it. I am not even sure if its still an issue, it is very hard to debug as I only have seen it on a production environment. After all none of those issue are blocker that should stop you in building a RC candidate. However you should be aware that a potential "release" is nothing else then a RC. So if any RC is voted to be released, thats it! That RC will be the release,. There is no way of applying modified code to it or using a later revision for the "real" release. The RC that is voted is the exact release. In fact you can simply rename the package and the RC is the release once the vote was positive. So any fix to the above mentioned issues would go into a version 2.1.1 or 2.1.2 and would require a separated RC, vote and publishing process. Sebastian 2013/3/4 Maxim Solodovnik <solomax...@gmail.com> > My idea was to build RC today/tomorrow ... > Should I wait? > > > On Mon, Mar 4, 2013 at 1:09 PM, seba.wag...@gmail.com < > seba.wag...@gmail.com> wrote: > >> I have to review those issue open as soon as possible. >> But it might take 1-2 weeks. >> >> Sebastian >> >> >> 2013/3/4 Maxim Solodovnik <solomax...@gmail.com> >> >>> Hello Sebastian, >>> >>> It seems like all "my" issues are currently resolved (hopefully will >>> close them today) >>> can you take a look at the issues remaining (only 4) >>> >>> Thanks in advance >>> >>> >>> On Sat, Feb 9, 2013 at 9:08 AM, Maxim Solodovnik >>> <solomax...@gmail.com>wrote: >>> >>>> 1) I'm currently trying to help Timur with SIP (only testing efforts) >>>> Current issue: 8kHz audio is seems to be hardcoded into red5phone and >>>> Timur is trying to enable at least 22kHz >>>> >>>> 2) I'm going to implement mailQ (the only big java issue in the list) >>>> >>>> 3) I can help you with modifying the build >>>> >>>> 4) After Vasiliy will creates the rest backup files, I'll add them to >>>> the build.properties and will close 446 >>>> >>>> 5) I'll update Joomla plugin >>>> >>>> >>>> namely, mine seems to be: >>>> OPENMEETINGS-327 >>>> OPENMEETINGS-446 >>>> OPENMEETINGS-431 >>>> OPENMEETINGS-528 >>>> OPENMEETINGS-378 (or should we move this to 3.0 ?) >>>> >>>> I would love if you can handle: >>>> OPENMEETINGS-516 >>>> OPENMEETINGS-475 >>>> OPENMEETINGS-404 (or should we move this to 3.0 ?) >>>> OPENMEETINGS-377 >>>> >>>> I can help you with: >>>> OPENMEETINGS-529 >>>> >>>> I believe we should move OPENMEETINGS-270 to 3.0 just before the >>>> release build since it is very hard to reproduce/find the main cause >>>> >>>> >>>> >>>> On Sat, Feb 9, 2013 at 6:59 AM, seba.wag...@gmail.com < >>>> seba.wag...@gmail.com> wrote: >>>> >>>>> what is the list of issues to be fixed for Version 2.1 that you are >>>>> looking at currently? >>>>> I am searching for the AEC feature. That is only a change in the build >>>>> system from my point of view and could be possible to be resolved for >>>>> version 2.1. >>>>> >>>>> (including CC dev@) >>>>> >>>>> Sebastian >>>>> >>>>> >>>>> 2013/2/8 Maxim Solodovnik <solomax...@gmail.com> >>>>> >>>>>> Hello Sebastian, >>>>>> >>>>>> can you please take a look at this list: >>>>>> >>>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20OPENMEETINGS%20AND%20fixVersion%20%3D%20EMPTY%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20ORDER%20BY%20priority%20DESC >>>>>> >>>>>> I would like to set "Fix Version" for all these issues to "3.0" >>>>>> Maybe you would like to mark some of them as "2.1" >>>>>> >>>>>> -- >>>>>> 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 >>> >> >> >> >> -- >> 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
