David, I have synced with Fatih already and I will do my best to help on the CD front (time permitting). Note that my primary involvement in OPNFV is not versioning but since my project NFVbench is coming from a CD environment I might as well contribute there to make sure I’m not getting into trouble ;-) I will keep Frank in the loop of course.
Thanks for writing that wiki page. Regards, Alec From: David McBride <dmcbr...@linuxfoundation.org> Date: Friday, September 15, 2017 at 12:04 PM To: "Alec Hothan (ahothan)" <ahot...@cisco.com> Cc: TECH-DISCUSS OPNFV <opnfv-tech-discuss@lists.opnfv.org>, opnfv-project-leads <opnfv-project-le...@lists.opnfv.org>, Aric Gardner <agard...@linuxfoundation.org>, Raymond Paik <rp...@linuxfoundation.org>, Trevor Bramwell <tbramw...@linuxfoundation.org>, Tapio Tallgren <tapio.tallg...@nokia.com> Subject: Re: [opnfv-project-leads] [release][euphrates] stable branch window Hi Alec, I really appreciate your interest in and knowledge of configuration management and versioning. This is an important topic that doesn't get enough attention, IMHO. I don't mind your questions at all. Yes, you are correct about the branch name. The change in versioning has not affected the branch naming. As you said, the the branch will be "stable/euphrates". My apologies for not being clear about that. As far as your proposal is concerned, here are a couple of suggestions: · Please make sure that you coordinate with Fatih, since he is working on a new proposal for versioning that will take into consideration XCI. I don't think it would be productive for both of you to be working on separate versioning proposals in isolation. · Also, if you haven't already, make sure that you involve your Cisco TSC representative, Frank Brockners. Frank is very familiar with TSC policies and procedures and can advise you on preparing an effective presentation and getting it on the agenda. David On Fri, Sep 15, 2017 at 11:41 AM, Alec Hothan (ahothan) <ahot...@cisco.com<mailto:ahot...@cisco.com>> wrote: David, That might look obvious but perhaps you could confirm the exact branch name moving forward (or perhaps this has not changed). From the look of existing branches, looks like it will be “stable/euphrates” I assume projects can/will commit stuff on that branch until some code freeze milestone? Could you point to the remaining limestone agenda for euphrates? And I assume there will be at some point tags to point to subrelease (5.0, 5.1…) on that branch? When will these tags be created and what format will they have? I’m trying to get a proposal out for tagging/CD and would like to avoid OPNFV release tags with “5.0.0” format if possible (will explain why in my proposal). Sorry if I ask many questions, Thanks Alec From: <opnfv-project-leads-boun...@lists.opnfv.org<mailto:opnfv-project-leads-boun...@lists.opnfv.org>> on behalf of David McBride <dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>> Date: Friday, September 15, 2017 at 11:26 AM To: TECH-DISCUSS OPNFV <opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>>, opnfv-project-leads <opnfv-project-le...@lists.opnfv.org<mailto:opnfv-project-le...@lists.opnfv.org>> Cc: Aric Gardner <agard...@linuxfoundation.org<mailto:agard...@linuxfoundation.org>>, Raymond Paik <rp...@linuxfoundation.org<mailto:rp...@linuxfoundation.org>>, Trevor Bramwell <tbramw...@linuxfoundation.org<mailto:tbramw...@linuxfoundation.org>>, Tapio Tallgren <tapio.tallg...@nokia.com<mailto:tapio.tallg...@nokia.com>> Subject: Re: [opnfv-project-leads] [release][euphrates] stable branch window Reminder... In a few minutes, Aric will begin generating branches for projects that have not yet been branched. Exceptions: • RelEng • Projects that did not participate in the release • Projects that withdrew from the release List: 1. Apex 2. Armband 3. Bamboo 4. Barometer 5. Bottlenecks 6. Calipso 7. Compass4nfv 8. Daisy4NFV 9. Doctor 10. Domino 11. FastDataStacks 12. Fuel@OPNFV 13. FUNCTEST 14. High availability (HA) 15. IPv6 16. JOID 17. KVMforNFV 18. Moon 19. NFVBench 20. Octopus 21. OpenRetriever 22. OPNFVDOCS 23. OVNO 24. Orchestra 25. OVN4NFV 26. Parser 27. Pharos 28. Promise 29. QTIP 30. SampleVNF 31. SDNVPN 32. SFC 33. StorPerf 34. VSPerf 35. Yardstick On Fri, Sep 8, 2017 at 4:24 PM, David McBride <dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>> wrote: Reminder... The stable branch window closes as of MS7, one week from today, on September 15 at 12 p.m. (PT). PTLs - please contact Aric as soon as you're ready to branch. Aric will branch any projects that have not already been branched on Sept 15. Let me know if you have any questions. David On Tue, Aug 29, 2017 at 3:23 PM, David McBride <dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>> wrote: Team, As you know, MS6 was this past Friday, Aug 25. In addition to the requirements associated with MS6, this milestone also marks the opening of the stable branch window, which subsequently ends with MS7 on Sept 15. This means that PTLs may request to branch their project any time before Sept 15. Note that I erroneously told the release meeting this morning that PTLs may create their own branch. That's not the case. Instead, please contact Aric (copied) and request that he create the branch for you. Also, as a reminder, we have changed the version number format as of the Euphrates release. • 5.0.0 - Euphrates initial release version • 5.1.0 - Euphrates SR1 • 5.2.0 - Euphrates SR2 Let me know if you have any questions. David
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
