16:00:03 #startmeeting OPNFV release 16:00:03 Meeting started Tue Feb 28 16:00:03 2017 UTC. The chair is dmcbride. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:03 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:00:03 The meeting name has been set to 'opnfv_release' 16:00:10 #topic roll call 16:00:15 #info David McBride 16:01:29 #info Bryan Sullivan 16:03:23 #info Stuart Mackie 16:03:30 #info Serg Melikyan 16:04:05 #info Morgan Richomme 16:04:12 #info Tim Rozet 16:04:19 #info Trevor Cooper 16:04:34 #info Jose Lausuch 16:05:37 #info Georg Kunz 16:06:05 #info Maryam Tahhan 16:06:09 available on IRC only today 16:08:22 #topic MS6 16:08:29 #link https://wiki.opnfv.org/display/SWREL/Milestone+Compliance+for+Danube 16:11:52 #link https://wiki.opnfv.org/display/DOC/Documentation+Guide 16:13:35 #info will proposed documentation changes be rolled out for Danube, or for the E-release? 16:31:51 #action morgan_orange summarize proposal for testing section to be shared by mail with Sofia and community 16:35:15 #topic MS7 - stable branch 16:36:30 #info MS7 (March 10) closes the window 16:37:46 #link https://wiki.opnfv.org/display/SWREL/Git+Tagging+Instructions+for+Danube 16:38:04 #info git tagging instructions for Danube ^^ 16:44:32 #topic versioning 16:46:05 #info suggest changing format of versioning 16:46:11 jmorgan1: colorado.1.0 vs 3.1.0-colorado 16:47:01 #info for example, Colorado.1.0 would become 3.1.0-colorado 16:48:09 #info 3.1.0 == 3.1.0-colorado 16:48:36 #info follows conventional major.minor.patch labeling scheme 16:50:45 #action dmcbride to research how other upstream components do labeling 16:51:35 #link https://releases.openstack.org/ 16:52:37 #info Bin points out that OpenStack simply uses a three digit label 16:54:56 #topic test milestones 16:55:05 #link https://releases.openstack.org/ocata/ 16:55:16 #info jose_lausuch1 suggests "framework ready" 16:55:31 #info See the version numbering in OpenStack Ocata release 16:56:35 #info jose_lausuch1 says this MS should fall before test case implementation (MS6) 16:56:56 #link https://www.python.org/dev/peps/pep-0440/ 16:57:05 #info The above defines tagging format 16:57:29 thanks bh526r 16:57:37 #info e.g. 1.0.0, 1.0.0rc2, 3.0.5rc1 etc 17:00:48 #info trevor_intel says that test projects should follow feature release MSs as much as possible 17:04:49 #info feature projects have dependencies on test projects (i.e. test framework must be integrated and functional in order for feature projects to implement and execute test cases in CI that use that framework) 17:05:07 #endmeeting