[10:01pm] balunasj: so I've got 3 things to talk about
[10:02pm] balunasj: 1) post-mortem follow up, and input
[10:02pm] balunasj: 2) Release plan comments
[10:02pm] balunasj: 2.1) Updated doc plan for it
[10:02pm] balunasj: 3) Moving meeting to Thursday?
[10:02pm] balunasj: -
[10:02pm] balunasj: Three might be the easiest
[10:03pm] serogers: OK
[10:03pm] balunasj: how does moving the meetings to thursday sound
[10:03pm] serogers: Same time as now, but on Thursday?
[10:03pm] balunasj: I wanted to consolidate my meetings into 2 days - tuesdays, and thursdays
[10:03pm] serogers: That should be OK
[10:03pm] balunasj: or shifted a little if that works better for you
[10:04pm] serogers: This time is OK for me
[10:04pm] balunasj: ok good
[10:05pm] balunasj: so lets move on to 1)
[10:05pm] balunasj: I am only about half way through the write up for the post-mortem
[10:05pm] balunasj: The big items that were good
[10:05pm] balunasj: :
[10:05pm] balunasj: build updates
[10:05pm] balunasj: jira process
[10:05pm] balunasj: mock release
[10:06pm] balunasj: specfic to you was moving the docs out of trunk gave you flexibility, and sped up the project build.
[10:06pm] balunasj: The bad
[10:06pm] pyaschenko joined the chat room.
[10:07pm] balunasj: Build updates took longer than we thought - and pushed the schedule out a week
[10:07pm] pyaschenko1 left the chat room. (Ping timeout: 258 seconds)
[10:07pm] balunasj: dev branch with svnmerge and jboss svn too slow for minsk team
[10:07pm] balunasj: Initial quality of components was low - more dev testing needed.
[10:08pm] balunasj: Changes for M3
[10:08pm] balunasj: Dev branch usage - documented, with workflow, and testing from minsk
[10:08pm] balunasj: Keeping jira up to date from everyone
[10:09pm] balunasj: Still having a mock release, and going to a release model with component code freeze
[10:09pm] balunasj: and specific time for bug fixes prior to code freeze
[10:09pm] balunasj: Those are the main points.
[10:09pm] serogers: OK
[10:09pm] balunasj: I would like to get your thoughts on those questions, and make sure you have what you need
[10:11pm] serogers: The approach we took worked OK for me. I'll work on using svnmerge properly and being able to tag and release myself.
[10:11pm] serogers: The reviewing worked fairly well too
[10:12pm] balunasj: serogers: I'm hoping that the time between component code freeze, and tagging can be used for review as well.
[10:13pm] serogers: Yes
[10:13pm] serogers: Ideally that's how it would work next time
[10:15pm] balunasj: other positive items? How did you feel about the build changes?
[10:16pm] serogers: Build changes worked well for me.
[10:17pm] balunasj: ok how about issues, or things that slowed you down? Do you feel you received the information on new components when you should and had enough to use?
[10:18pm] balunasj: The release stuff for the first time slowed us down a little
[10:18pm] serogers: Yeah the information on the new components was a bit hard for me to know where to look. Once Ilya pointed me to the wiki pages the information was OK, but was still a bit out of date in some aspects
[10:19pm] serogers: It would be good if when the Jiras for documentation are created, there were links to the design in the wiki
[10:19pm] balunasj: serogers: yes, that is a good point
[10:19pm] balunasj: there were other comments on jira/wiki updates, and linking
[10:20pm] balunasj: specifically that wiki should like to the jira, and jira should link to wiki. When features are shifted out of a component the wiki needs to be updated, etc....
[10:20pm] serogers: Especially when components names were changed it was confusing as well, since they weren't always referred to consistently
[10:21pm] balunasj: serogers: yes, I ran into that as well.
[10:21pm] balunasj: anything else?
[10:22pm] serogers: They were my main concerns
[10:23pm] balunasj: ok, and do you have any suggestions for changes in M3 and beyond?
[10:24pm] serogers: Not apart from those comments
[10:24pm] balunasj: ok
[10:25pm] balunasj: so if there is nothing else with post-mortem lets move on to release plan
[10:25pm] serogers: OK
[10:26pm] balunasj: You saw the email on it, I'm going to be updating wiki, and writing a blog
[10:28pm] balunasj: I'd like it if you could update the doc plan
[10:28pm] balunasj: based on the new timeline
[10:28pm] balunasj: and update the wiki pages with it if you could
[10:28pm] serogers: OK, will do
[10:28pm] balunasj: I'm hoping by the time you start in your morning, I'll have the wiki updated
[10:28pm] balunasj: and perhaps the blog
[10:28pm] serogers: Cool
[10:28pm] balunasj: then you'll know where to go from
[10:29pm] balunasj: That should cover M3, all the way to final
[10:30pm] balunasj: Thats all I had for the meeting today
[10:31pm] balunasj: Anything else from your end?
[10:31pm] serogers: OK. I don't think there is anything else I want to cover that we haven't already touched on.
[10:31pm] serogers: Were you happy with how the docs are going?
[10:31pm] balunasj: ok great!
[10:31pm] balunasj: yes, I like the docs, and the updates.
[10:32pm] balunasj: We'll need to start focus on migration documents, and plans soon, so streamlining the component doc parts will be critical.
[10:32pm] serogers: Great
[10:32pm] balunasj: I also need to do a full review of the dev guide, but likely won't get to that before JavaOne
[10:32pm] serogers: Sure
[10:33pm] balunasj: ok, so have a good night, and we'll catch up more later