14:32:28 #startmeeting Helium Daily Bug Scrub & Release sync 14:32:28 Meeting started Thu Sep 11 14:32:28 2014 UTC. The chair is gzhao. Information about MeetBot at http://ci.openstack.org/meetbot.html. 14:32:28 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:32:28 The meeting name has been set to 'helium_daily_bug_scrub___release_sync' 14:32:29 Is there a bug-scrub meeting? 14:32:30 ah 14:32:34 thx gzhao ! 14:32:34 unfortunately yes.. i ll need both 14:32:35 :) 14:32:48 chair tbachman edwarnicke 14:32:56 PriyankaChopra: I’d recommend just resubmitting the one that failed 14:32:57 #chair tbachman edwarnicke 14:32:57 Current chairs: edwarnicke gzhao tbachman 14:33:13 #info goldavberg for lispflowmapping 14:33:19 okay.. 14:33:20 #topic roll call 14:33:25 #topic Roll Call 14:33:26 #info tbachman for groupbasedpolicy 14:33:35 gzhao: you liked caps better ;) 14:33:50 #info gzhao for release 14:33:51 #info Hideyuki Tai for VTN project 14:34:00 #info PriyankaChopra for plugin2oc 14:34:01 tbachman: do you want to drive 14:34:10 * tbachman looks around 14:34:11 lol 14:34:12 sure? 14:34:35 #info oflibMichal for openflowjava 14:34:43 we’ll wait until :40 for folks to find their way in 14:35:06 #info edwarnicke 14:35:26 Phil is going to be late due to dentist appt. 14:35:32 gzhao: tbachman Thanks for picking up running the meeting :) 14:35:40 edwarnicke: np! 14:35:53 #info regXboi for an extra ear 14:36:14 * regXboi notes I have one more than yesterday, so I can lend it more easily 14:36:18 regXboi: the dr. gave you an extra ear? 14:36:23 edwarnicke: sure 14:36:32 tbachman: not exactly, he fixed the one that wasn't working well 14:36:43 #info CASP3R Integration (Till Luis rocks up) 14:37:17 #info michal_rehak (openflowplugin) 14:37:44 #info Vijay for SNBI 14:38:56 #info ttkacik for yangtools and mdsal 14:40:41 so, I have the following projects missing: 14:41:05 aaa, bgppcep, controller, dlux, pcmm, tcpmd5, ovsdb, sdni, sfc, and snmp4sdn 14:41:54 #info missing aaa, bgppcep, controller, dlux, pcmm, tcpmd5, ovsdb, sdni, sfc, and snmp4sdn 14:42:07 #topic bugs 14:42:18 should we go project-by-project? 14:42:22 (for those here) 14:42:38 tbachman: I would like Ed first talk about where we are for RC0 14:42:44 sure 14:42:49 #topic rc0 status 14:43:03 tbachman: then go for status and give people sometime as well to join 14:43:21 OK 14:43:28 edwarnicke: so Ed, do you want to talk about autorelease RC0 14:43:29 * tbachman gives edwarnicke the stage 14:43:47 So... RC0 went out on time on Tue Sept 9 (one moment while I marshal links ;) ) 14:45:03 gzhao: Could you dig up the link to your announcement 14:45:19 #link http://nexus.opendaylight.org/content/groups/staging/org/opendaylight/integration/distribution-karaf/0.2.0-Helium-RC0/ <- link to RC0 14:45:44 #info autorelease build running every four hours to test it keeps working 14:46:27 edwarnicke: this one? https://lists.opendaylight.org/pipermail/release/2014-September/000352.html 14:46:31 #info nightly builds should be coming in format RC0- (or if its easily doable, RC0-1-, RC0-2- etc) 14:46:48 #link https://lists.opendaylight.org/pipermail/release/2014-September/000352.html <- RC0 announcement 14:47:21 Please please please test RC0 for your features ASAP 14:47:46 #link https://wiki.opendaylight.org/view/Karaf:Step_by_Step_Guide#How_to_Test_RC0 <- instructions on how to test 14:48:53 edwarnicke: question: do you want people to test RC0 on build #70? 14:49:21 gzhao: You mean the RC0-1 nightly ? 14:49:29 edwarnicke: yes RC0-1 14:49:37 didn’t colindixon send an email on this? 14:49:50 Probably also a good idea, but it go pushed to the wrong repo, hoping to correct that for tonights nightly 14:50:05 tbachman: You make this completely unfounded presumption that I read email ;) 14:50:09 edwarnicke: ok 14:50:16 no — just wanted to find the link :) 14:50:32 tbachman: If you can find the link, please #link it in 14:50:34 #info colindixon for TTP 14:50:39 I *think* thats all from me on RC0 14:50:43 edwarnicke: what link do we want? 14:50:45 speak of the devil ;) 14:50:52 braiiinnnn 14:50:54 edwarnicke: looking :) 14:50:54 tbachman: Which link are you looking for? 14:51:06 colindixon’s email asking folks to test 14:51:06 was up until midnight testing TTP in RC0 14:51:09 have bugs 14:51:17 * tbachman thinks it was colindixon, but maybe it was gzhao ? 14:51:17 tbachman: I think it was gzhao’s e-mail 14:51:22 ah, sorry 14:51:35 https://wiki.opendaylight.org/view/Karaf:Step_by_Step_Guide#How_to_Test_RC0 14:51:39 is that what you wanted 14:52:06 colindixon: I think tbachman was looking for your email 14:52:53 #topic status 14:53:02 #link https://lists.opendaylight.org/pipermail/release/2014-September/000375.html 14:53:22 yeah 14:53:28 there is a template for RC1 we will use for status 14:53:28 I think taht’s what tbachman is looking for 14:53:41 :) 14:53:45 gzhao: What is our status on folks getting into karaf and autorelease? 14:53:54 * tbachman was #fail-ing on email search 14:53:57 thx gzhao ! 14:54:45 were we going to have folks send these to one of the MLs? 14:54:46 Oh, two other things on autorelease... currently failing on a minor bug already being worked to be fixed. And I am going to take the every four hours builds off line for a bit today so I can rework the whole thing to not require human intervention 14:54:49 edwarnicke we have a patch from plugin2oc but it has failed the verification test . 14:54:59 CASP3R: Thank you for letting us know 14:55:06 Do we have plugin2oc guys here? 14:55:08 Karaf only Defense4All not started, sdni and oc are getting close to merge to integration 14:55:11 we *need* to talk about this https://lists.opendaylight.org/pipermail/release/2014-September/000357.html 14:55:23 edwarnicke: PriyankaChopra is here 14:55:27 for plugin2oc 14:55:53 so, maybe one thing at a time 14:56:01 tbachman: sure 14:56:01 we probably should discuss the email gzhao sent out 14:56:07 edwarnicke: PriyankaChopra is here for plugi oc 14:56:08 and agree on that 14:56:37 PriyankaChopra: Is there anything blocking you on your verification tests? 14:56:38 My understanding from the last meeting was that we were going to send this status to the ML 14:56:40 is that correct? 14:56:54 tbachman: yes 14:57:01 Great :) 14:57:03 just like the other milestones 14:57:06 Did we say *which* ML? 14:57:11 D4A are planning this activity, hope to start soon 14:57:12 edwarnicke the build passed 14:57:14 discuss? 14:57:17 controller-dev? 14:57:22 colindixon: tbachman: we are sending status to the ML everyday? 14:57:24 * tbachman can’t remember 14:57:25 tbachman: release, just like everythign else 14:57:28 ah 14:57:29 k 14:57:34 hideyuki: I don’t think so 14:57:35 let me check 14:57:39 https://git.opendaylight.org/gerrit/#/c/11053/ 14:57:49 https://git.opendaylight.org/gerrit/#/c/11036/ 14:57:51 ugh 14:57:59 it seems to imply that we are 14:58:00 The email says this: Please use the following templates when briefing your project' status for this release daily meeting 14:58:07 I was thinking that we’d send an e-mail update once per RC 14:58:09 https://git.opendaylight.org/gerrit/#/c/11036/1 14:58:14 PriyankaChopra: You have no features test at all: https://jenkins.opendaylight.org/plugin2oc/job/plugin2oc-merge/org.opendaylight.plugin2oc$features-plugin2oc/9/testReport/ 14:58:24 colindixon: it makes sense to me. 14:58:47 edwarnicke: that’s probably my fault — I asked them to add that, but didn’t actually look in their link 14:59:13 tbachman: No worrie 14:59:34 so, we need to agree on whether we’re doing daily status to the release ML 14:59:41 does that seem too burdensome? 14:59:47 I think we want a good focus here 15:00:01 It should be a mostly cut-and-paste job 15:00:07 with a daily calendar reminder ;) 15:00:08 colindixon: tbachman hideyuki : For project status, my thoughts are: since we have this meeting, project will go and update their progress daily, one email at end of RC0 will need be send out to ML 15:00:33 gzhao: Just send us a template :) 15:00:36 gzhao: OK 15:00:36 gzhao: when you say update their progress daily — is that on the ML? 15:00:40 Or wiki page? 15:00:49 gzhao: But could we *not* do daily status reports... 15:00:50 if it’s a daily readout, it should be just a few lines in IRC 15:00:58 at most 15:01:04 * edwarnicke hates status reports :( Never formats his TPS reports correctly 15:01:09 colindixon: I like that :) 15:01:09 That’s probalby better 15:01:12 b/c we’re logging this 15:01:23 edwarnicke: no daily email, just use this meeting 15:01:24 edwarnicke: +1 15:01:26 maybe ML for the initial RC 15:01:27 edwarnicke: But always stapled :) 15:01:30 don't forget the cover sheets on the TPS reports :P 15:01:40 I think daily stuff is best handled informally, we’re looking for major bugs and thing sthat need attention *now* 15:01:52 #info projects will report daily bug status on IRC, which is captured by meetbot 15:02:06 #info peasants rejoice 15:02:17 okay — so, for RC — will we do those to ML? 15:02:24 tbachman: I think yes? 15:02:25 just to verify that they’ve tested it? 15:02:31 tbachman: yes 15:02:33 that seems reasonable :) 15:02:43 * tbachman pats self on back 15:02:50 lol 15:02:53 once 15:02:57 twice 15:03:03 15:03:03 shall we go status for each project? 15:03:08 gzhao: sure 15:03:10 topic each one? 15:03:12 gzhao: colindixon tbachman Might it make sense to keep a spreadsheet with a row for each project and column for each nightly for folks to indicate they have tested that nightly, whether the tests were good, and any bugs if not? 15:03:41 edwarnicke: I will do it 15:03:53 I think the idea is this: (1) very short updates via IRC in the daily meetings (2) longer updates like the M# status updates weekly before each RC 15:03:55 edwarnicke: gzhao is the expectation a test of nightlies? 15:04:13 I mean 15:04:19 are we requiring that of projects? 15:04:28 tbachman: require is to strong a word 15:04:32 b/c they may decide that resources are best spent focusing on critical bugs 15:04:32 k 15:04:36 request ;) 15:04:38 tbachman: That is a good point 15:04:44 we can put the spreadsheet there 15:04:47 and folks can update it 15:04:48 tbachman: And maybe it was a bad idea ;) 15:04:57 https://docs.google.com/spreadsheets/d/1TRYposNDFPaKcySlvwkOXvfR6Anx2EFujlIjoTthhRY/edit#gid=829479065 15:04:59 * edwarnicke tends to run about 50% yield on ideas ;) 15:05:09 colindixon: +1 15:05:14 but I’m not convinced we want to make that a daily expectation 15:05:29 okay… 25 mins left 15:05:33 tbachman: Maybe a 'list RC/nightly checked' column in gzhao's spreadsheet? 15:05:34 lets move on to individual projects 15:05:40 sure :) 15:05:44 So its less of a 'requirement' and more of a 'could you tell us the last one you tested' ? 15:05:45 but that’s just a check 15:05:54 tbachman: Sure :) 15:05:55 to say that it’s tested and was good 15:05:59 but if it’s not good 15:06:07 need more than just a check ;) 15:06:18 (not tested, tested and bad, tested and good) 15:06:39 with less than 25 mins left, maybe we should move on? 15:06:56 there are like 12 projects to give status 15:07:01 let's go to status for each project, I want to have 5 or minutes to discuss the meeting time as well, since there are project contacts that have difficulties to attend at this time 15:07:06 tbachman: So maybe RED (not tested) YELLOW (tested and bad) GREEN (tested and good) 15:07:07 it seems to me that people should be allowed to test the nightlies but not required 15:07:13 * edwarnicke likes RED,YELLOW,GREEN :) 15:07:28 colindixon: I agree 15:07:31 colindixon: I agree, I think the thing to capture is the latest thing tested with... 15:07:49 # project contact, please info in your status: RED (not tested) YELLOW (tested and bad) GREEN (tested and good) 15:07:53 just saying that getting folks to update that might be a challenge 15:08:23 who start testing using RC0, any project? 15:08:25 #info tbachman for groupbasedpolicy: red 15:09:20 * tbachman waits for all the other projects to bust out of the gate 15:09:27 #info colindixon for TTP: yellow (found a few bugs that need to be patched) 15:09:39 #info edwarnicke for controller: many features, I'll need to aggregate data for tomorrow 15:09:48 #info goldvberg for lispflowmapping: yellow found (found one bug which was patched) 15:09:49 #info oflibMichal for openflowjava: green 15:09:56 lispflowmapping, release, vtn, plugin2oc, openflowplugin, openflowjava, integration, snbi, yangtools, mdsal 15:09:57 there we go :) 15:10:09 #info vjanandr for SNBI: red 15:10:10 #info Hideyuki for VTN :YELLOW (We need more tests with OF plugin. We need to put VTN Coordinator to the Karaf distribution.) 15:10:24 /me is debugging a custom karaf distribution at the same time 15:10:53 #info asaforon for d4a: red 15:11:18 PriyankaChopra: plugin2oc? 15:11:25 ttkacik: MD-SAL and yangtools? 15:11:37 tho I guess those are really tested by all :) 15:11:44 tbachman: thanks 15:12:06 #topic meeting time 15:12:19 I switch the topic 15:12:29 because there are people cannot make this time 15:12:35 oflibMichal: openflowjava? 15:12:41 #info PriyankaChopra for plugin2oc : red 15:12:53 tbachman: green 15:12:54 oh, sorry 15:12:57 saw that above 15:13:00 sorry oflibMichal 15:13:03 tbachman: np 15:13:17 CASP3R: integration? 15:13:26 yes 15:13:29 green? 15:13:50 also, I think we can do different times of this meeting, so people can join, the drawback is it will be confusing for people, any idea? 15:13:52 I think we're still yellow cause of the karaf testing setup 15:14:02 CASP3R: can you info that it? 15:14:11 * edwarnicke is seized by the mischievous temptation to start a project named 'green' 15:14:16 lol 15:14:17 #info Integration yellow due to karaf testing not fully setup 15:14:21 CASP3R: What's going on there? 15:14:22 CASP3R: thx! 15:14:35 basic its around having feature-all and feature-only 15:14:53 feature-all isn't stable (on a call right now looking into it) 15:15:31 back to time change 15:15:34 Ah.. the kitchen sink thing... yes... we need to explore that :) 15:15:44 gzhao: were there any specific time requests made? 15:15:48 Madhu: you made it 15:15:51 or “just not now” ;) 15:16:02 gzhao: yes... but this time really really sucks for me guys. 15:16:02 Maybe its good to find out what the local time is for all the folks here currently? 15:16:19 Madhu: would having another one later work? 15:16:22 To make sure we can accomodate reasonably our global geographic spread 15:16:39 I question the need for daily standup meetings on this 15:16:53 twice a week maybe.. 15:17:05 Madhu: fair enough. I forget what we did for Hydrogen 15:17:20 there are people have difficulties to attend this meeting at this time, I wonder if we can have two days in a week to start at different time, e.g Tues, Thurs at 7:30, M.W.F at other time 15:17:27 Madhu: 15:17:31 I do think that developers need time — particularly up front — to address and fix bugs 15:17:34 Madhu: I think the idea isn’t necessarily that *everyone* has to show up *every* time, but we want a critical mass to show up so we can make sure people understand what problems are going on and can get some help 15:17:52 colindixon: sure.. 15:17:56 Madhu: daily fill the spreadsheet, meeting twice a week is sufficient in my mind 15:17:59 and I offered to stay away from this meeting :) 15:18:01 Looks like its currently 5:16pm in Europe, 6:16pm in Israel , 8:46pm in India, 11:16pm in Taipei and 12:16am in Tokyo 15:18:09 because this time doesn't work for me. sorry guys 15:18:19 gzhao: i think so too 15:18:20 gzhao: We have a bunch of other stuff I think we need to organize around 15:18:23 Cleaning up logs 15:18:24 etc 15:18:27 Madhu: meeting frequency aside - does later work better? 15:18:31 What we found in Hydrogen was there were a lot of details 15:18:34 tbachman yep. 15:18:38 And we needed daily cadence to get them handled 15:18:41 anytime after 9am PT is good for me 15:18:52 edwarnicke: did we do a daily cadence for Hydrogen? 15:19:04 tbachman: that really does not matter :) 15:19:13 I think we should allow projects to make their own decision for attendance 15:19:17 but the general notion of daily cadence is a bit too much 15:19:18 but again 15:19:22 in the end, they know best how their time is spent 15:19:25 as colindixon said it is optional 15:19:36 tbachman: we did a twice daily meeting 15:19:38 folks can attend only if they are blocked or needing help 15:19:39 as I recall, there were multiple meetings per day to cover the different time zones 15:19:41 wowsa 15:19:51 9am PST is 7pm Europe, 8pm Israel, 10:30pm India, 1am Taipei, 2am Tokyo... so basically terrible for all non-NA timezones 15:20:09 I can see us offering two meetings 15:20:22 and letting the projects decide when to attend 15:20:23 in the end 15:20:33 tbachman: you don't mean on the same day? 15:20:34 if a project has critical bugs to fix, that are holding up others 15:20:37 tbachman: that’s what I did 15:20:40 yes on the same day 15:21:04 what to folks think of that? 15:21:08 H had twice daily meetings - one on a europe centric time, the second on an asia centric time 15:21:11 I think we’ve done something similar for other things 15:21:16 Yeah 15:21:20 one was early, the other late 15:21:26 from what I see, majority wants to keep meeting daily. 15:21:46 regXboi: do you remember the times? 15:21:50 I think we had one that was 9a PST and one that was 5p PST 15:21:59 colindixon: that sounds familiar 15:22:02 I can go look 15:22:28 I ask only b/c I recall that there was some serious canvasing to find the absolute best options there 15:22:33 so 15:22:33 so, no need to reinvent the wheel :) 15:22:35 #link https://wiki.opendaylight.org/view/CrossProject:Hydrogen_Release_Work 15:22:50 9 am PST and 5:45 pm PST 15:22:51 5:45 15:22:52 interesting 15:22:54 okay 15:23:07 don’t know how you got the :45, but we can run with it 15:23:16 what do folks think> 15:23:19 9am PST is still pretty brutal for Europe and the Middle East 15:23:20 ask colindixon - I don't remember :) 15:23:23 we have 8 minutes, any proposal? 15:23:40 #info regXboi proposes reusing the H process of dual daily cadence 15:23:41 edwarnicke: Madhu will 8:30 work? 15:23:50 Keep 7:30am PST for Europa and do a 5pm PST for Asia and PST? 15:24:22 #info edwarnicke propose Keep 7:30am PST for Europa and do a 5pm PST for Asia and PST 15:24:30 edwarnicke: I don't care about the times - I just think two is better than one 15:24:39 regXboi: ACK :) 15:24:49 tbachman: the :45 was make to make it short (it was supposed to be 15 minutes) 15:25:02 colindixon: that would be a good tenant to keep :) 15:25:17 tbachman: it didn’t work 15:25:18 gzhao: if am the only one 15:25:22 i would suggest don't change anything 15:25:23 shall we keep 7:30 as is to avoid confusion, and add a couple of 5:00pm PST Mon and Wed 15:25:32 I can certainly manage without attending the meeting 15:25:43 and if someone needs my help, they can catch me anytime on IRC 15:25:44 Madhu: lol 15:25:56 tbachman: am serious :) 15:26:04 :) 15:26:21 gzhao: edwarnicke colindixon tbachman if we can simplify it without my time availability 15:26:36 gzhao: were there others interested in different times/ 15:26:37 ? 15:26:42 http://www.timeanddate.com/worldclock/meetingtime.html?iso=20140912&p1=283&p2=24&p3=43&p4=735&p5=438&p6=241&p7=248 15:26:44 anyone else here interested in other time options? 15:27:39 colindixon: That link is awesome, could you add Tel Aviv ? 15:27:57 okay folks, 3 mins left 15:28:05 and we should get the meeting times resolved 15:28:15 http://www.timeanddate.com/worldclock/meetingtime.html?iso=20140912&p1=283&p2=24&p3=43&p4=735&p5=676&p6=438&p7=241&p8=248 15:28:24 unless I hear that others are interested in an additional time, I’m inclined ot keep just the one, at the current time 15:28:31 if you add TEl-Aviv it would be great 15:28:46 AsafOron: I think he just did? 15:28:53 #info unless I hear that others are interested in an additional time, I’m inclined ot keep just the one, at the current time 15:29:02 it seems like 7:30a and 7:30p is what woud make it work 15:29:05 gzhao: thx! 15:29:32 Madhu: is 7:30pm any better for you? 15:29:39 shall we request project that cannot attend send out the status template update 15:29:48 rofl... guys i don't want to be a spoilt sport 15:29:52 I have a family :) 15:29:56 Let’s start with 7:30am 15:30:02 yes he did, saw it just now. tx 15:30:03 so... please decide on a time without my consideration 15:30:10 and if folks need the other time, we can add the pm 15:30:20 tbachman: we can start with that 15:30:34 colindixon: tbachman expect some nag from me post 9am :) 15:30:36 #link http://www.timeanddate.com/worldclock/meetingtime.html?iso=20140912&p1=283&p2=24&p3=43&p4=735&p5=676&p6=438&p7=241&p8=248 this shows the time zones we have people in (that I know of) 15:30:56 #info we can start with keeping just the 7:30am PST meeting, and add a 7:30pm PST meeting if folks need it 15:30:59 going once 15:31:02 going twice 15:31:06 Madhu: fair enough, to make it *reasonable* for everyone, we really need 3 meetings 15:31:14 tbachman: call it 15:31:17 15:31:23 okay 15:31:26 anything else? 15:31:32 otherwise we’ll call it for today 15:31:46 once 15:31:48 twice 15:31:52 #endmeeting