Version 1

    [10:05pm] serogers: Yep, I saw the comments

    [10:06pm] balunasj: serogers: I also wanted a general status, and make sure you were comfortable with the M2 jira's
    [10:06pm] balunasj: but lets start with ilya_shaikovsky comments
    [10:07pm] serogers: Yes
    [10:07pm] balunasj: thoughts?
    [10:07pm] serogers: I agree with the comments
    [10:07pm] serogers: I have marked a lot of the migrated sections that need review with a note
    [10:08pm] serogers: Before M2 I'll go through and comment out any components not included
    [10:08pm] serogers: similar to how it was done for M1
    [10:09pm] balunasj: serogers: ok good.  I suggest using development branches for work that is not "ready" yet
    [10:09pm] serogers: OK, not the trunk?
    [10:09pm] balunasj: so you can have a working branch in svn, than can then be migrated as things mature.
    [10:10pm] balunasj: Perhaps in trunk you start with lots of TBD ( which are already there ).
    [10:10pm] balunasj: Then as sections are completed, and components are added you mere to /trunk.
    [10:10pm] balunasj: This is similar to what we are discussing on the dev side as well.
    [10:10pm] serogers: OK
    [10:11pm] balunasj: The use of developer branches and ensuring the trunk is "clean" and mostly current, and stable.
    [10:13pm] serogers: OK, so I work in an existing branch? Or have one just for docs work?
    [10:13pm] balunasj: I'm asking Alex S to make a "RichFaces Development Branch Guide" with resources and links.
    [10:14pm] balunasj: But the idea would be you would have your own branch ( broken out by units of work that you determine ).
    [10:14pm] balunasj: You work in it, and then when you are ready to merge you do that and the branch goes away.
    [10:15pm] balunasj: you create a new branch for the next task.
    [10:15pm] balunasj: Minor updates and fixes can be made in trunk
    [10:15pm] balunasj: this is mainly to make sure trunk is as stable as possible.
    [10:15pm] serogers: OK
    [10:16pm] balunasj: ilya_shaikovsky: does that sound like a good way to keep trunk docs clean?
    [10:17pm] ilya_shaikovsky: that sounds good yes
    [10:18pm] ilya_shaikovsky: with that remark "[15:15:12] balunasj: Minor updates and fixes can be made in trunk" for quick issues fixes
    [10:19pm] balunasj: ilya_shaikovsky: ?
    [10:19pm] ilya_shaikovsky: I'm saying that this way is pretty good. Branch for new sections/chapters and using just trunk for fixes
    [10:20pm] balunasj: ilya_shaikovsky: yes, but large bugs ( mainly in components, core, etc... ) should have their own branch too.
    [10:21pm] balunasj: ilya_shaikovsky: but no one should have to make a new branch for the simple things - overhead not worth it.
    [10:21pm] ilya_shaikovsky: yes agree
    [10:22pm] wesleyhales joined the chat room.
    [10:22pm] balunasj: serogers: we are going to making a "hopefully" final update to the build system ( bottom of )
    [10:23pm] balunasj: serogers: with that will be instructions and info on the branch stuff as well.
    [10:23pm] balunasj: serogers: anything else from ilya_shaikovsky's post you would like to discuss?
    [10:23pm] serogers: No, I think that covers it
    [10:25pm] balunasj: serogers: ok so just a general status on M2 and docs?  And a quick review/questions about jira?
    [10:26pm] serogers: Status is good and Jiras seem fine, I think there shouldn't be any problems
    [10:26pm] • balunasj looking quick one min
    [10:27pm] balunasj: serogers: how do you feel about moving CDK doc back into /docs ?
    [10:27pm] serogers: I would be fine with that, though weren't they moved for a reason?
    [10:27pm] balunasj: It will have docs-parent as its parent and that causes some ordering issues.
    [10:28pm] balunasj: serogers: originally it was moved because CDK had it's own trunk/branch/tags stucture, and in the future may have separate releases.
    [10:28pm] balunasj: This is not even a possiblity until after 4.0.0.Final
    [10:29pm] balunasj: and not likely until a few point releases really stabilies the CDK.
    [10:29pm] balunasj: That is part of the reason for the build struture updates in the forum as well
    [10:29pm] serogers: Hmm, well I guess it's your call. I'm fine to move it back with the other docs though
    [10:30pm] balunasj: serogers: I thought you might
    [10:30pm] serogers:
    [10:30pm] balunasj: serogers: one spot for your stuff, and since doc dependencies do not effect runtime at all there is no need for it to inherit or effect richfaces-parent or bom.
    [10:31pm] serogers: OK
    [10:31pm] balunasj: we can talk about that more later.
    [10:31pm] balunasj: but the other issues and component topics seem good?
    [10:31pm] serogers: Yes
    [10:32pm] balunasj: serogers: ok, and you will create some jira's based on the comments from Ilya to track the tasks?
    [10:32pm] serogers: OK
    [10:32pm] balunasj: serogers: excellent!
    [10:33pm] balunasj: thats all I wanted to cover for now
    [10:33pm] serogers: OK, there is nothing else I need to discuss
    [10:34pm] balunasj: ilya_shaikovsky: anything else you would like to bring up for now?
    [10:35pm] ilya_shaikovsky: Seems no for now
    [10:35pm] balunasj: ok then serogers thanks, and we'll talk later.  Let me know is anything comes up
    [10:35pm] serogers: OK, will do. Bye!
    [10:36pm] balunasj: later