balunasj
:
agenda is posted in meeting info links in channel topic
[
11:08am
]
balunasj
:
is the wiki working for any of you?
[
11:09am
]
nbelaevski
:
works for me
[
11:09am
]
alexsmirnov joined the chat room.
[
11:09am
]
balunasj
:
ok it seems to be back up for me too now - got error pages for the first few time
[
11:10am
]
balunasj
:
ok lets get started
[
11:10am
]
balunasj
:
I wanted to make sure we are ready for the 3.3.2.CR1 release and everyone is on the same page.
[
11:10am
]
balunasj
:
I saw we have 3 reopened issues
[
11:11am
]
balunasj
:
(see agenda)
[
11:11am
]
balunasj
:
we should probably talk about them first
[
11:11am
]
balunasj
:
Please take a look here - https://jira.jboss.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310341&status=4&fixfor=12313512
[
11:12am
]
balunasj
:
The critical one is RF-7172
[
11:13am
]
balunasj
:
Seems pretty important that this is fixed
[
11:13am
]
balunasj
:
nbelaevski: what are your thoughts?
[
11:13am
]
balunasj
:
alex k marked it resolved Jul 18th
[
11:14am
]
balunasj
:
28th
[
11:14am
]
balunasj
:
I just pinged Alex K to join us
[
11:15am
]
nbelaevski
:
balunasj: ok, better Alex will report how it's going
[
11:15am
]
balunasj
:
nbelaevski: agreed
[
11:16am
]
Alex_Kolonitsky joined the chat room.
[
11:17am
]
balunasj
:
Alex_Kolonitsky: Hi Alex
[
11:17am
]
Alex_Kolonitsky
:
Hi Jay
[
11:17am
]
balunasj
:
We are looking at 3 reopened issues for 3.3.2.CR1
[
11:17am
]
balunasj
:
https://jira.jboss.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310341&status=4&fixfor=12313512
[
11:17am
]
balunasj
:
wanted to get a status on them
[
11:18am
]
balunasj
:
timeframe, and severity opinion ( can they be pushed to 3.3.2.GA)
[
11:19am
]
alexsmirnov
:
RF-7172 - described behavior seems correct. {param} is not an EL-expression, therefore it should be renderer as '{testParam}'.
[
11:19am
]
Alex_Kolonitsky
:
RF-7172 Fixed but not commited
[
11:20am
]
balunasj
:
Alex_Kolonitsky: I'm assuming the jira has a typo - should be #{testParam} right
[
11:21am
]
nbelaevski
:
balunasj: actually no
[
11:22am
]
nbelaevski
:
that's client-evaluated expressions
[
11:22am
]
nbelaevski
:
the same as in rich:calendar
[
11:23am
]
rruss left the chat room. (Read error: 110 (Connection timed out))
[
11:23am
]
balunasj
:
nbelaevski: ok - I'll need to review closer
[
11:24am
]
balunasj
:
Alex_Kolonitsky: how invasive was the fix for this?
[
11:24am
]
Alex_Kolonitsky
:
RF-7172 Parameters not being passed to contextMenu
[
11:24am
]
Alex_Kolonitsky
:
Fixed but not commited because of code freeze
[
11:25am
]
balunasj
:
Alex_Kolonitsky: right, I'm asking how invasive the fox for this is?
[
11:26am
]
balunasj
:
in other words it is currently listed to be fixed for 3.3.2.CR1 we either need to shift to 3.3.2.GA
[
11:26am
]
balunasj
:
or unfreeze to get this fix in.
[
11:26am
]
balunasj
:
This is a CR1 release so it does not need to be 100%
[
11:26am
]
rruss joined the chat room.
[
11:26am
]
balunasj
:
but anything major ( especially regressions ) should be fixed
[
11:28am
]
nbelaevski
:
balunasj: I think the fix is isolated, so what do you think about the idea to fix the problem, run tests for this component and release CR1?
[
11:28am
]
balunasj
:
nbelaevski: +1
[
11:29am
]
balunasj
:
nbelaevski: that is what I was looking for - how isolated the fix is
[
11:29am
]
balunasj
:
tkuprevich: are you able to test this quickly?
[
11:29am
]
nbelaevski
:
balunasj: yes, it's isolated
[
11:29am
]
balunasj
:
nbelaevski: thanks
[
11:30am
]
balunasj
:
lets discuss the other two then talk about the respin and testing
[
11:30am
]
balunasj
:
IMO - RF-7666 can wait - it is a demo issue
[
11:30am
]
balunasj
:
only concern here is if this represents a real issue
[
11:31am
]
tkuprevich
:
balunasj: it shouldn't take a lot of time, but I was going to leave soon...
[
11:31am
]
nbelaevski
:
balunasj: yes, that's what I thought about
[
11:31am
]
nbelaevski
:
Alex_Kolonitsky: have you looked at this?
[
11:31am
]
balunasj
:
tkuprevich: you marked this as reopened - is it a problem with the demo or do you think it is an issue with calendar?
[
11:32am
]
balunasj
:
tkuprevich: If there is a build for you tomorrow AM your time how long do you think testing will take?
[
11:32am
]
tkuprevich
:
balunasj: I don't know actually. I didn't check at any othre application
[
11:33am
]
tkuprevich
:
balunasj: a few minutes. But Isn't it a last working day for us? I'm just not sure
[
11:33am
]
balunasj
:
tkuprevich: offline
[
11:34am
]
balunasj
:
Alex_Kolonitsky: ping^
[
11:37am
]
Alex_Kolonitsky
:
Fixes for bugs RF-7172 and  RF-7666 are not committed yet and waiting for code unfreeze
[
11:38am
]
Alex_Kolonitsky
:
if you want i can commit them right now
[
11:38am
]
balunasj
:
7172 - we decided would go in
[
11:39am
]
balunasj
:
7666 - if it is just a problem with the demo can wait
[
11:39am
]
Alex_Kolonitsky
:
ok
[
11:39am
]
balunasj
:
5751 - is reopened and have some votes from the community - so curious about that issue as well.
[
11:39am
]
balunasj
:
Alex_Kolonitsky: is 7666 a problem with demo or calendar?
[
11:40am
]
Alex_Kolonitsky
:
calendar
[
11:40am
]
balunasj
:
Can you email a diff to the richfaces -exadel list?
[
11:40am
]
balunasj
:
or attach the patch to the jira?
[
11:40am
]
Alex_Kolonitsky
:
ok
[
11:41am
]
balunasj
:
so that we can see how isolated it is?
[
11:41am
]
balunasj
:
Alex_Kolonitsky: ok what about 5751?
[
11:42am
]
balunasj
:
it looks like it was fixed in Jul by Markhel
[
11:45am
]
Alex_Kolonitsky
:
I'll have a look at this bug as soon as possible
[
11:45am
]
balunasj
:
Alex_Kolonitsky: ok thanks
[
11:46am
]
balunasj
:
nbelaevski: what do you think of it - It has been a problem since 3.3.0
[
11:46am
]
balunasj
:
and we are going to have 3.3.2.GA
[
11:46am
]
balunasj
:
I'm leaning to postpost to GA
[
11:46am
]
balunasj
:
so we can get this release out
[
11:47am
]
nbelaevski
:
balunasj: agree
[
11:47am
]
balunasj
:
nbelaevski: ok good
[
11:47am
]
balunasj
:
so Alex_Kolonitsky commit & merge your changes for 7172
[
11:47am
]
balunasj
:
send out the patch file for 7666 so we can take a quick look
[
11:48am
]
balunasj
:
then if not risky commit and merge 7666
[
11:48am
]
balunasj
:
Konstantin: Can then build a new distribution for QE
[
11:48am
]
balunasj
:
QE will test first thing tomorrow and we'll release tomorrow afternoon
[
11:49am
]
balunasj
:
sound like a plan?  any objections or concerns?
[
11:50am
]
Konstantin
:
Ok, I will do this tomorrow.
[
11:50am
]
balunasj
:
Konstantin: ok great
[
11:51am
]
balunasj
:
Konstantin, nbelaevski - you are comfortable with the rest of the release procedure?
[
11:51am
]
nbelaevski
:
balunasj: yes
[
11:51am
]
balunasj
:
smukhina1: will you be ready to get the doc bundle to IT for posting?
[
11:51am
]
balunasj
:
nbelaevski: ok good
[
11:51am
]
balunasj
:
so that is the plan
[
11:52am
]
balunasj
:
Alex_Kolonitsky: How long do you think it will take you to forward or attach the patch file for your changes?
[
11:52am
]
smukhina1
:
yes, I will give it tomorrow
[
11:52am
]
balunasj
:
smukhina1: great thanks
[
11:53am
]
bj_990 joined the chat room.
[
11:54am
]
balunasj
:
nbelaevski: we'll discuss 4.0 A1 in our next meeting and discuss how this effects that release
[
11:54am
]
nbelaevski
:
balunasj: ok good
[
11:54am
]
balunasj
:
Alex_Kolonitsky: How long do you think it will take you to forward or attach the patch file for your changes?
[
11:55am
]
Alex_Kolonitsky
:
I will do it tomorrow morning
[
11:55am
]
lfryc left the chat room. ("Leaving")
[
11:55am
]
balunasj
:
nbelaevski: that means that you will need to look because your morning will be middle of night for me - is that ok?
[
11:56am
]
balunasj
:
nbelaevski: otherwise the fix for 7666 needs to be moved to GA
[
11:56am
]
nbelaevski
:
yes, that's ok
[
11:56am
]
balunasj
:
ok thanks!
[
11:56am
]
balunasj
:
Anything else to bring up for 3.3.2.CR1?
[
11:59am
]
balunasj
:
ok - thanks and we'll check in again at tomorrow meeting
[
11:59am
]
balunasj
:
and get this release out