### Log session started at ðÆÐé 17. ð░ð▓ð│ 17:41:32 2010 ###
[17:41:32] nbelaevski [~nbelaevsk@93.191.103.3] has joined #richfaces
[17:41:32] Channel topic is: project mtg info http://tinyurl.com/nqbek5 | project http://www.jboss.org/richfaces | twitter : http://twitter.com/richfaces
[17:41:32] Topic was set by balunasj_door_cl on ðíÐÇ 19. ð░ð▓ð│ 22:01:09 2009
[17:41:32] Channel synchronized in 0.0 seconds
[17:41:34] wolfe.freenode.net [*@*] has set channel mode +cnt
[17:41:35] Channel was created at ðƒð¢ 13. ð░ð┐ÐÇ 11:37:47 2009
[17:52:34] alexsmirnov [~Adium@c-67-174-245-9.hsd1.ca.comcast.net] has joined #richfaces
[17:56:31] Alex_Kolonitsky [~akolonits@93.191.103.3] has joined #richfaces
[18:00:21] prabhaat [~prabhaat@user-0ccsrgp.cable.mindspring.com] has joined #richfaces
[18:00:44] <prabhaat> wow..i was able to login here on first attempt
[18:00:45] <ilya_shaikovsky> hello All!
[18:01:09] <ilya_shaikovsky> prabhaat, congratulations! :) Lucky day :)
[18:01:29] <prabhaat> ilya_shaikovsky, ah..I am going to buy a lottery ticket today :)
[18:01:38] <ilya_shaikovsky> :-D
[18:01:44] <ilya_shaikovsky> It's because we close to release :)
[18:01:45] <@balunasj> Hi All
[18:01:48] <ilya_shaikovsky> so we reaaaly need you :)
[18:01:52] <ppitonak> hello all
[18:01:53] <ilya_shaikovsky> balunasj, hi!
[18:02:13] <nbelaevski> hello all
[18:02:15] <@balunasj> Agenda posted, but .org very slow :-(
[18:02:18] <nbelaevski> prabhaat: congrats :)
[18:02:27] <alexsmirnov> hi
[18:02:39] <@balunasj> prabhaat: Good to see you on, and responding ;-)
[18:02:42] <@balunasj> alexsmirnov: Hi
[18:03:11] <@balunasj> and here is the link http://community.jboss.org/wiki/RichFacesTeamMeetingAgenda8-17-2010
[18:03:24] <@balunasj> lets get started
[18:03:38] <@balunasj> So M2 code freeze is friday end of day.
[18:04:02] <@balunasj> I'll build release and try to have it ready before Monday.
[18:04:23] <@balunasj> If there are issues I need to resolve with new build it might not be until monday.
[18:04:35] <@balunasj> We are still planning on a mock release today
[18:04:52] <prabhaat> balunasj, something that's really important for me is a mock release
[18:04:55] <@balunasj> Alex_Kolonitsky: and I need to work through a few things in the dist, then I'll
[18:04:56] <prabhaat> :)
[18:05:22] <@balunasj> prabhaat: Agreed - I think there will be a fair # of little gotcha's
[18:05:35] <@balunasj> prabhaat: speaking of that have you seen the staging instructions?
[18:05:45] <@balunasj> http://community.jboss.org/wiki/MavenStagingSettings
[18:05:57] <prabhaat> balunasj, yup..we need to iron those gotchas otherwise we will be in chaos next week
[18:06:19] <@balunasj> I asked a question on that to see if this would work around the maven 2 issue - because it is a full/blind mirror it might.
[18:06:32] <@balunasj> prabhaat: exactly, so we are on the same page.
[18:06:50] <prabhaat> balunasj, yup
[18:07:08] <@balunasj> prabhaat: do you think the staging settings above will fix that?  or need to wait for mock release?
[18:07:42] <prabhaat> balunasj, mock release is not only for staging settings but also to verify that we have everything set up in Hudson as well
[18:07:52] <@balunasj> yup
[18:08:05] <prabhaat> so that most of things are automated except manual testing
[18:08:28] <@balunasj> prabhaat: yup - so you'll also verify the staging stuff as well when that is out
[18:08:35] <@balunasj> lets move to dev status.
[18:08:39] <prabhaat> k
[18:08:47] <@balunasj> Build updates
[18:09:10] <@balunasj> Nearly all of the build updates are completed.
[18:09:25] <@balunasj> Alex_Kolonitsky is working on fixing the distribution build
[18:09:45] <@balunasj> and I'll be working with him, and making updates for the mock release.
[18:10:00] <@balunasj> Alex_Kolonitsky: how is the work on the distribution going?
[18:10:41] <alexsmirnov> balunasj : I did not merge CDK updates back to trunk ( I did it in brunch and testing build now ).
[18:10:54] <Alex_Kolonitsky> I few minutes I'll commit result and can check it
[18:11:04] <@balunasj> alexsmirnov: :-) yup - about to ask you about that
[18:11:17] <@balunasj> Alex_Kolonitsky: ok good - I'll review.
[18:11:22] <alexsmirnov> balunasj : It's about to done.
[18:11:40] <@balunasj> Alex_Kolonitsky: There are some other items like 777 permissions, and final name of the assembled artifacts.
[18:12:02] <@balunasj> Alex_Kolonitsky: Those are minor to me for now, but if there is time we should look too.
[18:12:41] <@balunasj> Alex_Kolonitsky: Once dist is working again though - we need to make sure the zip issues are resolved, and that the archetypes are correct.
[18:12:59] <@balunasj> prabhaat: For the mock release I'd like you guys to check those, if you can.
[18:13:01] <Alex_Kolonitsky> ok
[18:13:17] <@balunasj> Alex_Kolonitsky: They should already be in jira, and assigned
[18:13:38] <prabhaat> balunasj, better to specify that in a RFPL jira when you are ready for mock release
[18:13:53] <prabhaat> less likely to forget then :)
[18:13:53] <@balunasj> alexsmirnov: how much more time do you think you will need before you can merge to trunk?
[18:13:59] <@balunasj> prabhaat: agree
[18:15:31] <@balunasj> alexsmirnov: I don't want to have the mock release, until we get your updates, since they seem fairly widespread.
[18:15:52] <alexsmirnov> balunasj : A few hours to test result and check it into trunk.
[18:16:14] <@balunasj> alexsmirnov: ok that should work out, we've got a few hours ( or more ) as well.
[18:16:35] <@balunasj> alexsmirnov: does that include moving cdk docs into /modules/docs ?  if not I'll do that quick
[18:17:48] <alexsmirnov> Yes, it's there.
[18:18:44] <@balunasj> alexsmirnov: ok so you've already moved it in your updates.  Good, one less thing :-)
[18:19:09] <@balunasj> nbelaevski: you have soem myfaces updated in jsf-test - how long do you need for that?
[18:19:24] <nbelaevski> they are almost ready
[18:19:31] <@balunasj> ok good
[18:19:41] <nbelaevski> we need to check them in and release jsf-test
[18:19:50] <@balunasj> so we'll shoot for sync up in a couple of hours then.
[18:20:23] <@balunasj> ok
[18:20:57] <@balunasj> I have a quick question I'd like to get opinions on - hopefully it will be quick.
[18:21:39] <@balunasj> As the build stands now, ( unless we keep /trunk/build svn:externals updated at all times ) you can have build issues
[18:21:49] <@balunasj> if you just svn co /trunk
[18:22:01] <alexsmirnov> nbelaevski : Ok, I also did some improvements in jsf-test, so release would also get them into project.
[18:22:02] <@balunasj> This is because our repo settings are in richfaces-parent
[18:22:28] <@balunasj> but /trunk/pom.xml and /bom/pom.xml can get to parent
[18:22:39] <@balunasj> because they have no repo settings.
[18:22:52] <@balunasj> As I was discussing with Nick I see two options
[18:23:24] <alexsmirnov> balunasj : I supposed to have externals links for stable projects only ( so they shouldn't be updated, or even used from Jboss repo ).
[18:23:57] <@balunasj> 1) We have all dev team ( new contributors ) follow the information on getting started in the jboss wiki ( http://community.jboss.org/wiki/MavenGettingStarted-Users )
[18:24:19] <alexsmirnov> So, you can run once 'bootstrup' build ( that includes internals ), or setup jboss maven repo.
[18:24:24] <@balunasj> 2) Add repo info to both /trunk/pom.xml, and bom/pom.xml
[18:24:33] <@balunasj> or really a 3rd option
[18:25:04] <@balunasj> 3) Updated svn:externals to point to what ever is currently in use in /trunk ( i.e.
[18:25:14] <@balunasj> 10-SNAPSHOT now, and 10 after I release it)
[18:25:33] <@balunasj> 3.1) Users would then need to build -P bootstrap at least once.
[18:25:38] <@balunasj> <end>
[18:25:40] <@balunasj> thoughts?
[18:25:44] <@balunasj> alexsmirnov: thinking...
[18:26:18] <@balunasj> alexsmirnov: so you are suggesting 3) ( or users can do 1) if they wish.
[18:26:24] <@balunasj> I'm just not crazy about 2)
[18:27:00] <@balunasj> Infact paul ( meven guy at JBoss ) said he does not think repo info should be in build at all ( should in settings.xml only ).
[18:27:21] <alexsmirnov> I suggest 3). The 2 is only intermediate state if we need to update and test richfaces-parent.
[18:28:18] <@balunasj> alexsmirnov: good point - although this also means that all modules must use the same version of the svn:external items.
[18:29:07] <@balunasj> alexsmirnov: I'm also wondering if the aggregators ( /trunk/pom.xml , /trunk/core/pom.xml ) even need parents at all.  Although I have not tested if that break release builds.
[18:29:21] <alexsmirnov> balunasj : I disagree about repo. For example, I have different project that I follow ( like MyFaces, Google Guava and so on ), each of them use its own repositories.
[18:30:01] <@balunasj> alexsmirnov: right now in richfaces-parent we have the jboss repo configured, I plan on leaving it there
[18:30:11] <nbelaevski> balunasj: aggregators need parent because of plugin versions declared there
[18:30:18] <alexsmirnov> That mean dosens repositories. It's hard to maintain so many settings just to look into source code.
[18:30:36] <@balunasj> alexsmirnov: agree
[18:30:59] <@balunasj> nbelaevski: in the new system there are very few plugins declared in aggregators, but that was my concern as well.
[18:31:19] <nbelaevski> I suffered from this problem using eclipse plugin
[18:31:25] <@balunasj> as I said have not tried anything there, but just brainstorming
[18:31:38] <nbelaevski> or help plugin - snapshot version was being downloaded every time
[18:32:01] <@balunasj> alexsmirnov: We can stick with repo setting in parent I think
[18:32:43] <@balunasj> alexsmirnov: iirc paul's point was that if repo information changes, then all builds tagged will break unless you update the tag.
[18:32:54] <alexsmirnov> Yes, that is my prefference.
[18:33:02] <@balunasj> alexsmirnov: ok good
[18:33:19] <@balunasj> One last thing with build.
[18:33:47] <@balunasj> Prior to me releasing richfaces-parent 10 - I would alexsmirnov and nbelaevski to review it for anything that needs to be removed, moved, or added.
[18:33:52] <alexsmirnov> If repo is changed, that can be overrided by using the same name in settings.xml.
[18:34:07] <@balunasj> alexsmirnov: plus mirror settings
[18:34:41] <@balunasj> nbelaevski: alexsmirnov : So after we get some of the last updates done ( jsf-test update, etc...) please review it.
[18:35:03] <@balunasj> Anything else for build that needs to be discussed now?
[18:35:24] <@balunasj> lets move on to component status then https://jira.jboss.org/browse/RF-8933
[18:35:25] <jbossbot> jira [RF-8933] New 4.0.0.M2 Components [Open, Critical, Jay Balunas] https://jira.jboss.org/browse/RF-8933
[18:36:46] <@balunasj> There are two left inplaceinput and input number slider
[18:36:57] <@balunasj> status?
[18:37:44] <ilya_shaikovsky> all except autocomplete and inplaceSelect even done at showcase :) So works fine enough at least for demo :)
[18:37:47] <abelevich> main functionality of InplaceInput component is done
[18:38:02] <nbelaevski> balunasj: some bugs are left too fix: http://goo.gl/cslF
[18:38:40] <ilya_shaikovsky> nbelaevski, that's only unscheduled
[18:38:56] <ilya_shaikovsky> sorry
[18:38:58] <ilya_shaikovsky> scheduled
[18:39:00] <@balunasj> ilya_shaikovsky: ?  those are all schduled
[18:39:07] <ilya_shaikovsky> I created some during today and yesterday
[18:39:31] <ilya_shaikovsky> And some not in list but present in unscheduled is really weird
[18:39:50] <ilya_shaikovsky> like markup problems for inplace
[18:40:29] <@balunasj> ilya_shaikovsky: yes - a review of unscheduled issue is overdue
[18:40:45] <@balunasj> ilya_shaikovsky: nbelaevski : perhaps we can tackle these after the mock release is out?
[18:42:31] <@balunasj> abelevich: how much time is needed for inplaceInput?
[18:42:31] <ilya_shaikovsky> balunasj, definitelly need.. agre
[18:42:52] <ilya_shaikovsky> balunasj, I just created
[18:42:56] <ilya_shaikovsky> Anton has not reviewed
[18:43:06] <ilya_shaikovsky> I just pointed you to sample of unscheduled issue
[18:43:12] <ilya_shaikovsky> balunasj, ^
[18:43:24] <abelevich> inplaceInput is ready only junit left
[18:44:01] <@balunasj> ilya_shaikovsky: ok - perhaps you can give the list a quick review, and assign any critical issues to M2?
[18:44:08] <@balunasj> abelevich: any how much time for that?
[18:44:49] <abelevich> 4 hours
[18:45:00] <@balunasj> abelevich: ok good.
[18:45:29] <@balunasj> nbelaevski: ilya_shaikovsky : are the bugs for number slider blockers?
[18:45:39] <ilya_shaikovsky> no I believe
[18:45:55] <ilya_shaikovsky> just minor markup issue.. only if use additional arrows elements
[18:45:59] <@balunasj> nbelaevski: ilya_shaikovsky : is there more core development needed on it before the issue linked in RF-8933 is resolved?
[18:45:59] <jbossbot> jira [RF-8933] New 4.0.0.M2 Components [Open, Critical, Jay Balunas] https://jira.jboss.org/browse/RF-8933
[18:46:39] <@balunasj> I just want to make sure we get our base development done asap - and the work on bugs rest of week ( as we discussed last week ).
[18:47:33] <@balunasj> https://jira.jboss.org/browse/RF-8983
[18:47:34] <jbossbot> jira [RF-8983] InputNumberSlider component [Open, Major, Nick Belaevski] https://jira.jboss.org/browse/RF-8983
[18:47:43] <nbelaevski> RF-9095 & RF-9096 are pretty important
[18:47:45] <jbossbot> jira [RF-9095] a4j:log : misses server side exceptions. [Open, Critical, Nick Belaevski] https://jira.jboss.org/browse/RF-9095
[18:47:45] <jbossbot> jira [RF-9096] autoComplete should became just autocomplete - prior to M2 [Open, Major, Nick Belaevski] https://jira.jboss.org/browse/RF-9096
[18:48:06] <@balunasj> nbelaevski: agree
[18:48:12] <ilya_shaikovsky> balunasj, doh.. b.t.w. find out why Nick's list so short - it's points only to issues assigned to him
[18:48:20] <ilya_shaikovsky> so I thought that others in unscheduled
[18:48:48] <@balunasj> before we move on to general jira issues - I would like to finish up with
[18:48:54] <@balunasj> component core stuff
[18:49:33] <@balunasj> nbelaevski: the inputnumberslider is assigned to you, I know you are busy, can others work on it?  It should be nearly complete
[18:49:42] <ilya_shaikovsky> so I believe that all unscheduled - not really major to block release
[18:49:44] <@balunasj> Konstantin worked on it prior to vacation.
[18:50:24] <nbelaevski> no, everybody is busy
[18:50:50] <@balunasj> nbelaevski: do you have an estimate on the time required?
[18:51:13] <nbelaevski> balunasj: unfortunately no
[18:51:38] <@balunasj> nbelaevski: ok
[18:52:28] <@balunasj> Lets discuss more at the staff meeting, sounds like we need to shift, but have 3 new component for M2 :-(
[18:53:57] <@balunasj> ok
[18:54:14] <@balunasj> nbelaevski: you wanted to talk about OSGI bundles?
[18:54:17] <nbelaevski> balunasj: yes
[18:54:30] <nbelaevski> one of users asked for OSGI bundles build
[18:54:44] <nbelaevski> so I wanted to get opinions on that
[18:55:07] <nbelaevski> should not be hard to implement
[18:55:15] <@balunasj> yes - I think we should have it, and should not be too hard
[18:55:20] <@balunasj> there are tools to help
[18:55:23] <@balunasj> but not for M2
[18:55:38] <nbelaevski> agree - for 4.x builds in general
[18:56:42] <nbelaevski> balunasj: I'll assign the task to F_4.x then
[18:57:09] <@balunasj> ok good
[18:57:32] <@balunasj> QE besides mock release - any other concerns, questions etc...?
[18:57:44] Alex_Kolonitsky [~akolonits@93.191.103.3] has left #richfaces
[18:58:34] <prabhaat> balunasj, nope..we have some concerns about iteration components that lfryc  has brought before
[18:58:42] <prabhaat> balunasj, but we will look at that post M2
[18:58:55] <alexsmirnov> I have just one question - is RF trunk pass build for anyone ?
[18:58:55] <@balunasj> ok good thanks
[18:59:14] <@balunasj> alexsmirnov: yes, in hudson, my machine, etc...
[18:59:22] <@balunasj> with changes I checked in you might need to run
[18:59:25] <ppitonak> alexsmirnov: for me yes
[18:59:29] <@balunasj> mvn clean install -u ?
[18:59:31] <prabhaat> alexsmirnov, i see bom, cdk, core, examples pass in last 2 hours in Hudson
[18:59:31] <ppitonak> alexsmirnov: and also Hudson is ok
[18:59:32] <alexsmirnov> I cannot build merged brunch not trunk project.
[18:59:43] <@balunasj> but it depends on your repo setup.
[18:59:45] <prabhaat> alexsmirnov, v
[18:59:47] <prabhaat> http://hudson.qa.jboss.com/hudson/view/RF-4.0/
[18:59:48] <jbossbot> jira [RF-4] Add expression or the current row index of rich:dataTable [Closed, Major, Alexander Francuzov] https://jira.jboss.org/browse/RF-4
[19:00:18] <prabhaat> alexsmirnov, jbossbot : Palo ( ppitonak ) did the cleanup
[19:00:35] <@balunasj> alexsmirnov: You may need to build checkstyle & parent trunks.
[19:00:49] <@balunasj> alexsmirnov: That is part of where the discussion came before about repo placement ;-)
[19:01:41] <@balunasj> So here is my thinking
[19:01:45] <@balunasj> we can:
[19:01:48] <alexsmirnov> I did. Although bom module in the projects set, maven always tries to download richfaces-bom & richfaces-commons-bom from Jboss repo.
[19:02:12] <@balunasj> there is no richfaces-commons-bom anymore
[19:02:21] <alexsmirnov> I see...
[19:02:54] <@balunasj> That was one of the updates we talked about a day or two ago
[19:03:52] <@balunasj> alexsmirnov: after the meeting we can discuss work through that more if you wish?
[19:04:22] <@balunasj> so we can:
[19:04:27] <@balunasj> 1) Review unscheduled issues
[19:04:38] <alexsmirnov> balunasj : ok
[19:04:41] <@balunasj> 2) review open issues in jira for m2
[19:04:59] <@balunasj> 3) break and kkeep working on mock release
[19:05:21] <@balunasj> Either way - I think most everyone can go, unless you have input into these
[19:05:58] <nbelaevski> let's do 1) & 2)
[19:06:00] <nbelaevski> ?
[19:06:34] <@balunasj> Sure, but we may need to break - I'll need caffeine for both ;-)
[19:07:02] <alexsmirnov> Me too :-)
[19:07:11] <@balunasj> hehe
[19:07:16] <nbelaevski> I need ice-cream :)
[19:07:20] <@balunasj> So lets take a quick break and start on
[19:07:21] <@balunasj> https://jira.jboss.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+RF+AND+resolution+%3D+Unresolved+AND+fixVersion+is+EMPTY+ORDER+BY+affectedVersion+ASC,+priority+DESC
[19:07:29] <@balunasj> nbelaevski: we all have our needs ;-)
[19:07:37] <nbelaevski> :)
[19:09:07] <ilya_shaikovsky> guys.. sorry but have to go.. I will check postponed to next milestones ones tommorow and ping you if think that can't workaround something postponed at showcases :)
[19:09:12] <ilya_shaikovsky> balunasj, if this ok?
[19:12:10] cofeineSunshine [~justinas@78-60-23-252.static.zebra.lt] has quit IRC: Ping timeout: 245 seconds
[19:13:17] <@balunasj> ok I'm back
[19:13:30] <@balunasj> ilya_shaikovsky: ok np
[19:13:41] ilya_shaikovsky [~x3User255@93.191.103.3] has quit IRC: Ping timeout: 258 seconds