#opnfv-meeting: Synchronised Release discussion

Meeting summary

1. General discussion of SR (dneary, 15:20:35)
   1. current plan is march 2015 is helium/juno based and just upstream integration (no new features) (cdub, 15:21:13)
   2. postponing for kilo isn't currently justified (no clear idea waht we'd get from waiting for kilo) (cdub, 15:21:48)
   3. dlenrow asks whether there is any opposition to the initial release plan for March, which is releasing integrated Juno + Helium and dependencies for upstream projects (dneary, 15:21:54)
   4. ChrisPriceAB confirmed that the board has been working on Juno + Helium as a base, and he has not heard anyone argue against that (dneary, 15:23:10)
   5. dneary asked whether we have a good idea of what we would gain from moving to Kilo, and also remarked that we do not yet have a basis to build on and get out in front of the upstream projects (dneary, 15:24:18)
   6. Palani went over the VNFs which are currently being considered to test the platform in response to a question about which workloads people plan to run on the initial release (dneary, 15:25:22)
   7. There was some further discussion on the realism of aiming for anything more than the current plan of integrating past upstream releases, and ChrisPriceAB proposed that we move on to discussion of the process of release rather than focussing on the scope of the project for now. (dneary, 15:28:03)
   
   
2. Simultaneous Release process (dneary, 15:28:17)
   1. dlenrow showed the current planning for the first release, with milestones for consideration of projects being included and deliverables (dneary, 15:29:37)
   2. m2 is 12/30, unclear we'll have any projects by then (cdub, 15:30:54)
   3. cdub pointed out that 2014-12-30 is in one month, including a week of US holidays and a short week, and it seems unrealistic to expect any projects to be ready to integrate the release in that process (dneary, 15:31:27)
   4. m4 is 2/15/15 and that's an anchor for delivering march release 3/15/15 (cdub, 15:32:01)
   5. Fundamental question is, what do we deliver? Git tags, packages, VM images, kickstart files, ...? (dneary, 15:34:43)
   6. general agreement that "get started/bootstrap" is the most fundamental project right now to get moving, suggestion to focus on it to enable us to start identifying gaps, and filling them. (dneary, 15:39:19)
   7. It was suggested (sorry, didn't recognise the voice) that Get Started could define required pieces which would easily enable others to replicate the stack with alternative components (eg. OS, config mgmt tool, etc) (dneary, 15:53:27)
   8. Uli suggested that maintaining focus for Getting Started was required to get something done. These approaches are compatible. (dneary, 15:54:15)
   9. Next Monday there are two relevant meetings: Octopus (15h-16h UTC) and Get Started (16h-17h UTC) (dneary, 15:59:16)
   10. Luc Lemieux asked where he can find details about the Monday meetings. Email was sent to the opnfv-tech-discuss list, dlenrow suggested we should get better about adding meetings to the wiki. (dneary, 16:05:31)

Action items

1. (none)

People present (lines said)

1. dneary (21)
2. cdub (6)
3. collabot (2)