You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openmeetings.apache.org by Maxim Solodovnik <so...@gmail.com> on 2013/02/07 17:48:24 UTC
Issues need to be sorted before release
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
Re: Issues need to be sorted before release
Posted by Maxim Solodovnik <so...@gmail.com>.
There is only 1 Joomla issue with the code contribution, this is why it is
in the list
I saw no issues related to cluster in the JIRA, this is why it is not in
the list
Can you create the issues, so we can sort it and see it is fit into the
time schedule?
The recordings in 1.7 and 1.8 are small, but I was sure it is no problem
@Vasiliy can you check if it has interview recordings or not
I'll add some basic asserts into JUnit test.
On Sun, Feb 10, 2013 at 4:41 AM, seba.wagner@gmail.com <
seba.wagner@gmail.com> wrote:
> I think you can move everything Joomla related, Joomla is a project at
> apache-extras.org.
> So setting any fix version is actually random from my point of view.
>
> I can see no recording files in the 1.8 and 1.7 backup files. They seem to
> be rather small, or exported without the files at all.
> Also they do not contain an interview recording. It would be good if both
> recording types are contained as they have different flags set.
>
> Once the import is done, for me its important not just to see the "import
> complete" message but to do some test, for example: control that there are
> really 2 users in the database, that there is a flvrecording. Control that
> there are 2 FLVRecordings, control that there is a private massage, control
> that there are really files in the recordings section and not just entries
> in the db that have no file.
> I don't know if the overall test will fail if there is an exception in the
> import somewhere. Or for example if the file operation does not detect the
> files.
> Basically the JUnit test should control the same things that you would to
> when you import a backup file:
> Goto the user administration check that the users are there, check the
> orgs, check the rooms, check that there are files in the file section and
> that those files exist (by draging something to the whiteboard), check that
> there are recordings and that those recordings do really exist (by playing
> something).
> Of course you can't check in JUnit by dragging a file to the whiteboard or
> playing in the recording UI, but you can check if the files do exist on the
> file-system with that id referenced in the database.
> So some assertTrue tests in the "TestOldBackups".
> Do you want me to write those tests?
>
> Sebastian
>
>
> 2013/2/10 seba.wagner@gmail.com <se...@gmail.com>
>
> what about the cluster related changes that I plan to do.
>> Should they go into a separated branch or into trunk?
>>
>> Sebastian
>>
>>
>> 2013/2/9 Maxim Solodovnik <so...@gmail.com>
>>
>>> 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.wagner@gmail.com <
>>> seba.wagner@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 <so...@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.wagner@gmail.com
>>>>
>>>
>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>>
>>
>>
>>
>> --
>> Sebastian Wagner
>> https://twitter.com/#!/dead_lock
>> http://www.webbase-design.de
>> http://www.wagner-sebastian.com
>> seba.wagner@gmail.com
>>
>
>
>
> --
> Sebastian Wagner
> https://twitter.com/#!/dead_lock
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.com
>
--
WBR
Maxim aka solomax
Re: Issues need to be sorted before release
Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
I think you can move everything Joomla related, Joomla is a project at
apache-extras.org.
So setting any fix version is actually random from my point of view.
I can see no recording files in the 1.8 and 1.7 backup files. They seem to
be rather small, or exported without the files at all.
Also they do not contain an interview recording. It would be good if both
recording types are contained as they have different flags set.
Once the import is done, for me its important not just to see the "import
complete" message but to do some test, for example: control that there are
really 2 users in the database, that there is a flvrecording. Control that
there are 2 FLVRecordings, control that there is a private massage, control
that there are really files in the recordings section and not just entries
in the db that have no file.
I don't know if the overall test will fail if there is an exception in the
import somewhere. Or for example if the file operation does not detect the
files.
Basically the JUnit test should control the same things that you would to
when you import a backup file:
Goto the user administration check that the users are there, check the
orgs, check the rooms, check that there are files in the file section and
that those files exist (by draging something to the whiteboard), check that
there are recordings and that those recordings do really exist (by playing
something).
Of course you can't check in JUnit by dragging a file to the whiteboard or
playing in the recording UI, but you can check if the files do exist on the
file-system with that id referenced in the database.
So some assertTrue tests in the "TestOldBackups".
Do you want me to write those tests?
Sebastian
2013/2/10 seba.wagner@gmail.com <se...@gmail.com>
> what about the cluster related changes that I plan to do.
> Should they go into a separated branch or into trunk?
>
> Sebastian
>
>
> 2013/2/9 Maxim Solodovnik <so...@gmail.com>
>
>> 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.wagner@gmail.com <
>> seba.wagner@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 <so...@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.wagner@gmail.com
>>>
>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>
>
>
> --
> Sebastian Wagner
> https://twitter.com/#!/dead_lock
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.com
>
--
Sebastian Wagner
https://twitter.com/#!/dead_lock
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com
Re: Issues need to be sorted before release
Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
what about the cluster related changes that I plan to do.
Should they go into a separated branch or into trunk?
Sebastian
2013/2/9 Maxim Solodovnik <so...@gmail.com>
> 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.wagner@gmail.com <
> seba.wagner@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 <so...@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.wagner@gmail.com
>>
>
>
>
> --
> WBR
> Maxim aka solomax
>
--
Sebastian Wagner
https://twitter.com/#!/dead_lock
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com
Re: Issues need to be sorted before release
Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
Yeah,
sure if you are keen give it a go :)
Sebastian
2013/3/4 Maxim Solodovnik <so...@gmail.com>
> OM-377 is reproducible, and the code of calendar click handlers frighten
> me a lot :))
> OM-475 is also reproducible, as soon as you click at OM flash area F11 is
> not handled by browser anymore, and I have no idea where to search who
> catches this keypress ...
>
> I propose to move OM-270 to 3.0 and prepare RC (I don't believe It will
> pass as RC1 :)) )
>
>
> On Mon, Mar 4, 2013 at 1:40 PM, seba.wagner@gmail.com <
> seba.wagner@gmail.com> wrote:
>
>> 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 <so...@gmail.com>
>>
>>> My idea was to build RC today/tomorrow ...
>>> Should I wait?
>>>
>>>
>>> On Mon, Mar 4, 2013 at 1:09 PM, seba.wagner@gmail.com <
>>> seba.wagner@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 <so...@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 <solomax666@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.wagner@gmail.com <
>>>>>> seba.wagner@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 <so...@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.wagner@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.wagner@gmail.com
>>>>
>>>
>>>
>>>
>>> --
>>> WBR
>>> Maxim aka solomax
>>>
>>
>>
>>
>> --
>> Sebastian Wagner
>> https://twitter.com/#!/dead_lock
>> http://www.webbase-design.de
>> http://www.wagner-sebastian.com
>> seba.wagner@gmail.com
>>
>
>
>
> --
> WBR
> Maxim aka solomax
>
--
Sebastian Wagner
https://twitter.com/#!/dead_lock
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com
Re: Issues need to be sorted before release
Posted by Maxim Solodovnik <so...@gmail.com>.
OM-377 is reproducible, and the code of calendar click handlers frighten me
a lot :))
OM-475 is also reproducible, as soon as you click at OM flash area F11 is
not handled by browser anymore, and I have no idea where to search who
catches this keypress ...
I propose to move OM-270 to 3.0 and prepare RC (I don't believe It will
pass as RC1 :)) )
On Mon, Mar 4, 2013 at 1:40 PM, seba.wagner@gmail.com <seba.wagner@gmail.com
> wrote:
> 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 <so...@gmail.com>
>
>> My idea was to build RC today/tomorrow ...
>> Should I wait?
>>
>>
>> On Mon, Mar 4, 2013 at 1:09 PM, seba.wagner@gmail.com <
>> seba.wagner@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 <so...@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 <so...@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.wagner@gmail.com <
>>>>> seba.wagner@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 <so...@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.wagner@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.wagner@gmail.com
>>>
>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>
>
>
> --
> Sebastian Wagner
> https://twitter.com/#!/dead_lock
> http://www.webbase-design.de
> http://www.wagner-sebastian.com
> seba.wagner@gmail.com
>
--
WBR
Maxim aka solomax
Re: Issues need to be sorted before release
Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
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 <so...@gmail.com>
> My idea was to build RC today/tomorrow ...
> Should I wait?
>
>
> On Mon, Mar 4, 2013 at 1:09 PM, seba.wagner@gmail.com <
> seba.wagner@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 <so...@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 <so...@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.wagner@gmail.com <
>>>> seba.wagner@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 <so...@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.wagner@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.wagner@gmail.com
>>
>
>
>
> --
> WBR
> Maxim aka solomax
>
--
Sebastian Wagner
https://twitter.com/#!/dead_lock
http://www.webbase-design.de
http://www.wagner-sebastian.com
seba.wagner@gmail.com
Re: Issues need to be sorted before release
Posted by Maxim Solodovnik <so...@gmail.com>.
My idea was to build RC today/tomorrow ...
Should I wait?
On Mon, Mar 4, 2013 at 1:09 PM, seba.wagner@gmail.com <seba.wagner@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 <so...@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 <so...@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.wagner@gmail.com <
>>> seba.wagner@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 <so...@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.wagner@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.wagner@gmail.com
>
--
WBR
Maxim aka solomax
Re: Issues need to be sorted before release
Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
I have to review those issue open as soon as possible.
But it might take 1-2 weeks.
Sebastian
2013/3/4 Maxim Solodovnik <so...@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 <so...@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.wagner@gmail.com <
>> seba.wagner@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 <so...@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.wagner@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.wagner@gmail.com
Re: Issues need to be sorted before release
Posted by Maxim Solodovnik <so...@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 <so...@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.wagner@gmail.com <
> seba.wagner@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 <so...@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.wagner@gmail.com
>>
>
>
>
> --
> WBR
> Maxim aka solomax
>
--
WBR
Maxim aka solomax
Re: Issues need to be sorted before release
Posted by Maxim Solodovnik <so...@gmail.com>.
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.wagner@gmail.com <seba.wagner@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 <so...@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.wagner@gmail.com
>
--
WBR
Maxim aka solomax
Re: Issues need to be sorted before release
Posted by "seba.wagner@gmail.com" <se...@gmail.com>.
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 <so...@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.wagner@gmail.com