17:01:04 <colindixon> #startmeeting
17:01:04 <odl_meetbot> Meeting started Tue Jan 14 17:01:04 2014 UTC.  The chair is colindixon. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:01:04 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
17:01:12 <colindixon> #topic overview
17:01:34 <colindixon> #info I'm going to try to keep this meeting to the tasks which are due today (or at least started by today) to keep things brief
17:01:51 <colindixon> we're missing cdub, is he around?
17:02:49 <Madhu> colindixon: am here and I added myself as a Team member
17:03:22 <colindixon> #topic Identify all places dependency versions in project pom.xml files are not current for all ODL Dependencies
17:03:32 <colindixon> Madhu: this is done on the spreadsheet
17:03:36 <colindixon> and I've seen the e-mails
17:03:53 <Madhu> yes. i marked it as DONE after agreeing with the team during yest evening meeting
17:04:10 <colindixon> perfect
17:04:16 <Madhu> now its time to wrangle each project owner to get the stuffs done
17:04:19 <colindixon> #agreed this item is done
17:04:22 <edwarnicke> I concur, please note identify is not fix (although its still good :) )
17:04:58 <colindixon> #info note that this is "identify" and not fix
17:05:08 <colindixon> #topic Identify differing versions of dependencies on external artifacts and negotiate a recommended version
17:05:18 <colindixon> what is the status here?
17:05:19 <Madhu> #info the actual work per-project to update starts 1/15
17:05:45 <Madhu> external artifact dependencies are identified... but negotiation has not started yet.
17:05:46 <colindixon> (sorry, trying to run this fast and lean to waste fewer people's time)
17:06:00 <colindixon> #info Madhu: external artifact dependencies are identified... but negotiation has not started yet.
17:06:01 <Madhu> will start today guys. we have to move the deadline at least a couple of days
17:06:08 <colindixon> that makes sense
17:06:19 <colindixon> I don't think that this is designed to be a death march as much as a cadence
17:06:31 <colindixon> has that info been e-mailed out to people yet?
17:06:41 <Madhu> not yet.
17:06:56 <Madhu> Action item on me to take care of that
17:07:16 <Madhu> if we all agree i will move the date to 1/16
17:07:22 <edwarnicke> Madhu: Thats the latest start date... no harm in starting early :)
17:07:52 <edwarnicke> I'm OK with agreeing to moving the start date to 1/16 as long as we hold the line on the end date
17:08:02 <Madhu> edwarnicke: agreed
17:08:07 <colindixon> #action Madhu to e-mail out the list of external dependencies and their versions, and we'll start negotiating by 1/16
17:08:21 <Madhu> these dependency convergence is a mandatory criteria for release artifacts
17:08:22 <colindixon> can somebody change that date on the spreadsheet
17:08:26 <colindixon> ?
17:08:30 <Madhu> colindixon: i will
17:08:40 <colindixon> perfect
17:08:48 <Madhu> How can we communicate the importance of dependency convergence to the project owners ?
17:09:03 <colindixon> #info Madhu has updated the start date for this task "Update dependency version on external artifacts to match across ODL" to 1/16
17:09:04 <Madhu> it basically holds many things. including proper IT.
17:09:32 <colindixon> email the project-dev lists? and follow up with the project lead as expressed in the spreadsheet?
17:10:09 <Madhu> :) sure. but u think that will work ?
17:10:25 <colindixon> if it doesn't we escalate with the TSC, Phil and people
17:10:28 <colindixon> or me
17:10:31 <colindixon> or edwarnicke
17:10:35 <colindixon> we can apply pressure
17:10:41 <Madhu> can't we do it now ?
17:10:48 <Madhu> anyways i will shut up now
17:10:51 <Madhu> move on to next topic
17:11:02 <edwarnicke> Madhu: One other thing to note... the loop really has to get closed... sadly just emaling is only the first step... got to get folks responding and moving
17:11:18 <Madhu> edwarnicke: exactly my point.
17:11:19 <colindixon> #info maybe bring up the things individual projects are expected to do during the TSC meeting?
17:11:25 <edwarnicke> also, Madhu, if you have any trouble getting a project going, I know most of the folks and am willing to do a follow up poke
17:11:58 <Madhu> to me this dependency convergence is extremely important for what is to follow. so special attention is required
17:12:03 <Madhu> am sure edwarnicke u know about that
17:12:07 <colindixon> #agreed we need to have a relatively low tolerance for open loop on these per-project tasks including removing log messages, fixing version dependencies, etc.
17:12:30 <colindixon> #topic user manaual
17:12:37 <colindixon> rob dolin isn't here
17:12:39 <phrobb> We should use these meetings to close the loop.  We have good representation across the projects online here now
17:12:39 <edwarnicke> Madhu: I completely agree :)
17:13:03 <colindixon> #info since the relevant people aren't here, move this topic to this evening
17:13:07 <edwarnicke> Yes, Madhu started doing some of that loop closing on the 5:45pm PST yesterday with the snmp4sdn and vtn folks :)
17:13:08 <phrobb> posting daily attendance of project/lead would be helpful for these meetings also
17:13:18 <edwarnicke> phrobb: great idea :)
17:13:21 <colindixon> #topic general comments about the meeting
17:13:36 <colindixon> #info we should post attendance of project leads
17:13:45 <colindixon> #info this will enable loop closing
17:13:46 <edwarnicke> We could start with a 'roll call' topic and do a quick roll call in about 60 seconds
17:13:53 <Madhu> meetbot does it automatically
17:13:54 <colindixon> quickly, can we do this rollcall?
17:14:13 <colindixon> #topic roll call of project leads
17:14:31 <colindixon> please all project leads, do a pound #info with present and for what project
17:14:51 <Madhu> colindixon: i think the meetbot already does that
17:14:53 <Madhu> attendance
17:15:04 <Madhu> but if you think this is useful
17:15:13 <abhijitkumbhare> #info abhijitkumbhare is present: Openflowplugin
17:15:13 <colindixon> but not if they're paying attention
17:15:35 <Madhu> #info Madhu for OVSDB & Release related global wrangling.
17:15:58 <LuisGomez> #info Luis for Inetgration and global testing
17:16:13 <colindixon> edwarnicke, tony, abhijitkumbhare , michal_rehak , Madhu , ashaikh , suchi, gera, konstantin, rober vaga, dana, david goldberg, christine, LuisGomez
17:16:34 <colindixon> we''ll see what that gets and move on in 30 seconds
17:16:50 <ashaikh> #info Anees for Open DOVE and platform qualification  (Ryan will join also for Open DOVE)
17:17:33 <colindixon> last call
17:17:42 <colindixon> ok
17:17:45 <colindixon> well that's something
17:17:57 <colindixon> #topic developer guide
17:18:12 <colindixon> #info again, chris price and rob dolin aren't present, hopefully we can do this in the evening meeting
17:18:27 <colindixon> #topic Write recommendation for cutting Release Branches and laying Release labels
17:18:44 * regXboi glares at ashaikh for the misrouting
17:18:53 <colindixon> #info wrong topic, ignore this
17:19:00 <colindixon> #topic Document how to cut release artifacts for a project
17:19:06 <colindixon> Madhu: GiovanniMeo how goes this?
17:19:22 <Madhu> it is done
17:19:31 <Madhu> at least roughly and pasted the email as a wiki doc :)
17:19:34 <colindixon> ok
17:19:38 <colindixon> can you give the link
17:19:45 <Madhu> yes. 1 sec
17:19:48 <colindixon> perfect
17:20:03 <colindixon> you can pound link it
17:20:09 <colindixon> and that will make it an actual link in the logs
17:20:12 <Madhu> #info Release recommendation #link https://wiki.opendaylight.org/view/Simultaneous_Release:Simultaneous_Release_Plan_2014:ReleaseRecommendations
17:20:18 <colindixon> perfect
17:20:59 <colindixon> #info colindixon marked this task as done on the spreadsheet
17:21:13 <colindixon> #topic Write recommendation for cutting Release Branches and laying Release labels
17:21:14 <edwarnicke> Madhu: Are these recommendations cutting a branch or simply laying a tag?
17:21:25 <regXboi> Madhu - I saw the email on updating versioning - are you around this evening PT?
17:21:32 <Madhu> edwarnicke: i discussed this with GiovanniMeo
17:21:35 <colindixon> (sorry, I'm changing topics too fast)
17:21:39 <regXboi> I won't be able to get to opendove until then....
17:21:47 <Madhu> he felt it is better to have a tag instead of branch
17:21:59 <colindixon> LuisGomez: we'll pick up with this topic after this conversation calms down
17:22:00 <Madhu> and it is easy to add a post-script to create a branch from the tag
17:22:00 <edwarnicke> Madhu: From a tag you can pull a branch, so I'm good
17:22:05 <Madhu> yep.
17:22:11 <edwarnicke> Just wanted to know
17:22:16 <Madhu> essentially because this is tried and tested many times and hence this decision
17:22:23 <LuisGomez> colindixon: ok
17:22:36 <Madhu> regXboi: yes.
17:22:54 <regXboi> @Madhu: thanks - will look for you on main channel then
17:23:04 <Madhu> regXboi: yes sir.
17:23:11 <colindixon> #info Madhu's instructions specify that you create a tag for release artifacts rather than a branch. edwarnicke is good with this because you can pull a branch from a tag easily.
17:23:35 <Madhu> colindixon: correction.
17:23:48 <Madhu> the tag is automatically labeled by the maven-release-plugin
17:23:50 <colindixon> Madhu: you can correct with pound info yourself i you want
17:24:02 <Madhu> #info maven-release-plugin does the tagging automatically
17:24:07 <colindixon> perfect
17:24:08 <colindixon> thanks!
17:24:16 <dual_regXboi> warning: regXboi now will be building both rhel and windows going forward
17:24:22 <dual_regXboi> (twice the insanity)
17:24:38 <colindixon> so, LuisGomez how goes the recommendations for cutting release branches and laying release labels?
17:25:12 <LuisGomez> i am actually not working on that, is this something for the integration team?
17:25:15 <Madhu> colindixon: i haven't synced up with LuisGomez yet.
17:25:41 <Madhu> this is closely tied up with the tag that is laid by the maven-release-plugin
17:25:54 <Madhu> and is not integration branch specific. but we may have to add more jenkins job
17:26:04 <colindixon> ok
17:26:15 <colindixon> so, is this essentially done by the previous topic?
17:26:18 <LuisGomez> no problem to add more jenkins, i can help on that
17:26:22 <colindixon> or is there more to do?
17:26:30 <colindixon> and if so what timeline is reasonable to get it done by?
17:26:31 <Madhu> #info post-release, we need more integration jenkins job for RELEASE and new SNAPSHOTs
17:26:48 <Madhu> colindixon: this is certainly manageable
17:27:01 <edwarnicke> Could I recommend we add to the developers guide a link to the tagged code for the release artifacts... might be handy for folks
17:27:03 <Madhu> jenkins jobs are easily copy + paste :)
17:27:24 <Madhu> edwarnicke: good idea.
17:27:26 <colindixon> that sounds like a good idea
17:27:39 <colindixon> I'm going to agreed that
17:28:13 <colindixon> #agreed developer guide should include a tag to the tag in the code for the release artifacts, colindixon will put it in the notes for the spreadsheet
17:28:17 <Madhu> btw. I didn't add any recommendation for post-release branch managements.
17:28:28 <Madhu> edwarnicke: this will address the weekly releases and branches
17:28:37 <Madhu> also the semantic versioning question that muthu asked.
17:28:48 <Madhu> shall we have that post release (or close to the release after things calm down ? )
17:28:55 <colindixon> yeah
17:29:00 <colindixon> I think we have enough on our plates
17:29:22 <edwarnicke> Madhu: I agree with postponing those till after the release.  Sufficient unto the day is the troubles thereof :)
17:29:48 <Madhu> #info the release management, versioning and branching recommendations are for Hydrogen release only. Post-Hydrogen release management discussions will be Post-Hydrogen ;)
17:29:54 <colindixon> #info Madhu and LuisGomez will work on providing recommendations for release branches and laying release labels the date will be moved
17:30:08 <colindixon> when do you want to moved the date to?
17:30:11 <colindixon> 1/15?
17:30:12 <colindixon> 1/16?
17:30:18 <Madhu> colindixon: we decided on this
17:30:24 <Madhu> the tag is the label
17:30:27 <colindixon> did I miss it
17:30:28 <colindixon> ok
17:30:38 <Madhu> we can manage branches via tags
17:30:43 <colindixon> ok
17:30:45 <Madhu> and if needed automate it via jenkins
17:30:50 <colindixon> ok
17:30:55 <Madhu> since tags are guaranteed, we are good
17:31:02 <colindixon> have we provided instructions for people?
17:31:07 <Madhu> unless we have a problem with that
17:31:11 <colindixon> that's what we really need
17:31:16 <colindixon> that's the link you sent earlier
17:31:21 <Madhu> yes. tags are auto-generated by maven-release-plugin
17:31:26 <colindixon> and we just need to add jenkins jobs?
17:31:46 <Madhu> edwarnicke: should we add a post-script in jenkins to lay a branch on the tag ?
17:31:50 <Madhu> we can do that if that is needed
17:32:07 <Madhu> i don't want to use the release:branch option of maven-release-plugin (because of the unknown)
17:32:08 <colindixon> Madhu ok, can you pound info a useful summary of what we've agreed on and what the next step is and I'll move on to the last topic for today
17:32:10 <edwarnicke> Madhu: I think the tag is enough for the moment
17:32:17 <Madhu> edwarnicke: agreed.
17:32:25 <Madhu> colindixon: doing that now
17:32:30 <edwarnicke> You can always cut a branch from a tag
17:32:56 <colindixon> (really wants to be done in 2 minutes)
17:32:58 <Madhu> #info we will use the default behavior of maven-release-plugin to lay the release tag automatically. the branching from that can be managed manually.
17:33:04 <colindixon> perfect
17:33:12 <colindixon> #topic Write Release Review Template
17:33:26 <colindixon> #info this is done and posted here #link https://wiki.opendaylight.org/view/Sample_Release_Review
17:34:07 <colindixon> It is intentionally a verbatim copy of the sections required of the document in the Project Lifecylce page here:
17:34:08 <colindixon> #link http://www.opendaylight.org/project-lifecycle-releases#MatureReleaseProcess Unless others feel differently, my logic was that the TSC would want to (and may be limited by it's charter to) impose the minimum requirements as to not hold up any of the releases.
17:34:46 <edwarnicke> colindixon: We checked with hideyuki from vtn and Christine_ from snmp4sdn last night and they are fine with the template
17:35:16 <colindixon> good
17:35:28 <colindixon> #agreed this is done and marked as such on the spreadsheet
17:35:36 <colindixon> #topic log level recommendations
17:35:43 <colindixon> #help we need somebody to volunteer for this
17:35:59 <colindixon> any volunteers?
17:36:08 <colindixon> (if not I'm going to call for last topics and close the meeting)
17:36:49 <colindixon> volunteers? last topics?
17:36:55 <colindixon> going once
17:36:56 <dual_regXboi> what log level are you talking about, syslog?
17:37:03 <edwarnicke> dual_regXboi: Yes, syslog
17:37:16 <dual_regXboi> I'll bend some time to it
17:37:21 <edwarnicke> I was thinking things like: logs on entry and exit to a block should be at level debug or trace, etc
17:37:32 <dual_regXboi> I'll bend some thought time on it
17:37:37 <dual_regXboi> when is it due by?
17:37:38 <colindixon> #agreed dual_regXboi will pick this up and write up a short guide on how to pick proper log levels
17:37:40 <edwarnicke> dual_regXboi: Thanks
17:37:44 <colindixon> today officially
17:37:48 <dual_regXboi> uh
17:37:49 <colindixon> we can move it to 1/16 if that helps?
17:37:53 <dual_regXboi> massively
17:37:54 <colindixon> when can you do it?
17:38:09 <dual_regXboi> I can find some time tonight to think about it while updating version numbers
17:38:16 <colindixon> is 1/15 possible
17:38:21 <colindixon> or is 1/16 the right thing
17:38:26 <Madhu> dual_regXboi: can u please look @ the openflowplugin to begin with :)
17:38:32 <dual_regXboi> link?
17:38:36 <Madhu> the logs are massive and it screams help.
17:38:46 <Madhu> edwarnicke: u might know something behind why it is so.
17:38:47 <dual_regXboi> it's worse than yang?
17:38:51 <edwarnicke> Madhu: I am aware the logs are massive, it was actually the inspiration for that item
17:38:54 <Madhu> dual_regXboi: pls take a look
17:39:03 <Madhu> u will be surprised and shocked
17:39:04 * dual_regXboi marvels that something is noiser than yang
17:39:11 <edwarnicke> But I think that simple guidelines on when to use what log level will help
17:39:26 <edwarnicke> It gives us something to drive folks towards
17:39:27 <colindixon> #agreed we'll move the log level recommendations deadline to 1/16 and if dual_regXboi can get it done early great
17:39:28 <dual_regXboi> openflowplugin is in controller or own project?
17:39:36 <edwarnicke> openflowplugin is a project :)
17:39:39 <Madhu> its own project.
17:39:47 <dual_regXboi> ok... will pull it tonight and look while playing with OpenDove
17:40:00 <Madhu> dual_regXboi: u have to use OF13 to see the real deal :)
17:40:08 <Madhu> dual_regXboi: i can help u with that if u need
17:40:15 <colindixon> #info lots of comments for where dual_regXboi shoudl start looking (see the full log)
17:40:20 <edwarnicke> I think though, this can be really simple
17:40:20 <colindixon> #endmeeting