Version 1
    balunasj: struberg: In this meeting alone we have people in Australia, Texas, New York, and Minsk.
    [10:01pm] struberg: hrhr
    [10:01pm] balunasj: serogers: Hi Sean
    [10:01pm] serogers: Hi Jay, hi everyone
    [10:01pm] ilya_shaikovsky: serogers, Hi!
    [10:01pm] struberg: I think my question was about the RichFaces-3.3.3-jsf2 bringing in a dependency on jsp-api
    [10:02pm] struberg: for the non - jsf2 artifact, this dependency is not inherited (optional)
    [10:02pm] balunasj: struberg: we need to start doc meeting right now, but do you think you could bring this up with some details on the forums?
    [10:02pm] balunasj: struberg: This is something we would need to investigate.
    [10:02pm] struberg: but for jsf2 it comes along (and clashes my tomcat with a duplicate ExpressionLanguageFactory because it already has geronimo-el)
    [10:03pm] balunasj: serogers: I updated the agenda you sent out with some more details, but the basics are the same -
    [10:03pm] struberg: I'm not even subscribed to the richfaces forum yet, only weld-dev and seam-dev
    [10:03pm] serogers: balunasj: thanks, I saw that, it looks good
    [10:03pm] struberg: but will do - txs and good luck for the meeting
    [10:04pm] balunasj: struberg: thanks for letting us know you ran into something
    [10:04pm] balunasj: serogers: I'm sorry I missed the last meeting - JSFSummit was very busy.
    [10:05pm] serogers: No problem Jay
    [10:05pm] balunasj: serogers: I think we can get started
    [10:05pm] serogers: Great
    [10:06pm] serogers: First on the agenda is the release schedule. Do we have any firm dates for 4.0, or for future 3.3.3 releases?
    [10:07pm] balunasj: serogers: 4.0 is a little more cloudy   because of some issues that have been discussed with EG, and because of the 3.3.3 release.
    [10:08pm] balunasj: serogers: First thing next year we are going to plan out the timeline in more detail with the updates based on the above items.
    [10:08pm] balunasj: serogers: Because 4.0 work has been going on in parallel
    [10:09pm] serogers: balunasj: OK. That sort of leads into the next item on the agenda which is whether I should put more work into the 3.3.3 docs than just maintenance
    [10:09pm] balunasj: serogers: I hope we can get an ALPHA 2 release out end of February.  nbelaevski - seem reasonable?
    [10:09pm] serogers: OK, I'll keep that in mind
    [10:10pm] nbelaevski: balunasj: yes
    [10:10pm] balunasj: serogers: Because the 3.3.3 release is going to add JSF 2.0 support I think we need have a chapter or section on that for the CR1/GA release.
    [10:11pm] balunasj: we discussed this at the team meeting, and there were mixed thoughts on it.
    [10:11pm] serogers: OK
    [10:11pm] balunasj: either keep it just wiki based, or actually have a section in the docs.
    [10:11pm] balunasj: serogers: I've been thinking about this more and I think a section in the docs is needed
    [10:11pm] serogers: It is probably worth having in the docs. I will at least be able to re-use it in the 4.0 docs
    [10:12pm] serogers: For the most part
    [10:12pm] balunasj: serogers: but for BETA1 release we don't need it in yet.  The wiki page is being created now by ilya_shaikovsky
    [10:12pm] ilya_shaikovsky: serogers, I will contains mainly for specific settiong for 3.3.3 and limitations...?
    [10:12pm] ilya_shaikovsky: so I'm not sure about re-use
    [10:12pm] ilya_shaikovsky: ...? - ? sign not needed
    [10:12pm] balunasj: serogers: I'm not sure how much can be moved to 4.0.
    [10:12pm] ilya_shaikovsky: balunasj, that was I mean
    [10:12pm] serogers: ilya_shaikovsky: OK, no problem
    [10:13pm] balunasj: yup
    [10:13pm] balunasj: serogers: the 3.3.3 doc update will hopefully not be too hard or too involved.  It should be roughly based on the wiki but with more content or explanations.
    [10:14pm] serogers: OK
    [10:14pm] ilya_shaikovsky: So I'm not sure that we should cover that in guide instead of having just wiki page to which we could point the users from all resources..
    [10:14pm] balunasj: serogers: I was thinking it could be part of the getting started section, with perhaps a link to details in the migration guide.
    [10:14pm] serogers: That sounds good
    [10:14pm] balunasj: ilya_shaikovsky: why?
    [10:15pm] ilya_shaikovsky: I'm not against - just not sure If this really needed
    [10:16pm] nbelaevski: ilya_shaikovsky: what about users downloading distro?
    [10:16pm] nbelaevski: ilya_shaikovsky: docs are included, but wiki page wouldn't
    [10:16pm] balunasj: ilya_shaikovsky: ok  - are you thinking people don't really read the guide?
    [10:16pm] ilya_shaikovsky: nbelaevski, good point
    [10:17pm] ilya_shaikovsky: balunasj, no I'm not think so.. think that this just specific settings info.. but seems finally you guys right.. guys who downloaded distro will wait that this info will be in docs
    [10:17pm] ilya_shaikovsky: bundled
    [10:19pm] balunasj: I'll also put on my corporate hat
    [10:19pm] balunasj: and say that the docs are part of the enterprise releases as well ( with some updates ).
    [10:19pm] ilya_shaikovsky:
    [10:20pm] balunasj: serogers: Lets create some jira's for CR1 related to this.
    [10:20pm] serogers: balunasj: OK
    [10:20pm] balunasj: serogers: Including a review of wiki page ilya_shaikovsky is writing.
    [10:20pm] nbelaevski: balunasj: well said
    [10:20pm] balunasj: serogers: lets wrap up the release schedule for 3.3.3
    [10:21pm] serogers: OK
    [10:21pm] balunasj: serogers: We are hoping to get BETA1 out first thing next week
    [10:21pm] balunasj: Then we'll have either a BETA2 or CR1 likely in mid/lat January.
    [10:21pm] _eMaX_1 joined the chat room.
    [10:21pm] _eMaX_1: hi all
    [10:22pm] balunasj: We'll have the beta2 if there are critical issues found, or if there are enough jira issues to warrant another release.
    [10:22pm] _eMaX_1: anyone here knows how to open a popup window in a richtable as a response to a doubleclick that is parameterized with information from the row the doubleclick went on?
    [10:22pm] nbelaevski: serogers, balunasj: I have a question for docs & 3.3.x
    [10:23pm] balunasj: _eMaX_1: Hi, we are currently in a mtg, can you ask you question in about 40 min?
    [10:23pm] nbelaevski: ?
    [10:23pm] balunasj: _eMaX_1: or on the forums.
    [10:23pm] _eMaX_1: of course I'm sorry, no problem
    [10:23pm] balunasj: _eMaX_1: np
    [10:23pm] balunasj: nbelaevski: looking...
    [10:24pm] nbelaevski: serogers: look through them from time to time and assign fix version - I don't know which one to select for you not to get overloaded
    [10:24pm] serogers: nbelaevski: OK, I'll check it out
    [10:24pm] nbelaevski: balunasj: that's link for general unscheduled issues, some are pretty old, that's why I raised the question
    [10:24pm] nbelaevski: serogers: thanks!
    [10:24pm] balunasj: nbelaevski: agreed
    [10:25pm] balunasj: serogers: for now any issues you think will make it into 3.3.3 set a fix for release of 3.3.3.CR1
    [10:25pm] balunasj: serogers: if we have a BETA2 we'll adjust then.
    [10:25pm] serogers: balunasj: OK, will do
    [10:26pm] balunasj: serogers: regarding 3.3.3.BETA1 release - we need to create a doc bundle of what is there for uploading.
    [10:26pm] balunasj: serogers: is that something you are comfortable with.
    [10:27pm] serogers: balunasj: I was looking at doing that today. I can get the docs building no problems but the API refs I was having some trouble getting
    [10:28pm] balunasj: serogers: is that covered in the doc build instructions from 3.3.X or is that missing?
    [10:28pm] _eMaX_1: I've also noted a potential issue with richtree when used together with a primefaces layoutunit, I'll post that on the forum
    [10:28pm] balunasj: _eMaX_1: excellent thanks
    [10:28pm] serogers: balunasj: that was missing
    [10:29pm] balunasj: serogers: doh
    [10:29pm] balunasj: nbelaevski: ilya_shaikovsky : do either of you know how this was integrated into doc bundles?
    [10:29pm] nbelaevski: balunasj: looking
    [10:30pm] serogers: I found a shell script that seemed like it would do it, but it failed when I ran it
    [10:30pm] serogers: it was called
    [10:30pm] balunasj: while nbelaevski is looking I'll wrap up the release plan.
    [10:31pm] balunasj: Depending if the next release is CR1 or BETA1 will obviously determine our schedule.
    [10:32pm] balunasj: If it is CR1 then we'll have that in the community for 2 weeks, and then post GA sometime in early to mid February.
    [10:32pm] balunasj: if it is a BETA2 we'll likely need to give it even more time for people to try out and for our own testing.
    [10:32pm] balunasj: So it would push out to end of February/March.
    [10:33pm] serogers: OK
    [10:33pm] lfryc left the chat room. ("Leaving")
    [10:33pm] nbelaevski: serogers: checked 3.3.1.GA distribution
    [10:33pm] balunasj: The idea here is to put 3.3.X on the shelf in a stable and clean state so we can all move on to 4.0 with a clean slate
    [10:34pm] nbelaevski: serogers: API docs are built for api, impl and ui projects externally to docs module and then just packaged together
    [10:35pm] serogers: nbelaevski: is there an automatic process somehow or do I need to manually copy the files?
    [10:35pm] nbelaevski: serogers: at least, that's what I see after quick observation
    [10:36pm] nbelaevski: serogers: they should be copied automatically when ui\assembly is built
    [10:36pm] nbelaevski: serogers: you need to use Maven profile named "release", command switch is '-P release' for it to activate
    [10:37pm] serogers: nbelaevski: Ah, I see, thanks
    [10:37pm] balunasj: nbelaevski: thanks
    [10:37pm] nbelaevski: serogers: you welcome. please let me know if you have additional problems with this
    [10:38pm] serogers: No problem. I will try again tomorrow
    [10:38pm] balunasj: serogers: so if you can work on a doc bundle for 3.3.3.BETA1 that would be good.
    [10:38pm] balunasj: serogers: please put in a jira for RFPL for BETA1 release for this.
    [10:38pm] balunasj: serogers: excellent.
    [10:39pm] balunasj: serogers: any thing else for 3.3.3 before we move on to 4.0?
    [10:40pm] serogers: Once it is packaged, does that commit it? Or do I need to send it to someone?
    [10:40pm] balunasj: serogers: The bundle will be pretty big
    [10:40pm] lfryc joined the chat room.
    [10:40pm] balunasj: serogers: you need to host it somewhere where IT can access
    [10:41pm] balunasj: serogers: Then either you or I can write IT and have them upload and update
    [10:41pm] balunasj: serogers: this used to be something we could do directly, but now is restricted.
    [10:42pm] balunasj: serogers: I can either help with the email or forward an example from the past.
    [10:42pm] balunasj: and I added the link to to provide a template for what the bundle should look like.
    [10:42pm] serogers: balunasj: if you could forward an example to start, that would be appreciated
    [10:42pm] serogers: Yes, thanks
    [10:43pm] serogers: When you say host it somewhere they can access... where do you suggest?
    [10:43pm] balunasj: serogers: sure
    [10:43pm] balunasj: serogers: This is something someone in your group there might know better
    [10:44pm] serogers: balunasj: OK
    [10:44pm] balunasj: serogers: This just need to be on a server, or link somewhere so IT can download it.
    [10:44pm] serogers: OK
    [10:44pm] • balunasj thinking this used to be a lot easier....:-(
    [10:46pm] serogers: OK,  think that covers all the 3.3.3 items then
    [10:47pm] balunasj: serogers: great so with 4.0 I just want to make sure we have the skeletons and content you've already done building in hudson
    [10:47pm] serogers: Yes. What do I need to do to get this going?
    [10:48pm] balunasj: serogers: so that as you make updates we can review and even modify ourselves if needed/wanted/
    [10:48pm] balunasj: serogers: how familiar are you with hudson and how jboss uses it?
    [10:49pm] balunasj: serogers: here is the link to the internal richface view -
    [10:49pm] serogers: not very familiar. I just know it does nightly builds to ensure everything compiles and so on
    [10:49pm] balunasj: needing VPN.
    [10:49pm] balunasj: serogers: np
    [10:49pm] balunasj: serogers: so first thing you'll need is a login so that you can create/modify builds.
    [10:50pm] balunasj: serogers: prabhat is probably the best person to help with that part.
    [10:50pm] serogers: OK
    [10:50pm] balunasj: serogers: The next step out be to review the current builds like "refaces-3.3-docs", and others.
    [10:50pm] balunasj: The interface for setting up a build is actually pretty easy.
    [10:51pm] balunasj: It is a web based form where you tell hudson the instructions for download, and building.
    [10:51pm] balunasj: basically putting in the info from your wiki page on building.
    [10:51pm] balunasj: Once you get the login
    [10:51pm] balunasj: and review some of the build let me know and we can walk through it.
    [10:52pm] serogers: OK, thanks.
    [10:52pm] • balunasj planning a hudson job review as part of new years resolution
    [10:52pm] serogers:
    [10:53pm] serogers: That all sounds good
    [10:53pm] balunasj: As for hosting nightly builds - hudson is probably the best place for now.
    [10:53pm] serogers: I agree
    [10:53pm] balunasj: there has been a lot of discussions internally about where to host them, but IT gives us little option.
    [10:54pm] balunasj: this is an example of the tools nightly doc build in hudson
    [10:55pm] balunasj: We would want something like this for RF 4.0 nightly
    [10:55pm] serogers: OK
    [10:56pm] serogers: The last thing on the agenda is the previous authors. I can't seem to find a list of the contributors for the 3.3.x docs so I can give them credit in the 4.0 docs
    [10:56pm] balunasj: We'll review and discuss 4.0 docs more once these are up, and ALAPHA2 is more concrete in the plans.
    [10:57pm] balunasj: serogers: I can give you list of them if you wish.
    [10:58pm] serogers: balunasj: that would be good
    [10:58pm] balunasj: ok
    [10:59pm] balunasj: I think that covers the agenda - is there anything else we need before we let serogers go to bed
    [11:00pm] serogers: I don't think so, I think we've covered everything
    [11:00pm] balunasj: ok great, and look at that right on time
    [11:01pm] serogers:
    [11:01pm] balunasj: serogers: Please enter the jira's and we'll follow up next week.
    [11:01pm] serogers: OK, will do.