Version 1
    [10:05pm] balunasj: btw - additional topic to discuss - nightly doc builds
    [10:05pm] serogers: OK
    [10:05pm] balunasj: so where would you like to begin?
    [10:06pm] serogers: We can start with the nightly builds if you like
    [10:06pm] balunasj: sure
    [10:07pm] balunasj: so now that we have access to updating and uploading our own docs it should open up the ability to have
    [10:07pm] balunasj: nightly doc builds uploaded from hudson.
    [10:07pm] serogers: OK
    [10:07pm] balunasj: however there will be a few hurdles - but we will not be the only team doing this.
    [10:07pm] balunasj: I suggest a couple things
    [10:08pm] balunasj: create an RFPL jira to track our part of it
    [10:08pm] balunasj: Write an email to mark newton about how the new changes might allow us to upload nightly builds
    [10:09pm] balunasj: work with QE guys on updates or testing changes
    [10:09pm] balunasj: in hudson
    [10:09pm] balunasj: We'll also need to discuss structure and location for the nightly builds.
    [10:09pm] balunasj: also - once the "books" are uploaded we'll want to work on getting the generated docs up there as well.
    [10:10pm] balunasj: </end>
    [10:10pm] serogers: OK
    [10:11pm] serogers: I don't think there will be any major problems
    [10:11pm] serogers: Do other projects do similar uploading?
    [10:11pm] balunasj: My only thought is that IT might not like the auto update of the doc area.
    [10:12pm] balunasj: serogers: that is just it - since the new access process/servers likely many projects are changing or working with the new system
    [10:12pm] balunasj: so there will be some investigation, and communication needed.
    [10:12pm] serogers: I see
    [10:13pm] balunasj: I suggest an email to the core mailing list
    [10:13pm] balunasj: & cc'ing mark newton
    [10:13pm] serogers: Yeah
    [10:13pm] balunasj: Then you will find out who is doing what.
    [10:13pm] balunasj: serogers: is that something you are comfortable with?
    [10:14pm] serogers: Yeah, I think so. If I have any trouble I will let you know
    [10:14pm] balunasj: serogers: perfect
    [10:14pm] balunasj: I think the first goal will be to get 4.0.x "books" uploaded
    [10:14pm] balunasj: once that is in place we'll look at getting the tld, javadoc, etc... upthere
    [10:15pm] serogers: Yep
    [10:15pm] balunasj: ok we should also discuss the structure for this as well.
    [10:15pm] balunasj: although that might change if other project do it differently and we like it.
    [10:15pm] serogers: No problem
    [10:16pm] balunasj: So right now
    [10:16pm] balunasj: has latest_3_3_x and then other release builds
    [10:17pm] balunasj: This is how seam handles it
    [10:17pm] balunasj: as an example
    [10:17pm] balunasj: they have /snapshot
    [10:17pm] balunasj: but I think we need some more structure under that
    [10:18pm] balunasj: all: do you guys prefer "nightly" or "snapshot"?
    [10:18pm] balunasj: snapshot might be more accurate because the builds could trigger at any time
    [10:19pm] nbelaevski: right, even more I like "unstable"
    [10:20pm] balunasj: hmm - do you think snapshot is more recognizable?  I think most developers will know they mean the same thing
    [10:21pm] serogers: I think "unstable" sounds too negative, I like "nightly" as it is a very common name for these type of builds, even if it technically isn't done at night
    [10:21pm] serogers: But snapshot is OK too
    [10:21pm] balunasj: ilya_shaikovsky: any thought on this?
    [10:22pm] ilya_shaikovsky: not much differs for me
    [10:22pm] ilya_shaikovsky: snapshot seems more accurate
    [10:22pm] ilya_shaikovsky: as we name our builds in this way
    [10:22pm] serogers: that's true
    [10:22pm] balunasj: ok lets go with "snapshot"
    [10:22pm] serogers: OK
    [10:22pm] nbelaevski: ok
    [10:23pm] balunasj: Even though I don't think we will have snapshot builds for 3.3.X
    [10:23pm] balunasj: we should add version qualifier to the snapshot
    [10:23pm] balunasj: like latest
    [10:23pm] balunasj: snapshot_4_0_X
    [10:24pm] balunasj: that way when 4.1.X comes around we won't have to adjust the links everywhere
    [10:24pm] balunasj: so under snapshot_4_0_X we need a place for the docs serogers is writing and for the generated docs
    [10:25pm] balunasj: this should mirror what we want to do for the actual release bundles
    [10:25pm] balunasj: we don't need to figure that part out right now, but something to thing about
    [10:26pm] balunasj: one thought is:
    [10:26pm] balunasj: are we ever going to "localize" generated docs?
    [10:27pm] balunasj: and do we want to have the "books" separated from the generated docs?
    [10:27pm] serogers: I'm not sure how we could
    [10:28pm] serogers: But we can probably look at that later
    [10:29pm] balunasj: yup
    [10:29pm] balunasj: so please create the jira, and start in on it.  I'll keep an eye out for it and support as needed.
    [10:29pm] serogers: OK, will do
    [10:29pm] balunasj: want to talk about 3.3.3.F next
    [10:30pm] serogers: OK
    [10:30pm] balunasj: right now there are two bugs for you
    [10:30pm] balunasj: RFPL-429
    [10:30pm] balunasj: RF-8494
    [10:30pm] jbossbot: [RFPL-429] Update documenation to show 3.3.3.Final instead of 3.3.3.GA [Open, Blocker, Sean Rogers]
    [10:30pm] jbossbot: [RF-8494] Describe limitations of table variables usage with sorting/filtering [Open, Major, Sean Rogers]
    [10:30pm] balunasj: and we are planning a code freeze and build to QE next Tuesday
    [10:31pm] balunasj: serogers: btw - like the new JBossBot for jira
    [10:31pm] serogers: OK. I should hopefully be able to knock those over tomorrow
    [10:31pm] balunasj: serogers: ok great
    [10:32pm] balunasj: and I'll create the release jira to track final step tasks like uploading
    [10:32pm] balunasj: serogers: related to the new upload process
    [10:33pm] serogers: I'm actually getting my wisdom teeth out on Friday, so won't be in to work again until Thursday next week after that. But I don't foresee any issues with those jiras
    [10:33pm] balunasj: serogers: OUCH
    [10:33pm] serogers: Yah
    [10:33pm] balunasj: serogers: thankfully I have a big mouth so I don't need to have mine out
    [10:33pm] balunasj:
    [10:33pm] ilya_shaikovsky:
    [10:34pm] serogers: I've been busy with some other issues but finished them today, so I have all day tomorrow to get those Jiras done
    [10:34pm] serogers:
    [10:34pm] balunasj: ok good that should be fine
    [10:34pm] balunasj: We can wait for later next week for the doc bundle to review, and upload
    [10:34pm] balunasj: the release would not be until the following week
    [10:34pm] serogers: OK
    [10:35pm] balunasj: but it would be good if you could knock off those jira so you can just come back and generate the bundle
    [10:35pm] serogers: Yep
    [10:35pm] balunasj: so that should work
    [10:36pm] balunasj: Just so we are all on the same page
    [10:36pm] balunasj: it should be "3.3.3.Final"
    [10:37pm] balunasj: both for the tag, labels, etc...
    [10:37pm] serogers: OK, no problem.
    [10:37pm] balunasj: serogers: as for the tech reviews for 4.0 I have had a chance.
    [10:38pm] balunasj: I will make it a point to review and delegate other reviews
    [10:38pm] balunasj: next week
    [10:38pm] balunasj: It might not be all done next week, but we'll get the task started
    [10:38pm] serogers: Cool. I'd like to start getting other sections reviewed but don't want to overwhlem you all with reviews
    [10:39pm] balunasj: serogers: thanks - I think everyone is busy, but we need to make time for the reviews - it is important.
    [10:39pm] serogers: Cool. In a couple of weeks I will put together another section for review then.
    [10:40pm] balunasj: serogers: another topic - any questions or comments related to the hudson reorg, or builds
    [10:41pm] serogers: It looks good, easier to navigate now.
    [10:41pm] balunasj: ok cool - if you have suggestions or need changes let me know
    [10:42pm] serogers: I was having some trouble where I wold get failures because it ran out of memory, but I've changed the configuration to not build on a particular system and it seems to be going OK now.
    [10:42pm] balunasj: btw - I recommend "hudson" iphone app.  It only works with the public server, but it nice for checking status on the run
    [10:42pm] serogers: OK, shall check it out
    [10:43pm] balunasj: serogers: the QE hudson guys were just telling me about
    [10:43pm] balunasj: some memory leak issues
    [10:43pm] balunasj: perhaps it is related
    [10:44pm] serogers: Maybe. Now I think about it I only changed the 3.3 builds and not the 4.0 builds, but haven't had any problems from either, so it may be OK
    [10:44pm] balunasj: ok good
    [10:44pm] balunasj: that is all I had - is there anything else anyone wants to talk about?
    [10:44pm] serogers: No, I think that is it.
    [10:45pm] serogers: So just keep in mind I'll be offline until the 24th
    [10:45pm] serogers: But I have one more day to get those Jiras done
    [10:45pm] balunasj: ok - I'll put it in the RF vacations calendar
    [10:45pm] balunasj: it is friday -->24th ?
    [10:45pm] serogers: Yes
    [10:45pm] ilya_shaikovsky: and that should be enough time for reviews
    [10:46pm] serogers:
    [10:46pm] balunasj: hehe
    [10:46pm] serogers: OK great
    [10:46pm] serogers: Thanks everyone
    [10:46pm] balunasj: serogers: back on the 24th
    [10:46pm] balunasj: or 25th?
    [10:46pm] serogers: Back on the 25th... but 24th your time
    [10:46pm] balunasj:  good point
    [10:47pm] balunasj: ok talk to you later
    [10:47pm] serogers: OK, bye