balunasj
:
FYI - agenda is here http://www.jboss.org/community/wiki/RichFacesTeamMeetingAgenda10-27-2009
[
11:05am
]
balunasj
:
ok lets get started
[
11:06am
]
pyaschenko joined the chat room.
[
11:06am
]
pyaschenko
:
Hi All
[
11:06am
]
amarkhel joined the chat room.
[
11:06am
]
amarkhel
:
hello
[
11:06am
]
balunasj
:
amarkhel, pyaschenko : hi guys - here is the agenda http://www.jboss.org/community/wiki/RichFacesTeamMeetingAgenda10-27-2009
[
11:06am
]
clerum joined the chat room.
[
11:06am
]
balunasj
:
So yesterday Ilya, Nick, and I discussed jira's for the 3.3.3 release.
[
11:07am
]
balunasj
:
This is going to be a very limited and focused release
[
11:07am
]
balunasj
:
The primary changes are JSF 2.0 support ( conditional and limited ) + some low risk or critical issues that should be addressed
[
11:08am
]
balunasj
:
amarkhel: Have you had a chance to review the jira lists - most of them are assigned to you.
[
11:08am
]
balunasj
:
?
[
11:09am
]
alexsmirnov
:
3.3.3 related issues seems what we are going to fix at least some JSF 2.0 compatibility. Is it 3.3.3 goal ?
[
11:09am
]
amarkhel
:
no i am going to do there right now
[
11:09am
]
balunasj
:
amarkhel: ok please do - we'll need to discuss some scheduling and estimates later
[
11:09am
]
amarkhel
:
ok
[
11:10am
]
balunasj
:
alexsmirnov: The primary goal of the JSF 2 items in 3.3.3 are admin-console support for AS 5.2
[
11:10am
]
balunasj
:
alexsmirnov: The secondary goal is to support existing RF 3.3.X applications running on top of JSF 2.0
[
11:11am
]
balunasj
:
alexsmirnov: note - not full integration/support as we discussed
[
11:11am
]
balunasj
:
alexsmirnov: part of what we need ( I'll create a RFPL jira ) is
[
11:12am
]
balunasj
:
alexsmirnov: an article that describes exactly what is support and what is not + plus what changes are needed for basic integration.
[
11:12am
]
balunasj
:
alexsmirnov: does that sound reasonable?
[
11:12am
]
alexsmirnov
:
Sure. Because Hibernate validator has been released, I think we should also switch Richfaces validators dependencies to release version.
[
11:13am
]
balunasj
:
alexsmirnov: has that been tested or tried?  How much risk is there?
[
11:14am
]
alexsmirnov
:
I don't see any significant API changes, so that is about testing the most.
[
11:14am
]
balunasj
:
alexsmirnov: is there a jira created for it already?  Do we have updates needed?
[
11:14am
]
balunasj
:
or is it just jar update
[
11:17am
]
alexsmirnov
:
I have not created JIRA issue yet. It should be just jar update unless final version has some significant changes that should be carefully tested.
[
11:18am
]
balunasj
:
If there are not significant change then I'm fine with it - if anything major is found I think we should hold off.
[
11:19am
]
alexsmirnov
:
Is RFPL better place for that task ?
[
11:19am
]
balunasj
:
alexsmirnov: It depends what the task is:  Update hibernate validator to latest version is a RF issues
[
11:20am
]
alexsmirnov
:
ok
[
11:20am
]
balunasj
:
Investigate compatibility and impact of hibernate validator update is RFPL
[
11:20am
]
balunasj
:
one is specific change to release the other is a research task that may or may not result in updates.
[
11:21am
]
balunasj
:
FYI - just created https://jira.jboss.org/jira/browse/RFPL-212
[
11:21am
]
balunasj
:
for wiki article on 3.3.3 support of JSF 2.0
[
11:22am
]
balunasj
:
None of the QE guys are online so we'll skip talking about there updates for now.
[
11:22am
]
pyaschenko left the chat room. (Read error: 60 (Operation timed out))
[
11:22am
]
balunasj
:
there were a few issues that we wanted to discuss more
[
11:22am
]
balunasj
:
https://jira.jboss.org/jira/browse/RF-7929
[
11:23am
]
balunasj
:
amarkhel you will like need Konstantin and/or Pavel's assistense with this one.
[
11:24am
]
balunasj
:
nbelaevski: what else did you want to discuss about this one?
[
11:24am
]
alexsmirnov
:
I've just created https://jira.jboss.org/jira/browse/RF-8049 for HibernateValidator.
[
11:24am
]
balunasj
:
alexsmirnov: thanks
[
11:25am
]
nbelaevski
:
balunasj: Konstantin has ongoing tasks for tables, so we need to agree who will do this work
[
11:25am
]
balunasj
:
nbelaevski: you mean for 4.0 tables right
[
11:25am
]
nbelaevski
:
balunasj: yes
[
11:25am
]
amarkhel
:
balunasj: Now I have no idea about this issue, probably Konstantin help is will be needed
[
11:26am
]
nbelaevski
:
Konstantin: have you seen this issue?
[
11:26am
]
balunasj
:
nbelaevski: you had thought pavel might be able to assist to - or is Konstantin really the only on for this?
[
11:26am
]
Konstantin
:
not
[
11:26am
]
nbelaevski
:
balunasj: I would like to limit this help to one person
[
11:27am
]
balunasj
:
nbelaevski: agreed
[
11:27am
]
nbelaevski
:
Konstantin: any thoughts on how much time this can take?
[
11:28am
]
Konstantin
:
I don't see this problem, so I cannot say about it now.
[
11:28am
]
balunasj
:
Konstantin: because you don't have IE 8?
[
11:30am
]
Konstantin
:
I have it, but I need time to investigate this problem if I should.
[
11:31am
]
balunasj
:
Konstantin: I think yes
[
11:31am
]
Konstantin
:
ok
[
11:31am
]
balunasj
:
nbelaevski: agree?  It is worth some time for investigation
[
11:31am
]
nbelaevski
:
balunasj: agree
[
11:32am
]
nbelaevski
:
Konstantin: how much time?
[
11:32am
]
balunasj
:
nbelaevski: - you did it again
[
11:32am
]
nbelaevski
:
abelevich: how heavy is Konstantin is loaded?
[
11:33am
]
abelevich
:
nbelaevski: not much ...
[
11:33am
]
nbelaevski
:
balunasj: I wonder how much time for investigation is necessary
[
11:33am
]
nbelaevski
:
abelevich: ok
[
11:34am
]
balunasj
:
nbelaevski: I would propose no more than 4 hours and then give us a report
[
11:34am
]
Konstantin
:
I need about 2 hours.
[
11:34am
]
balunasj
:
Konstantin: even better
[
11:34am
]
nbelaevski
:
Konstantin: balunasj: great
[
11:34am
]
balunasj
:
Konstantin: please post report to dev forum
[
11:35am
]
nbelaevski
:
balunasj: +1
[
11:35am
]
balunasj
:
next up - https://jira.jboss.org/jira/browse/RF-7980
[
11:35am
]
balunasj
:
assigned to pavel from Lukas
[
11:36am
]
balunasj
:
Pavel was on - I'll ping him
[
11:36am
]
rruss
:
sounds like IE 8 is a PITA 
[
11:36am
]
balunasj
:
yes - and something QE needs to focus on
[
11:37am
]
•
balunasj
 
wishing qe were attending
[
11:37am
]
pyaschenko joined the chat room.
[
11:37am
]
rruss
:
balunasj: does prabhat et al know this?
[
11:37am
]
nbelaevski
:
balunasj: I suggest to let Konstantin do this work also assuming two things:
[
11:37am
]
nbelaevski
:
- load for tables is not heavy now
[
11:38am
]
nbelaevski
:
- extended data table is built partially on scrollable data table code
[
11:38am
]
balunasj
:
rruss: yes
[
11:38am
]
nbelaevski
:
at least investigation. Andrey or Alex can do the rest
[
11:39am
]
rruss
:
balunasj: k
[
11:39am
]
balunasj
:
nbelaevski: agreed
[
11:40am
]
nbelaevski
:
balunasj: good
[
11:40am
]
•
balunasj
 
looking at other jiras might have questions on
[
11:40am
]
nbelaevski
:
so we can reassign both to Konstantin
[
11:40am
]
balunasj
:
nbelaevski: agreed
[
11:41am
]
balunasj
:
alexsmirnov: https://jira.jboss.org/jira/browse/RF-7636
[
11:41am
]
balunasj
:
alexsmirnov: Can you describe - you moved this to 3.3.3 a while ago
[
11:42am
]
balunasj
:
nbelaevski: shall I or you assign?
[
11:42am
]
nbelaevski
:
balunasj: thanks, just done that
[
11:42am
]
balunasj
:
nbelaevski: ic
[
11:43am
]
alexsmirnov
:
That is not trivial task. I've tried to resolve that for 3.2.2 release but it seems hard enough so i put it off.
[
11:43am
]
balunasj
:
alexsmirnov: then lets not put in in 3.3.3
[
11:43am
]
nbelaevski
:
balunasj: agree
[
11:43am
]
balunasj
:
alexsmirnov: it is a feature request and out of scope I think
[
11:43am
]
alexsmirnov
:
But I can fix that for 3.3.3 , together with other valigator tasks.
[
11:44am
]
balunasj
:
alexsmirnov: but you said not trivial task
[
11:44am
]
balunasj
:
alexsmirnov: I worry about load, and RF 4.0 priorities
[
11:45am
]
alexsmirnov
:
Even more, it may be not applicable for Validator 4.0 because it uses a different message API.
[
11:46am
]
balunasj
:
alexsmirnov: so lets hold off on this - this is a focused point release
[
11:46am
]
balunasj
:
alexsmirnov: it will be different in 4.0 anyway so not gaining much.
[
11:47am
]
nbelaevski
:
have someone from community requested this?
[
11:50am
]
balunasj
:
alexsmirnov: ^ agree?
[
11:50am
]
alexsmirnov
:
I haven't seen any more requests for that feature for a while.
[
11:50am
]
balunasj
:
ok lets move it to future
[
11:51am
]
balunasj
:
done
[
11:51am
]
balunasj
:
lets move on and talk about release plans with the time we have left
[
11:52am
]
balunasj
:
amarkhel: I'm assuming you are not ready to give an estimate of the work involved in the release?
[
11:52am
]
amarkhel
:
currently not
[
11:52am
]
balunasj
:
nbelaevski: what are your thoughts - just estimate?
[
11:52am
]
balunasj
:
See agenda for my thoughts on releasing.
[
11:53am
]
nbelaevski
:
that will depend on results of Konstantin investigations
[
11:53am
]
balunasj
:
ok
[
11:54am
]
nbelaevski
:
as Alex K. will help Andrey, I think they can distribute bugs so that for example Andrey can work on JSF 2.0 and Alex on bugs
[
11:54am
]
balunasj
:
agreed
[
11:54am
]
balunasj
:
Obviously I would like to get this out asap - at the same time I want to make sure we five
[
11:54am
]
balunasj
:
give QE enough time to test completely - we can not afford another SR
[
11:54am
]
nbelaevski
:
amarkhel: I rely on you in work distribution
[
11:54am
]
balunasj
:
amarkhel: Also please do not forget about RFPL items
[
11:55am
]
amarkhel
:
ok
[
11:55am
]
balunasj
:
amarkhel: don't worry about docs and QE tasks I'll follow up with them
[
11:55am
]
nbelaevski
:
this: "BETA1 out before end of November" seems realistic goal for me
[
11:55am
]
balunasj
:
nbelaevski: yes I thought that would give enough time
[
11:56am
]
balunasj
:
Also unlike 3.3.2 we will not be adding anything new into CR1
[
11:56am
]
balunasj
:
so should be a very simple release
[
11:56am
]
nbelaevski
:
balunasj: that's true
[
11:56am
]
balunasj
:
if things look good hopefully we can follow up with GA before end of year
[
11:56am
]
balunasj
:
then everyone "new year resolution"  == RichFaces 4.0
[
11:57am
]
balunasj
:
obviously between now and then 4.0 needs a lot of work too
[
11:57am
]
balunasj
:
amarkhel: please let us know your estimates and thought on dev forum when you are ready.
[
11:58am
]
amarkhel
:
balunasj:ok
[
11:58am
]
balunasj
:
amarkhel: thanks
[
11:58am
]
balunasj
:
lets talk about the check style plugin quickly
[
11:59am
]
balunasj
:
http://www.jboss.org/community/wiki/ProposedcheckstyleconfigurationforRichfaces40
[
11:59am
]
balunasj
:
Here is the proposed settings
[
11:59am
]
balunasj
:
I was not sure about Alex K's last email and his goal - but
[
12:00pm
]
balunasj
:
I really do not want to start out with this failing builds - as I said we should introduce warnings and then at some point in future switch to errors - likely at BETA1 release
[
12:01pm
]
nbelaevski
:
balunasj: if we have checkstyle integrated in Maven build I do not see why we would get failing builds
[
12:02pm
]
nbelaevski
:
balunasj: there is not much to build - and every body should do the build before commit
[
12:02pm
]
balunasj
:
nbelaevski: originally Alex K was talking about making the level "error" which would fail builds if there were a problem - correct?
[
12:02pm
]
nbelaevski
:
balunasj: also IDE plugin will highlight problems in the code while coding
[
12:03pm
]
nbelaevski
:
balunasj: yes. also he has already fixed most of the errors
[
12:03pm
]
balunasj
:
nbelaevski: agree that everyone should be building before commit - everyone should be testing before commit too.
[
12:04pm
]
balunasj
:
nbelaevski: that part I did understand from last email
[
12:04pm
]
alexsmirnov
:
nbelaevski: That depends from settings. Maven would mark build failure if checstyle detected 'error' level problems.
[
12:04pm
]
nbelaevski
:
alexsmirnov: yes. that's what I think we should do
[
12:05pm
]
balunasj
:
nbelaevski: I propose waiting for ALPHA2 release before enforcing this - give time for comments and discussion on settings before forcing it
[
12:06pm
]
nbelaevski
:
balunasj: ok. then I have a question
[
12:06pm
]
nbelaevski
:
balunasj: http://richfaces-pulse.exadel.com:81/dashboard-report-details.html#checkstyle
[
12:06pm
]
balunasj
:
looking...
[
12:07pm
]
nbelaevski
:
balunasj: it's built in our environment and we can switch this to "root" SVN location
[
12:07pm
]
alexsmirnov
:
Keeps chekstyle to generate 'warning' level and send these warnings from build seems better solution. We could switch to 'error' level then the most of problems are fixed.
[
12:08pm
]
nbelaevski
:
balunasj: should we?
[
12:08pm
]
nbelaevski
:
alexsmirnov: Alex K. will fix most problems in the near future
[
12:08pm
]
balunasj
:
nbelaevski: this is the first I have seen this page
[
12:08pm
]
balunasj
:
nbelaevski: when was it created or generated
[
12:08pm
]
balunasj
:
nbelaevski: i.e is this new work?
[
12:09pm
]
nbelaevski
:
balunasj: I guess it's been created somewhere in 2008
[
12:09pm
]
nbelaevski
:
balunasj: there are some problems with IT work - you see it's been updated 15 May the last time
[
12:09pm
]
balunasj
:
nbelaevski: I wish I new about this before now - yes I see last time it was updated
[
12:10pm
]
rruss left the chat room. ("Leaving")
[
12:10pm
]
balunasj
:
nbelaevski: do we know if there is a check style plugin in jboss hudson?
[
12:11pm
]
nbelaevski
:
balunasj: this is site fully built using Maven, so there's no need to use special plugin for Hudson
[
12:12pm
]
nbelaevski
:
balunasj: the only thing Hudson should do is mvn site:deploy or mvn site:site and the do deployment
[
12:12pm
]
balunasj
:
nbelaevski: ok so it could live in the workspace of the builds that is good
[
12:12pm
]
nbelaevski
:
balunasj: Prabhat already set up publishing for TestNG reports, site can be published just the same
[
12:12pm
]
alexsmirnov
:
But that requres some special settings for build and webserver to deploy reports, I guess.
[
12:13pm
]
nbelaevski
:
alexsmirnov: we can use built-in Hudson web server for now
[
12:13pm
]
balunasj
:
alexsmirnov: that is where my concern is - I don't want us spending a lot of time adding functionality to hudson.
[
12:13pm
]
balunasj
:
nbelaevski: if we have a need we can ask for QE/IT to add it ( although I worry about responsiveness )
[
12:14pm
]
balunasj
:
so if we can get it to build as and live in build workspace we don't need special support  just links
[
12:14pm
]
nbelaevski
:
balunasj: we can ask our IT to do that also
[
12:14pm
]
nbelaevski
:
balunasj: that's true
[
12:15pm
]
balunasj
:
When we start needing thing like mysql DB's for sonar - that is when it gets trickier and requires planning and pushing
[
12:15pm
]
nbelaevski
:
balunasj: the only external artifact it may require is external DB for historical reports generation
[
12:15pm
]
nbelaevski
:
balunasj: personally me doesn't like these trends graphs - they are almost about nothing
[
12:15pm
]
balunasj
:
nbelaevski: you mean the ones in hudson now - if so I agree
[
12:17pm
]
balunasj
:
oh - just saw the time - I need to get going soon
[
12:18pm
]
nbelaevski
:
balunasj: no, in the past we have added graphs showing how many checkstyle we had today, yesterday and last week, etc.
[
12:18pm
]
balunasj
:
nbelaevski: lets focus on changes that don't require outside resources like DBs for now and that can live in the hudson builds workspace - perhaps even a special build for it
[
12:18pm
]
nbelaevski
:
balunasj: they required DB, were loading slowly and made the build information inactual
[
12:18pm
]
nbelaevski
:
balunasj: ok, I agree
[
12:18pm
]
balunasj
:
nbelaevski: Items that require DB we'll push off
[
12:19pm
]
nbelaevski
:
balunasj: I'm 100% for this
[
12:19pm
]
balunasj
:
trends are nice to have, but current project metrics are much more important
[
12:19pm
]
balunasj
:
nbelaevski: so please leave checkstyle at warning for now and we'll discuss later
[
12:19pm
]
nbelaevski
:
balunasj: ok
[
12:20pm
]
balunasj
:
nbelaevski: I also think that you and I should discuss the metrics but that will need to wait - I need to go
[
12:20pm
]
nbelaevski
:
balunasj: ok, good
[
12:21pm
]
balunasj
:
Thanks all - I'll wite up minutes later today or tomorrow
[
12:21pm
]
nbelaevski
:
thanks all