balunasj
:
http://www.jboss.org/community/wiki/RichFacesTeamMeetingAgenda12-8-2009
[
11:05am
]
abelevich
:
))
[
11:05am
]
balunasj
:
Thats my roster page on internal page
[
11:05am
]
balunasj
:
Ok so I was out of touch most of last week
[
11:06am
]
smcgowan joined the chat room.
[
11:06am
]
balunasj
:
I just finished getting caught up on corp emails and stuff like that
[
11:06am
]
balunasj
:
Hi smcgowan
[
11:06am
]
smcgowan
:
good morning, jay
[
11:07am
]
balunasj
:
So the first thing I want to cover is QE status and jopr testing
[
11:07am
]
balunasj
:
I know we had a rebuild last week.
[
11:08am
]
balunasj
:
Since smcgowan and lfryc are here lets talk about that.
[
11:08am
]
balunasj
:
lfryc: was telling me there are some unrelated issues that will delay full jopr testing - true?
[
11:09am
]
smcgowan
:
balunasj:  yes, using EMBJOPR/trunk, we include snapshots of RHQ and JOPR, there was a recent change in RHQ which is not backwards compatible, but required, that prohibits embjopr from building
[
11:09am
]
smcgowan
:
balunasj:  ispringer recently tagged RHQ 1.3.0.GA but that is not working as the jbossas server instance is not detected,
[
11:09am
]
balunasj
:
smcgowan: ok - is there a way to test with an older version just to get a baseline before BETA1 release?
[
11:09am
]
smcgowan
:
ya, it's ugly
[
11:10am
]
balunasj
:
smcgowan: ouch
[
11:10am
]
smcgowan
:
balunasj:  i believe that is what lfryc is currently doing
[
11:10am
]
lfryc
:
smcgowan: but this is not the blocker, because we can just build it with older versions
[
11:10am
]
lfryc
:
smcgowan: the current works stopped the issue what is solving Ondra Zizka
[
11:10am
]
lfryc
:
smcgowan: its https://jira.jboss.org/jira/browse/JBQA-2775
[
11:11am
]
lfryc
:
smcgowan: it causes fail of the most of tests in jsfunit testsuite for embjopr
[
11:11am
]
smcgowan
:
https://jira.jboss.org/jira/browse/EMBJOPR-101
[
11:11am
]
•
balunasj
 
looking....
[
11:11am
]
lfryc
:
smcgowan: yeah, its right actually
[
11:12am
]
smcgowan
:
the resolution to these issues are needed to be done in EMBJOPR trunk, so we need to move forward
[
11:13am
]
balunasj
:
smcgowan: lfryc : but can't we take an older version of all of this from when they were trying to create AS 5.2 beta and swap in the new RF jars and JSF 2
[
11:13am
]
balunasj
:
prior to the myfaces changes.
[
11:13am
]
balunasj
:
For me I just want to make sure nothing critical is broken.  Minor issues can be addressed in a CR if needed.
[
11:13am
]
•
balunasj
 
as long as not large #
[
11:14am
]
lfryc
:
balunasj: smcgowan: I have discuss with ozizka the solutions a he promise me the help with manual testing the embjopr for with RF/JSF2
[
11:14am
]
balunasj
:
lfryc: but isn't that not until next week?
[
11:14am
]
smcgowan
:
that's what I was going to suggest, manual testing may be the best approach as an interim solution
[
11:14am
]
balunasj
:
smcgowan: agreed - I just want to make sure we are on a good track since this is a beta.
[
11:14am
]
lfryc
:
balunasj: He actually promised me help tomorrow.. if somebody will prepare the war for him
[
11:15am
]
balunasj
:
i.e. our apps and tests are going ok ( a couple of issues ).
[
11:15am
]
balunasj
:
so I think it will be ok, but not sure.
[
11:15am
]
balunasj
:
lfryc: what war do you mean?  Jopr + 3.3.3 + JSF 2?
[
11:15am
]
lfryc
:
balunasj: yeah, for AS 6.0.0.M1
[
11:16am
]
balunasj
:
lfryc: isn't that the version with the issues described above?
[
11:16am
]
prabhat
:
balunasj: smcgowan lfryc I was under the impression that manual testing with older version of JOPR will happen in parallel as we figured out test setup issue with JOPR
[
11:17am
]
lfryc
:
balunasj: I tried the embjopr with AS 6.0.0.M1 manually and it works for me locally..
[
11:17am
]
prabhat
:
lfryc: there you go
[
11:17am
]
lfryc
:
balunasj: the issues mentioned above are related to jsfunit/rhino
[
11:17am
]
lfryc
:
(afaik)
[
11:17am
]
smcgowan
:
right ^^
[
11:17am
]
balunasj
:
lfryc: ok good   and assuming that was with jsf 2 and 3.3.3 right
[
11:17am
]
smcgowan
:
me too, the console looks good to me as well
[
11:18am
]
smcgowan
:
yes
[
11:18am
]
lfryc
:
balunasj: right..
[
11:18am
]
balunasj
:
lfryc: smcgowan : awesome!
[
11:18am
]
prabhat
:
balunasj: i think this being a beta release, we should be fine
[
11:18am
]
smcgowan
:
i agree
[
11:18am
]
balunasj
:
prabhat: agreed
[
11:18am
]
lfryc
:
balunasj: so we will initiate the manual testing yesterday, it should take no more than 2 hours for ozizka with my support
[
11:19am
]
lfryc
:
(yesterday=tomorrow)
[
11:19am
]
prabhat
:
lfryc: you mean tomorrow?
[
11:19am
]
balunasj
:
I still want effort done for getting the actual tests running with jopr in parallel  ( by the jopr team)
[
11:19am
]
smcgowan
:
balunasj:  that be me
[
11:19am
]
balunasj
:
so that prior to CR1 the suite can be executed
[
11:19am
]
balunasj
:
smcgowan:
[
11:19am
]
smcgowan
:
and we're still working that
[
11:20am
]
prabhat
:
so all clear on jopr status?
[
11:20am
]
balunasj
:
ok given we will not be releasing 3.3.3 this week plan for a CR1 in the beginning part of January.
[
11:20am
]
smcgowan
:
the RHQ regression occurred last Thursday so we need to resolve, the 1.3.0.GA release was intended as an interim solution which did not work out
[
11:20am
]
balunasj
:
smcgowan: ok
[
11:21am
]
prabhat
:
balunasj: i did not get you..not releasing 3.3.3  meaning because of jsf2 problems that Lukas found?
[
11:21am
]
balunasj
:
so to echo prabhat jopr status is good for BETA release and you will plan on testsuite runs for CR1
[
11:22am
]
balunasj
:
prabhat: well we need to discuss the rest of QE status but going by https://jira.jboss.org/jira/browse/RFPL-273
[
11:22am
]
balunasj
:
it did not seem likely we would release this week.
[
11:22am
]
balunasj
:
so lets move on to general QE status
[
11:22am
]
balunasj
:
smcgowan: thanks for your help
[
11:22am
]
prabhat
:
balunasj: ya
[
11:22am
]
prabhat
:
balunasj: known issue first
[
11:23am
]
smcgowan
:
balunasj:  sure, i'll stay in contact with lfryc and ozizka
[
11:23am
]
balunasj
:
smcgowan: excellent thanks
[
11:23am
]
prabhat
:
balunasj: photoalbum fix ?
[
11:24am
]
balunasj
:
prabhat: link?
[
11:25am
]
prabhat
:
balunasj: there is a jira for it...just a sec
[
11:25am
]
balunasj
:
https://jira.jboss.org/jira/browse/RF-8182
[
11:25am
]
balunasj
:
This was resolved on Sat.  But last build for QE was Thur by Konstantin1
[
11:26am
]
prabhat
:
balunasj: ya, it's fixed but what i mean is that did we get the updated app in exadel maven?
[
11:26am
]
prabhat
:
/s/maven/repo
[
11:26am
]
balunasj
:
prabhat: right so you mean a rebuilt dist in general correct?
[
11:27am
]
prabhat
:
balunasj: i think one phoablum has to be rebuilt..this saves us from retesting
[
11:27am
]
balunasj
:
I think we will need to review some of the open/new issues and deside if we need another build for you.
[
11:27am
]
prabhat
:
balunasj: ok
[
11:27am
]
balunasj
:
is https://jira.jboss.org/jira/browse/RFPL-273 up to date?
[
11:27am
]
prabhat
:
balunasj: yes
[
11:28am
]
balunasj
:
prabhat: and how much would a new build set you back?
[
11:28am
]
lfryc
:
(with exception of 5, it is done for Thur release)
[
11:28am
]
prabhat
:
balunasj: if issues that lfryc found with jsf2 are not critical for beta release, i propose to move ahead with release
[
11:28am
]
lfryc
:
(and afaik 6 too)
[
11:29am
]
prabhat
:
balunasj: but would like to get others opinion as well
[
11:29am
]
balunasj
:
lfryc: so you are saying all but 5/6 you are finished with this?
[
11:29am
]
balunasj
:
prabhat: agreed - has anyone been able to look at new JSF2 issues?
[
11:29am
]
balunasj
:
https://jira.jboss.org/jira/secure/BrowseVersion.jspa?id=12310341&versionId=12314119&showOpenIssuesOnly=true
[
11:29am
]
ppitonak_
:
balunasj: for me, only photoalbum has to be tested
[
11:29am
]
balunasj
:
amarkhel: ?
[
11:30am
]
lfryc
:
balunasj: no, the 1, 2, 5, 6, 9 subtasks is done for Thur release
[
11:30am
]
amarkhel
:
Currently I am working on this issues
[
11:32am
]
balunasj
:
amarkhel: ok - any estimate to understanding them better - i.e. determine priority?
[
11:33am
]
nbelaevski
:
balunasj: amarkhel has some more reported issues from users to investigate
[
11:33am
]
nbelaevski
:
balunasj: they're workign both with Alex on this
[
11:33am
]
amarkhel
:
I haven't idea for now... 2 issues(with view couldn't be restored) seems similar
[
11:33am
]
balunasj
:
amarkhel: agreed they do seem similar
[
11:34am
]
balunasj
:
nbelaevski: ok is it the issue we commented on yesterday?
[
11:34am
]
nbelaevski
:
balunasj: no, that are another ones - I'm talking about bugs from users
[
11:35am
]
amarkhel
:
balunasj: I can't estimate this bugs right now.. I need to time to look, previously I looked at users bugs
[
11:35am
]
balunasj
:
nbelaevski: ok - so these don't have jira's yet or are not assigned to release yet.
[
11:35am
]
prabhat
:
nbelaevski: you think these (those that Lukas found with JSF2) are critical enough that we have to get these fixed in this release or can we do it in next release?
[
11:36am
]
balunasj
:
amarkhel: ok - that is what Nick is saying too
[
11:36am
]
nbelaevski
:
balunasj: they're in unscheduled currently: https://jira.jboss.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310341&fixfor=-1
[
11:36am
]
•
balunasj
 
looking....
[
11:36am
]
nbelaevski
:
balunasj: Andrey is investigating, after this I'm going to assign particular version
[
11:37am
]
balunasj
:
nbelaevski: ok
[
11:37am
]
balunasj
:
nbelaevski: do you think that investigating the JSF2 issues might be higher priority?
[
11:39am
]
balunasj
:
my concern is getting BETA1 stable enough and in a state that we don't need a BETA2 and can move to CR1 after this.
[
11:39am
]
nbelaevski
:
balunasj: 50/50. issues from users won't take much time, so I'll pass them in order to have more clarified view on our scope
[
11:40am
]
nbelaevski
:
balunasj: again, that's investigation only, not fixing. fixing can go for CR1 if necessary
[
11:40am
]
balunasj
:
nbelaevski: ok - well lets figure out timeframes and limits so that we can give QE a estimate for a final BETA1 build
[
11:41am
]
•
prabhat
 
is worried about 3rd iteration..will prefer beta2 instead
[
11:42am
]
balunasj
:
prabhat: hmm, would prefer not to have beta2 what concerns you about 3rd iteration?
[
11:42am
]
nbelaevski
:
this one: https://jira.jboss.org/jira/browse/RF-8194 is likely to be caused by implicit naviation in JSF2
[
11:42am
]
nbelaevski
:
I'd prefer to fix it in tests themselves
[
11:42am
]
prabhat
:
nbelaevski: you mean problem is with test?
[
11:43am
]
prabhat
:
nbelaevski: i think i did not get you
[
11:43am
]
nbelaevski
:
prabhat: test is calling non-existing page. JSF2 does implicit navigation, while JSF 1.2 does not
[
11:43am
]
prabhat
:
nbelaevski: true
[
11:43am
]
nbelaevski
:
prabhat: "switch" is that implicit navigation
[
11:44am
]
nbelaevski
:
prabhat: so I suggest to fix this check in tests
[
11:44am
]
lfryc
:
prabhat, nbelaevski: this is not covered by tests yet, it came from manual testing
[
11:44am
]
prabhat
:
nbelaevski: i see
[
11:44am
]
nbelaevski
:
lfryc: I remember I've seen such in rf-demo auto tests...
[
11:45am
]
lfryc
:
nbelaevski: whole RichFaces Miscs. isn't covered
[
11:46am
]
lfryc
:
(it actually doesnt matter)
[
11:46am
]
nbelaevski
:
lfryc: hmm, maybe it's not the case then. I've seen such in a4j:include demo test
[
11:46am
]
balunasj
:
lets refocus on estimates and priorities instead of digging into specific issues.
[
11:46am
]
balunasj
:
we can break and discuss as needed offline for specific items.
[
11:46am
]
nbelaevski
:
balunasj: right, sorry
[
11:46am
]
prabhat
:
balunasj: the reason for me pushing for beta2 is if we get new binaries for whole thing, we are going to retest whole thing. So work load for both approach is pretty much same.
[
11:46am
]
prabhat
:
balunasj: if we push beta1 out, community may find  more issues..we fix that in beta2 which means more stable CR1
[
11:47am
]
paliboy joined the chat room.
[
11:47am
]
balunasj
:
prabhat: very fair point.
[
11:47am
]
paliboy is now known as ppitonak.
[
11:47am
]
ppitonak_ left the chat room. ("Konversation terminated!")
[
11:47am
]
ppitonak left the chat room. (Client Quit)
[
11:47am
]
nbelaevski
:
prabhat, balunasj: how much time between BETA1 and BETA2 are we planning?
[
11:47am
]
ppitonak joined the chat room.
[
11:47am
]
prabhat
:
balunasj: given that we are calling it beta1, it wont look too bad. It also gives us (Lukas and Palo) some more time to write simple app related to JSF
[
11:47am
]
balunasj
:
prabhat: if we did that we would need a fairly rapid turn around.
[
11:47am
]
prabhat
:
oops related to JSF2 not JSF
[
11:47am
]
balunasj
:
nbelaevski: not even sure we'll do a BETA2 yet
[
11:48am
]
nbelaevski
:
balunasj: if we put small term between releases, community feedback can be limited
[
11:49am
]
prabhat
:
balunasj: nbelaevski that's how I think of course but I am flexible
[
11:49am
]
balunasj
:
nbelaevski: agreed that is part of why I'm not convinced of a BETA1 - because we still need 3.3.3.GA by end of Jan.
[
11:49am
]
balunasj
:
I also think we'll get limited community feedback on x-mas break
[
11:50am
]
nbelaevski
:
balunasj: yes, end of year + XMas
[
11:50am
]
ilya_shaikovsky
:
yup.. forum activitie already get lower than usually
[
11:51am
]
balunasj
:
prabhat: lfryc : how much time is needed to finish testing with build you got last Thur.
[
11:51am
]
balunasj
:
?
[
11:53am
]
ppitonak
:
balunasj: photoalbum can be tested in less than one day on all platforms and browsers
[
11:53am
]
lfryc
:
balunasj: I think we can finish it tomorrow incl. embjopr testing
[
11:53am
]
balunasj
:
ppitonak: you mean time left, or total time for testing?
[
11:53am
]
balunasj
:
lfryc: ok
[
11:54am
]
ppitonak
:
balunasj: as Lukas said
[
11:54am
]
balunasj
:
So this would mean we could release next week for a B1, but might require a B2 depending on # and severity of issues found.
[
11:55am
]
balunasj
:
Or we take some extra time and provide QE with another BETA1 build with current issues found
[
11:55am
]
prabhat left the chat room. (brown.freenode.net irc.freenode.net)
[
11:55am
]
balunasj
:
and release BETA1 later next week or first thing week of x-mas
[
11:56am
]
balunasj
:
and hopefully not need a B2 and do a CR1 Mid Jan.
[
11:56am
]
balunasj
:
nbelaevski: alexsmirnov : amarkhel : would like your thoughts on this?
[
11:57am
]
balunasj
:
personally I'm thinking give an extra week for B1 because we will have limited feedback from community over x-mas and short turn around to a B2
[
11:57am
]
balunasj
:
so we might as well get B1 more solid
[
12:00pm
]
balunasj
:
any other comments?
[
12:01pm
]
balunasj
:
prabhat is having client issues
[
12:01pm
]
balunasj
:
we'll wait for him to join back
[
12:01pm
]
balunasj
:
ilya_shaikovsky: What do you think about that plan?

///// irc server/client issues cont. below

balunasj
:
Did others get dropped?
[
12:05pm
]
kmix left the chat room. (Read error: 104 (Connection reset by peer))
[
12:05pm
]
nbelaevski
:
yes, just connected to us again
[
12:05pm
]
prabhat
:
balunasj: looks like
[
12:06pm
]
balunasj
:
I saw 8-10 people drop - knew something was up.
[
12:06pm
]
balunasj
:
last posts from me:
[
12:07pm
]
balunasj
:
Nick saw nearly my last post - 18:59:33] balunasj: so we might as well get B1 more solid
[
12:07pm
]
amarkhel left the chat room. ("ChatZilla 0.9.85 [Firefox 3.5.5/20091102152451]")
[
12:07pm
]
prabhat
:
balunasj: and I said I am fine with a respin of current beta if that's what most of us feel like
[
12:07pm
]
prabhat
:
/s/most/majority
[
12:07pm
]
balunasj
:
I'm just looking for feedback and opinion on pushing B1 out a week to make is more solid since community feedback will be limited.
[
12:08pm
]
balunasj
:
prabhat: ok
[
12:08pm
]
balunasj
:
nbelaevski: ilya_shaikovsky alexsmirnov : what do you guys thing/
[
12:08pm
]
balunasj
:
?
[
12:08pm
]
balunasj
:
think?
[
12:08pm
]
nbelaevski
:
balunasj: I'm for B1 later this week and CR1 mid Jan
[
12:09pm
]
prabhat
:
balunasj: what I also had argued earlier when I got disconnected is: "If end Jan is GA release then that still does not give too much time for feedback for CR assuming we release CR somewhere in mid Jan ;)"
[
12:09pm
]
balunasj
:
nbelaevski: That would be a updated B1 build to QE later this week right?  Then we would release B1 later next week.
[
12:09pm
]
nbelaevski
:
balunasj: yes
[
12:09pm
]
ilya_shaikovsky
:
balunasj, yes sounds good
[
12:09pm
]
balunasj
:
nbelaevski: ok
[
12:10pm
]
prabhat
:
balunasj: sounds good
[
12:10pm
]
balunasj
:
prabhat: I would prefer longer time for CR1 to "bake"
[
12:10pm
]
balunasj
:
as well.  The only way we could that is if everyone is working on other tasks at the same time.
[
12:11pm
]
balunasj
:
There would be no active development once in CR1
[
12:11pm
]
prabhat
:
balunasj: so as usual..please send an email when respin is done and bits are uploaded
[
12:11pm
]
balunasj
:
only critical issues & we would all need to push this release in the community ( I'm planning a "how to" blog for JSF 2, rf 3.3.3, and AS 6. with the RF demo.
[
12:12pm
]
balunasj
:
prabhat: ok
[
12:12pm
]
ppitonak_
:
balunasj: we need all binaries in exadel's maven repo
[
12:12pm
]
balunasj
:
I'll work with nbelaevski  and markhel to figure out a cut off date and release plan to get this to you.
[
12:12pm
]
balunasj
:
ppitonak_: you mean for the respin this week?
[
12:12pm
]
clerum left the chat room. (Read error: 104 (Connection reset by peer))
[
12:12pm
]
ppitonak_
:
balunasj: yes
[
12:13pm
]
balunasj
:
ppitonak_: it will be a regular distribution and updates for QE.
[
12:13pm
]
ppitonak_
:
balunasj: the first build of B1 wasn't in maven repo
[
12:13pm
]
alexsmirnov
:
have three releases for six weeks would be too much. I'm for B1/CR1/GA.
[
12:13pm
]
alexsmirnov
:
s/three/four/
[
12:14pm
]
smcgowan left the chat room. (Read error: 113 (No route to host))
[
12:14pm
]
balunasj
:
alexsmirnov: true - that is why we are only having B1 release late next week or Monday following
[
12:14pm
]
balunasj
:
plan for a CR1 mid January
[
12:14pm
]
balunasj
:
and let that "bake" for a while
[
12:14pm
]
wesleyhales left the chat room. (simmons.freenode.net irc.freenode.net)
[
12:14pm
]
ppitonak left the chat room. (simmons.freenode.net irc.freenode.net)
[
12:14pm
]
pmuir left the chat room. (simmons.freenode.net irc.freenode.net)
[
12:14pm
]
balunasj
:
perhaps delay GA release a bit
[
12:15pm
]
ppitonak joined the chat room.
[
12:15pm
]
wesleyhales joined the chat room.
[
12:15pm
]
pmuir joined the chat room.
[
12:15pm
]
clerum joined the chat room.
[
12:15pm
]
•
balunasj
 
during that time we'll all need to blog, push the CR1 for testing.
[
12:15pm
]
balunasj
:
Perhaps release GA in mid feb.
[
12:15pm
]
balunasj
:
alexsmirnov: wdyt?
[
12:16pm
]
prabhat
:
balunasj: i think 2 weeks between CR and GA is too short
[
12:16pm
]
balunasj
:
n.b. between CR1 and GA we'll not be actively developing in 3.3.3 - we'll be moving on to 4.0.
[
12:16pm
]
balunasj
:
prabhat: agreed - this would be about 4 weeks
[
12:17pm
]
nbelaevski
:
balunasj: well, if time permits, I'd agree with the plan
[
12:17pm
]
nbelaevski
:
more time for community to check is always better
[
12:17pm
]
balunasj
:
nbelaevski: agreed
[
12:17pm
]
alexsmirnov
:
nbelaevski: agreed too.
[
12:17pm
]
ilya_shaikovsky
:
balunasj, prabhat, I also believe that we need to try involve the community in testing as much as possible before GA espesially if want to finish with 3.3.x releases .. so seems reasonable shift
[
12:17pm
]
balunasj
:
plus with a CR1 we are more likely to get community members to check it out.
[
12:18pm
]
prabhat
:
ilya_shaikovsky: +1
[
12:18pm
]
balunasj
:
ilya_shaikovsky: Agreed and I've already had several people off to assist with 3.3.3 so I think we'll be in good shape.
[
12:19pm
]
balunasj
:
ok so that is the plan - nbelaevski lets discuss a plan for dev freeze this week offline.
[
12:19pm
]
•
balunasj
 
thinking I should have started with jsfsummit review....
[
12:19pm
]
nbelaevski
:
balunasj: ok
[
12:19pm
]
prabhat
:
balunasj: review will be good in email or blog
[
12:20pm
]
balunasj
:
Yup - I'm going to follow up Dan's update with mine later in the week
[
12:20pm
]
•
balunasj
 
wondering how plates get so full so fast..... I need a bowl....
[
12:22pm
]
balunasj
:
ok lets go with that and we'll review later
[
12:22pm
]
balunasj
:
thanks all