19:01:06 #startmeeting Arno adjusted target release plan planning meeting :D 19:01:06 Meeting started Wed Apr 22 19:01:06 2015 UTC. The chair is ChrisPriceAB. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:01:06 Useful Commands: #action #agreed #help #info #idea #link #topic. 19:01:06 The meeting name has been set to 'arno_adjusted_target_release_plan_planning_meeting__d' 19:01:11 #roll call 19:01:16 * ChrisPriceAB just for prosperity 19:01:21 #Chris Price 19:01:26 #info Trevor Cooper 19:01:52 posterity or prosperity? 19:02:02 * ChrisPriceAB lol yeah it's late :D 19:02:20 #info Frank Brockners 19:02:21 I'm ok with prosperity! 19:02:22 #info ulik could not attend the (european evening) meeting 19:02:39 I would love it as well 19:02:48 * frankbrockners hmm ... I'm in Europe as well ... 19:02:49 #info morgan_orange on vacation until tomorrow 19:03:03 * ChrisPriceAB Cry me an Arno so am I!!!! 19:03:04 * frankbrockners doing something wrong... 19:03:08 lol 19:03:30 #topic wiki updating readiness of information 19:03:47 * ChrisPriceAB lets move fast, just want to make sure we are all clear on what the plan is 19:04:12 #link https://wiki.opnfv.org/releases/arno/releasereadiness Arno overall release raediness tracking wiki mpage. 19:04:38 #info Is everyone happy with the level of detail of the items on the list at this time? 19:04:58 #info yes for me I think its what we need 19:05:05 #info I may add some details to the docs items as I think a 3 day action is a little too long for the type of iterations we need here 19:05:25 #info have a pending action to collate the infrmation available to perform first :D 19:06:04 #info Ok great. Another thing I would like to do is to begin to identify dependancies between tasks on the list. 19:06:17 #info on docs: Could we add an entry that asks for a list of *all* required docs across all projects? 19:06:41 #info Yeah sure, feel free to plug it in there or action me 19:06:51 This needs to be clear for everyone 19:07:23 #action ChrisPriceAB: Add an entry for docs that lists *all* required docs across all projects 19:07:39 #info second thing i would like to see if Jira stories on each. I noticed Fatih has already done that for octopus, I will do so on docs once I get a chance to sync with my team 19:07:41 on cross dependencies 19:08:07 #info although I realize it may be a little tough to spin it up all over the place and still focus on the gting the job done, so I don't think it should be mandeted 19:08:11 could we consider just doing the major things for now? 19:08:15 #info Jira is missing for Pharos ... I have to do that 19:08:15 #undo 19:08:15 Removing item from minutes: 19:08:22 #info although I realize it may be a little tough to spin it up all over the place and still focus on the gting the job done, so I don't think it should be mandated 19:08:43 #info Donät let Jira gate you on getting stuff done... 19:08:55 * frankbrockners you undid the wrong item... 19:09:03 #info just helps with tracking and knowing who has the ball on items 19:09:03 #info ... these are just the tasks, correct? 19:09:11 lol so I did 19:09:30 #info Jira is missing for Pharos ... I have to do that (trevor_intel) 19:10:09 Yes can be tasks to keep it simple. Some are using stories in order to organise specifi tasks in an area, but that's Jira 102, not Jira 101 19:10:24 on x-dependencies: Should we just focus on the major tasks - and reference them by name as opposed to number all items and use the number? 19:10:24 Ok 19:10:34 I'd like to avoid renumbering... 19:10:53 Yes we can do that. Can we organise by theme? I think each project needs to tackle that itself a little 19:11:10 theme is good for me 19:11:37 I'm fine with it. We can remove the numbering as I realised when I got started just what a bad idea it was 19:12:02 #topic Setting the plan and timeline 19:12:15 #info just to get our minds on this topic. We also need to move into this phase. 19:12:51 #info once we have a good idea of the tasks/dependancies etc. I think we can finalize this bit on the meeting just before the TSC call tomorrow. 19:13:17 #info I will start a section at the top of the WiKi where we can capture the planning part and let's try and keep our thoughts up there 19:13:29 #info estimated duration of the tasks is critical info to have 19:13:41 #info and I don't think we have this for functest by tomorrow 19:13:56 #info yes. Is also tough on the first iteration to get it right. And we only have one iteration... 19:14:24 #info you are right, I plan to get as much as we can in place by tomorrow. Hopefully it does not present as the critical path... 19:14:35 #info functest that is 19:14:48 at a high level it would be: today + (BGS to install to 3rd-party lab) + (BGS automation) + (FuncTest automation) 19:15:09 which assumes that (Functest manual) < (BGS to install to 3rd-party lab) + (BGS automation) 19:15:14 That's the general gist. Easy at 10000 ft 19:15:29 so in summary max ((Functest manual), (BGS to install to 3rd-party lab)) + (BGS automation) 19:16:02 + slack for docs readiness, packaging etc. 19:16:06 Yeah, but I still see a risk functest might present as the critical path.... then we need ppl to help 19:16:26 #info anything else to capture on the planning piece at this time? 19:16:33 ack - which the above says max()... so Functest might win 19:16:44 I think its a big risk 19:16:49 and there is the x-dependency: unless functest works we don't know whether bgs works 19:16:58 so post functest works bgs might have additional work to do 19:17:14 hehe yeah there's the catch. 19:17:28 so refined: 19:17:40 #topic any other items? 19:17:52 #info anything else we should capture in the meeting? 19:18:00 max ((Functest manual), (BGS to install to 3rd-party lab)) + (BGS automation) + (BGS fixes for all tests) + (Docs + Packaging) 19:18:26 Oh cool, I just put an integer into each and I get the answer :D 19:18:28 #info rough estimate (once we have data): time needed = max ((Functest manual), (BGS to install to 3rd-party lab)) + (BGS automation) + (BGS fixes for all tests) + (Docs + Packaging) 19:18:48 * ChrisPriceAB x to the power of (foo,bar) 19:19:10 ack - but even with small integers things add up... 19:19:20 it's getting late for me this week. 19:19:25 what day is it? 19:19:31 Friday 19:19:40 * frankbrockners no idea any more 19:20:08 you want another check in tomorrow morning? 19:20:09 #info Ok, so I will try to iterate on the docs items. Add a planning section at the top of the page. First realignment early Europe time, second realignment early US time. 19:20:24 Yes at least to get Morgan onboard 19:20:32 * frankbrockners fingers crossed 19:20:58 :) finally got an sms conversation with him today. He's back tomorrow. But he will land in a huge backlog 19:21:37 ok - r we done? 19:21:38 ok thankls guys. Unless we have something to follow with I'm happy to close 19:21:47 trevor_intel anything? 19:21:53 ok for now 19:21:57 same here 19:21:58 #endmeeting