balunasj
:
Hi all - the agenda has been posted and we'll get started in a min
[
10:58am
]
•
balunasj
 
need hot coffee
[
10:58am
]
abelevich__
:
balunasj: hi
[
10:58am
]
Marauder|away
:
Hi all guys!
[
10:59am
]
Marauder|away is now known as ilya_shaikovsky.
[
11:02am
]
balunasj
:
abelevich__: Hi Anton
[
11:02am
]
balunasj
:
ilya_shaikovsky: Hi
[
11:02am
]
balunasj
:
Nick and alex should be joining us as well - we'll give them another min
[
11:02am
]
•
prabhat2
 
notes that lfryc will be point of contact from qa perspective. Of course ppitonak will chime in as well
[
11:03am
]
nbelaevski joined the chat room.
[
11:03am
]
balunasj
:
prabhat2: sure thing - and thanks for checking in while on vacation
[
11:03am
]
balunasj
:
nbelaevski: Hi Nick
[
11:03am
]
abelevich__
:
hi nick
[
11:03am
]
nbelaevski
:
hi Jay
[
11:03am
]
nbelaevski
:
hello all
[
11:04am
]
ppitonak
:
hi all
[
11:05am
]
balunasj
:
OK guys lets get started - here is the agenda
[
11:05am
]
balunasj
:
http://www.jboss.org/community/wiki/RichFacesTeamMeetingAgenda10-13-2009
[
11:05am
]
balunasj
:
Lets talk about the status of the 3.3.2.SR1 release testing
[
11:06am
]
balunasj
:
lfryc: Can you summarize?
[
11:06am
]
Konstantin left the chat room. (Read error: 54 (Connection reset by peer))
[
11:06am
]
lfryc
:
I can summarize it following: We did the manual testing of components what have been touched by fixes in SR1 (sent by Ilya)
[
11:07am
]
Konstantin joined the chat room.
[
11:07am
]
lfryc
:
lfryc: Also rerun the builds in hudson for release with some errors, please ppitonak to complete me..
[
11:08am
]
ppitonak
:
yes, all builds finished successfuly except of some problems with selenium tests for demo
[
11:08am
]
ppitonak
:
lukas fixed these bugss
[
11:08am
]
ppitonak
:
it's not the problem in components
[
11:09am
]
balunasj
:
ppitonak: is this is issue that did not get merged?  or a different one?
[
11:09am
]
ppitonak
:
one not merged and two new
[
11:09am
]
ilya_shaikovsky
:
lfryc, about last one https://jira.jboss.org/jira/browse/RF-7964 - new issue should be created for your last comments and this is not a regression and not related to original.
[
11:09am
]
balunasj
:
ilya_shaikovsky: looking...
[
11:09am
]
lfryc
:
balunasj: yes, SR1 not includes these 3 fixes for ftests
[
11:10am
]
ppitonak
:
balunasj: I launched selenium tests locally
[
11:10am
]
ppitonak
:
everything runs fine with firefox on linux
[
11:10am
]
nbelaevski
:
lfryc: are there JIRA issues for these 3 tests?
[
11:11am
]
lfryc
:
nbelaevski: mmnt
[
11:11am
]
balunasj
:
ppitonak, lfryc: and you were able to manually verify the tested behavior and isolate the failure in the tests?
[
11:11am
]
•
balunasj
 
thinking nbelaevski and I are on the same page - I was about to ask that too
[
11:12am
]
lfryc
:
nbelaevski: RF-7970, RF-7976, RF-7977
[
11:12am
]
lfryc
:
nbelaevski: It's all related to selenium richfaces-demo/functional-tests!
[
11:13am
]
alexsmirnov joined the chat room.
[
11:13am
]
balunasj
:
alexsmirnov: Hi Alex
[
11:14am
]
lfryc
:
balunasj: nbelaevski we verified manually that the errors aren't in components - in RichFaces demo and in test-applications (JSP)
[
11:14am
]
balunasj
:
lfryc: I did not think that https://jira.jboss.org/jira/browse/RF-7970 made it into the 3.3.2.SR1
[
11:14am
]
balunasj
:
lfryc: Was this merged or should we move to 3.3.3.CR1?
[
11:14am
]
balunasj
:
lfryc: good
[
11:15am
]
lfryc
:
balunasj: we should move it to 3.3.3.CR1 since it is not tagged in 3.3.2.SR1 the result is only the red icon in hudson
[
11:15am
]
balunasj
:
lfryc: ok please do that.
[
11:16am
]
balunasj
:
lets talk about the one remaining issue in resolved state - 7964 - ilya_shaikovsky commented on it above
[
11:16am
]
lfryc
:
lfryc: I also verified all of the changes listed here: https://jira.jboss.org/jira/browse/RF/fixforversion/12314031
[
11:16am
]
ilya_shaikovsky
:
balunasj, issue itself is verified
[
11:17am
]
ilya_shaikovsky
:
as I understand from Lukas comment
[
11:17am
]
alexsmirnov
:
Guys, does Jboss servers alive ? I can't open never JIRA nor forums
[
11:17am
]
ilya_shaikovsky
:
but new one found
[
11:17am
]
ilya_shaikovsky
:
and this is new issue (present in 3.3.1)
[
11:17am
]
balunasj
:
lfryc: so RF-7964 can be closed - and the new one created as you say - correct?
[
11:17am
]
balunasj
:
alexsmirnov: working for me
[
11:17am
]
lfryc
:
balunasj: yeah, as said ilya_shaikovsky
[
11:17am
]
balunasj
:
alexsmirnov: maybe all that rain you are supported to be getting today?
[
11:17am
]
lfryc
:
balunasj: I'm closing it..
[
11:18am
]
balunasj
:
lfryc: ok and will create that new issue - for 3.3.3.CR1
[
11:18am
]
alexsmirnov
:
Everything else is available.
[
11:18am
]
balunasj
:
alexsmirnov: weird - let me try again
[
11:19am
]
balunasj
:
alexsmirnov: yup all working - jira forums, projects stie
[
11:19am
]
balunasj
:
stie
[
11:19am
]
balunasj
:
site - 2nd try
[
11:19am
]
balunasj
:
so on QE side all automated tests either passed, or accounted for
[
11:19am
]
binnyg joined the chat room.
[
11:20am
]
balunasj
:
and all manual testing of changes has been verified
[
11:20am
]
balunasj
:
lfryc: correct^?
[
11:20am
]
lfryc
:
balunasj: correct
[
11:20am
]
balunasj
:
great!
[
11:20am
]
lfryc
:
balunasj: there is still one unresolved issue in SR1 in JIRA: https://jira.jboss.org/jira/browse/RF/fixforversion/12314031
[
11:21am
]
balunasj
:
lfryc: yup we'll discuss in dev part
[
11:21am
]
lfryc
:
balunasj: ok
[
11:21am
]
balunasj
:
any other questions or comments for QE?
[
11:22am
]
lfryc
:
balunasj: I have no more comments (ppitonak ^^)
[
11:22am
]
lfryc
:
balunasj: I will report the issue for ext.data table broken in IE8
[
11:23am
]
ppitonak
:
what about bugs in neko-parser?
[
11:23am
]
balunasj
:
ppitonak: later on in agenda - but is that part of what is causing failed tests ?
[
11:23am
]
balunasj
:
ppitonak: that is what I was not sure of
[
11:23am
]
ppitonak
:
balunasj: I don't know
[
11:24am
]
ppitonak
:
balunasj: I only know that the number of bugs increased
[
11:24am
]
balunasj
:
ppitonak: is this effecting your tests - or just what Stan brought up with his tests?
[
11:24am
]
ppitonak
:
balunasj: hudson marked it as passed so I don't know whether it's a problem
[
11:25am
]
balunasj
:
ppitonak: did anything else change?  nbelaevski have you had a change to look?
[
11:25am
]
balunasj
:
s/change/chance
[
11:26am
]
ppitonak
:
balunasj: what do you mean?
[
11:26am
]
nbelaevski
:
balunasj: yes, I've checked tests results yesterday
[
11:26am
]
balunasj
:
ppitonak: I'm trying to figure out why they just started failing and what changed to make that happen
[
11:26am
]
ppitonak
:
balunasj: I only changed GA to SR1 and we got +46 failures
[
11:26am
]
balunasj
:
nbelaevski: thoughts?
[
11:26am
]
nbelaevski
:
ppitonak: some tests can be shown as passed because Hudson incorrectly interprets different testing configurations
[
11:27am
]
nbelaevski
:
balunasj: local run was ok
[
11:27am
]
alexsmirnov
:
nbelaevski: Did you have progress with JSF 2.0/tree component ? Is there any commits for that issue ?
[
11:27am
]
balunasj
:
nbelaevski: well that is good
[
11:27am
]
balunasj
:
alexsmirnov: we're going to talk about that is just one min
[
11:27am
]
nbelaevski
:
two failures: ERROR: Element //td[@id='_form:calendarFooter']/table/tbody/tr/td[5]/div not found
[
11:27am
]
nbelaevski
:
com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:97)
[
11:27am
]
balunasj
:
alexsmirnov: http://www.jboss.org/community/wiki/RichFacesTeamMeetingAgenda10-13-2009
[
11:27am
]
nbelaevski
:
and one timeout
[
11:29am
]
nbelaevski
:
I think that Hudson failures are caused by some environmental issues
[
11:29am
]
balunasj
:
nbelaevski: ok good
[
11:29am
]
pietia joined the chat room.
[
11:29am
]
balunasj
:
ppitonak: where you able to run locally?
[
11:29am
]
ppitonak
:
balunasj: we have never tried this run locally
[
11:30am
]
balunasj
:
ppitonak: ok please give that a try
[
11:30am
]
ppitonak
:
balunasj: ok
[
11:31am
]
balunasj
:
We still need to look into what stan was discussing - but that is not critical for 3.3.2.SR1
[
11:31am
]
balunasj
:
lets move on to - https://jira.jboss.org/jira/browse/RF-7971
[
11:32am
]
balunasj
:
nbelaevski: and ilya_shaikovsky : discussed this and wanted them to update us
[
11:33am
]
nbelaevski
:
yes, I've reviewed the fix I've made yesterday - there's still a risk of possible side effects with JSF 1.2
[
11:34am
]
nbelaevski
:
Ilya suggested to bundle admin-console with JSF 1.2, I've checked this with JBoss 5.1.0.GA upgraded to JSF 2.0 - admin console seems to be working ok
[
11:34am
]
nbelaevski
:
have just build JBoss 5 from branch but hadn't try this yet
[
11:35am
]
balunasj
:
what was the original catalyst for adding 7971 to 3.3.2.SR1?
[
11:37am
]
ilya_shaikovsky
:
balunasj, I believe we should not made fixes in order to make admin console works with JSF 2 and RF 3.3. I'm afraid that some days later guys will add some other component and will add new issue. and we will maintain this support for long.. So proposed to bundle JSF 1.2 into console project.. In order to use richfaces 3.3 in supported environment and not spend time on compatibility which we are not planned.
[
11:38am
]
nbelaevski
:
the original motivation was lack of workaround for the issues other than usage of extra 1.2 JSF
[
11:38am
]
rruss1 joined the chat room.
[
11:38am
]
balunasj
:
ilya_shaikovsky: in general I agree - I do not want to add risk to 3.3.2.SR1
[
11:38am
]
balunasj
:
for the AS 5.2. fix
[
11:38am
]
ilya_shaikovsky
:
I think maybe not a risk.. but time consumption
[
11:39am
]
ilya_shaikovsky
:
and not for server itself.. but just for application.. which could works good under jsf 1.2
[
11:39am
]
balunasj
:
I would be more willing to have a JSF 2.0 compatibility release or information on 3.3.X
[
11:42am
]
•
balunasj
 
really don't want another 3.3.X release to worry about
[
11:43am
]
balunasj
:
alexsmirnov: you have been looking into this as well - what are your thoughts?
[
11:43am
]
prabhat2 left the chat room.
[
11:43am
]
balunasj
:
alexsmirnov: if RF 3.3.X compatibility with JSF 2.0 close enough to work on
[
11:43am
]
balunasj
:
or just too far to try?
[
11:44am
]
ilya_shaikovsky
:
I think that we have many tasks and things to do in 4.x so if support release for 3.3-2.0 requires any development I would prefer just to add information on limitations for the guys who trying to use rf 3.3 under JSF 2.0
[
11:45am
]
•
balunasj
 
also thinking about difference between "officially" supported vs - some artivles and wiki pages on getting some support working.
[
11:45am
]
•
rruss
 
agrees with Ilya's assessment of the long term support issue
[
11:45am
]
alexsmirnov
:
balunasj: I think it makes sense to provide simple fix that does not affect JSF 1.2 compatibility. We would get a lot of similar questions with Jboss 5.2 release then other developers will try to migrate their applications.
[
11:46am
]
ilya_shaikovsky
:
alexsmirnov, but for those developers we have official support matrix. as 3.1.x - 3.2.x ahs strict limitations on jsf 1.1 and 1.2
[
11:46am
]
alexsmirnov
:
But we should postpone it if we got  problems with JSF 1.2.
[
11:46am
]
ilya_shaikovsky
:
ahs - had
[
11:47am
]
alexsmirnov
:
ilya_shaikovsky: How many developers do not read that ?
[
11:47am
]
rruss
:
Is there any expectation (based on the spec) that JSF 1.2 applications should work with JSF 2.0 implementations?
[
11:48am
]
balunasj
:
rruss: yes - JSF 2.0 is supposed to be backyards compatible
[
11:48am
]
balunasj
:
RichFaces as we have said publically for a while is not
[
11:48am
]
balunasj
:
AS 5.2 release with admin-console
[
11:48am
]
rruss
:
that would be the crux of the question from my perspective then
[
11:48am
]
ilya_shaikovsky
:
alexsmirnov, I agree..many of them not read. But the support could became hard in general if we allow this from the beggining.
[
11:48am
]
balunasj
:
through a wrench into this because they needed a way to run.
[
11:49am
]
pietia left the chat room. (Read error: 60 (Operation timed out))
[
11:49am
]
alexsmirnov
:
JSF always promoted as backward compatible technology, same as does Java itself.
[
11:49am
]
balunasj
:
alexsmirnov: yup
[
11:50am
]
balunasj
:
Another point is that other component libraries are claiming compatibility with JSF 2.0
[
11:50am
]
balunasj
:
such as icefaces
[
11:50am
]
alexsmirnov
:
Therefore, any JSF 1.2 applications and libraries should work with JSF 2.0 ( in theory :-).
[
11:50am
]
balunasj
:
exactly in theory
[
11:50am
]
nbelaevski
:
the last time we've discussed this topic, some incompatibilities with state manager were mentioned
[
11:51am
]
balunasj
:
nbelaevski: yup - alex was looking into this because of a surprise requirement from the admin console
[
11:51am
]
rruss
:
in theory there is no difference between theory and practice, but in practice ...
[
11:51am
]
balunasj
:
rruss: hehe
[
11:51am
]
alexsmirnov
:
nbelaevski: Yes, tree issue comes from state management.
[
11:52am
]
balunasj
:
alexsmirnov: you had mentioned a possible work around or JSF 2.0 compatibility module
[
11:52am
]
ilya_shaikovsky
:
and b.t.w. JSF 1.2 with facelets(which is very popular combination) - seems has a problems without RF..
[
11:52am
]
balunasj
:
alexsmirnov: is anything like that still on the table?
[
11:52am
]
ilya_shaikovsky
:
so many applications will lost compatibility even without us
[
11:52am
]
ppitonak left the chat room. (Remote closed the connection)
[
11:52am
]
balunasj
:
ilya_shaikovsky: that is a good point - but I had not heard that before - where did you see that?
[
11:54am
]
balunasj
:
all: lets take a step back for a minute - lets wrap up 3.3.2.SR1 discussion and release plan
[
11:54am
]
balunasj
:
Discussing the JSF 2.0 support and RF 3.3. is a whole meeting
[
11:54am
]
balunasj
:
either way I think we can all agree that this fix will not be in 3.3.2.SR1
[
11:54am
]
balunasj
:
RF-7971 ^
[
11:55am
]
ppitonak joined the chat room.
[
11:55am
]
balunasj
:
If that is the case we need to finish talking about the release plan and we can move this talk to a different meeting
[
11:55am
]
ilya_shaikovsky
:
I'm not actually sure for current state of such compatibility but if you remember we discussed that facelets 1.1x can't be used under jsf 2 without additional configuration.. Nick and Alex provided some details..
[
11:56am
]
•
rruss
 
agrees that JSF 2.0 and RF 3.3 could take at least a whole meeting
[
11:57am
]
balunasj
:
so lets postpone this talk until Thursday at 10:00 or 11:00 AM EST
[
11:57am
]
balunasj
:
can everyone make a meeting then?
[
11:57am
]
rruss
:
sure
[
11:58am
]
amitev left the chat room. ("Although nobody can come back and make a new start, anyone can start now and make a new end")
[
11:58am
]
nbelaevski
:
yes
[
11:58am
]
balunasj
:
alexsmirnov: ilya_shaikovsky nbelaevski ^^
[
11:58am
]
ilya_shaikovsky
:
sure
[
11:58am
]
alexsmirnov
:
ilya_shaikovsky: Facelets 1.1 tags couldn't be used with JSF 2.0 library, but implementation has an option to switch back View Definition from built-in to Facelets.
[
11:59am
]
balunasj
:
alexsmirnov: can you make a meeting on Thursday at 11 AM EST ( 8 AM PST )?
[
11:59am
]
alexsmirnov
:
Ok, let us discuss that on Thursday. 11 EST is more convenient for me.
[
11:59am
]
pietia joined the chat room.
[
11:59am
]
balunasj
:
alexsmirnov: ok
[
12:00pm
]
balunasj
:
I'll make the meeting
[
12:00pm
]
balunasj
:
lets finish out discussion on 3.3.2.SR1 release plan
[
12:01pm
]
balunasj
:
Testing sounds like it all set
[
12:01pm
]
balunasj
:
what is left is uploading, verification of uploaded files
[
12:01pm
]
balunasj
:
site updates/review and
[
12:01pm
]
balunasj
:
announcement
[
12:01pm
]
ppitonak
:
balunasj: btw
[
12:01pm
]
ppitonak
:
79%
[
12:01pm
]
ppitonak
:
WDescription%
[
12:01pm
]
ppitonak
:
Build stability: 1 out of the last 5 builds failed.79
[
12:01pm
]
ppitonak
:
Test Result: 0 tests failing out of a total of 2,740 tests.100
[
12:01pm
]
ppitonak
:
richfaces-3.3-release-component-tests-default-neko-parser
[
12:02pm
]
ppitonak
:
ooops
[
12:02pm
]
ppitonak
:
neko-parser job just finished with no failure
[
12:02pm
]
balunasj
:
ppitonak: excellent !
[
12:02pm
]
balunasj
:
ppitonak: no problem - the functional tests can be temperamental
[
12:03pm
]
balunasj
:
so Konstantin can you offload uploads from alexsmirnov so he can focus on other items?
[
12:03pm
]
ppitonak
:
balunasj: Prabhat suggested to use another machine and it worked
[
12:03pm
]
balunasj
:
ppitonak: that is good
[
12:04pm
]
balunasj
:
ilya_shaikovsky: I'll review you updates to the site
[
12:04pm
]
balunasj
:
and write the announcement
[
12:04pm
]
Konstantin
:
Yes, I can do this.
[
12:04pm
]
balunasj
:
alexsmirnov: can you point him at the dist files for this?
[
12:04pm
]
balunasj
:
lfryc: ppitonak : can you guys verify these files ( both from downloads, and maven ) first thing tomorrow?
[
12:04pm
]
alexsmirnov
:
ppitonak: Do you have timeout settings in tests ? Build machine would be to slow to finish all tests in intended time.
[
12:05pm
]
balunasj
:
alexsmirnov: from what I saw at least some of the tests did not seem to be timing related
[
12:05pm
]
ppitonak
:
alexsmirnov: I don't know these tests, we inherited them...
[
12:06pm
]
ppitonak
:
balunasj: np
[
12:06pm
]
lfryc
:
balunasj: ok, I'm in..
[
12:06pm
]
balunasj
:
Konstantin: will you be able to get the file uploaded and in place by AM tomorrow your time?
[
12:06pm
]
balunasj
:
Konstantin: this way we can release AM EST
[
12:07pm
]
ppitonak
:
balunasj: is downloading and verifying checksums and deploying enough?
[
12:08pm
]
lfryc
:
Konstantin: please can you ping us (richfaces-exadel@redhat.com or IRC) as you will deploy it?
[
12:08pm
]
balunasj
:
ppitonak: yes - the idea to confirm that the exact same bits that were tested are uploaded, and that maven is setup correctly
[
12:08pm
]
balunasj
:
ppitonak: for clean builds and working.
[
12:08pm
]
ppitonak
:
balunasj: ok
[
12:09pm
]
balunasj
:
ilya_shaikovsky: I'll review your site update and write blog today
[
12:09pm
]
Konstantin
:
balunasj: yes
[
12:09pm
]
balunasj
:
Konstantin: thanks
[
12:09pm
]
Konstantin
:
lfryc: ok
[
12:10pm
]
balunasj
:
Anything else for 3.3.2.SR1?
[
12:11pm
]
balunasj
:
ok I'll set up a meeting for Thursday & have some one from the AS team join us as well
[
12:11pm
]
balunasj
:
we'll get 3.3.2.SR1 out tomorrow
[
12:12pm
]
balunasj
:
ok guys thanks - I need to go for a walk before my next meeting....