02:31:28 <ekcs> #startmeeting congressteammeeting 02:31:29 <openstack> Meeting started Fri Jan 26 02:31:28 2018 UTC and is due to finish in 60 minutes. The chair is ekcs. Information about MeetBot at http://wiki.debian.org/MeetBot. 02:31:30 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 02:31:33 <openstack> The meeting name has been set to 'congressteammeeting' 02:31:39 <masahito> hi 02:31:53 <ekcs> hello all. today’s topics are kept here as usual https://etherpad.openstack.org/p/congress-meeting-topics 02:32:01 <ekcs> please read/comment/add =) 02:32:05 <ekcs> hi masahito ! 02:32:18 <ekcs> how’s it been? 02:36:46 <masahito> Good. 02:36:55 <ramineni_> ekcs: hi 02:37:05 <ekcs> hi ramineni_ ! 02:37:06 <ramineni_> masahito: hi 02:37:15 <masahito> ramineni_: hi 02:37:21 <ekcs> masahito: hope blazar feature freeze went well =) 02:38:02 <masahito> thanks. just working on tagging for some repo naw :-) 02:38:23 <ekcs> masahito: =] 02:38:27 <ekcs> ok let’s get started then. https://etherpad.openstack.org/p/congress-meeting-topics 02:38:33 <ekcs> #topic queens-3 02:38:42 <ekcs> server, dashboard released for queens-3 02:38:52 <ekcs> client branched at 1.9.0 02:39:24 <ekcs> finished quite a bit of work during this cycle. here are some notable ones: 02:39:33 <ekcs> policy library UI 02:39:33 <ekcs> mistral driver 02:39:35 <ekcs> config validator 02:39:36 <ekcs> QoS extension neutron driver 02:39:38 <ekcs> support for network microsegmentation use case (neutron and nova driver improvements) 02:39:39 <ekcs> goal: register policy in code 02:39:40 <ekcs> goal: support python 3.5 02:39:41 <ekcs> goal: tempest plugin (expected) 02:40:02 <ekcs> any thoughts/comments/questions on queens-3? 02:42:29 <ekcs> ok moving on then if no comments =) 02:42:41 <ekcs> #topic RC1 02:43:23 <ekcs> next major deadline is RC1. in two weeks. 02:44:04 <ekcs> here I have re-organized things to show the tasks we still have left to complete by RC1. 02:44:07 <ekcs> https://etherpad.openstack.org/p/congress-task-priority 02:44:32 <ekcs> please add other important ones if I missed any. 02:45:11 <ekcs> basically this is time for us to wrap up any finishing touches to have a polished, stable, and well documented release. 02:45:24 <ekcs> maybe maintainable too =p 02:45:41 <ekcs> thoughts/comments/questions? 02:47:38 <ramineni_> Rc1 deadline 02:47:43 <ramineni_> ? 02:48:03 <ekcs> it’s the week of 2/5. basically just under two weeks from now. 02:50:19 <ekcs> ok moving on then if nothing else to discuss here. 02:50:29 <ekcs> #topic PTL nomination 02:51:01 <ekcs> if anyone is interested in becoming PTL, the self-nomination period begins on 1/29. 02:51:28 <ekcs> here’s more information: https://governance.openstack.org/election/ 02:52:58 <ekcs> and that’s all the topics I have planned for today. anything else we’d like to discuss? 02:53:46 <masahito> Just a question for Q-3 release. 02:54:16 <ekcs> yup masahito 02:54:20 <masahito> Does all client libraries start to have stable branch now? 02:54:36 <masahito> IIRC, 02:55:16 <masahito> Python clients are released without stable branch before. 02:55:41 <ekcs> actually for congress we’ve had stable branches for a long time. as far back as I can remember. 02:55:57 <ekcs> I see stable/ocata branch in repo. 02:56:02 <ekcs> I think it depends on the release model. 02:56:20 <ekcs> as far as I know, if release model is cycles with milestones or cycles with intermediary then there is stable branch. 02:56:56 <ekcs> for independent release model there may not be stable branch required. 02:57:13 <masahito> okay, thanks :-) 02:57:13 <ekcs> https://releases.openstack.org/reference/release_models.html 02:57:32 <ekcs> np =) 02:58:47 <ekcs> anything else to discuss? or should we end early? 02:59:11 <ramineni_> Nothing from my side 02:59:55 <ekcs> btw masahito here’s what smcginnis said in his email about client library 03:00:01 <ekcs> Next Thursday is the final client library release. Releases will only be 03:00:02 <ekcs> allowed for critical fixes in libraries after this point as we stabilize 03:00:04 <ekcs> requirements and give time for any unforeseen impacts from lib changes to 03:00:05 <ekcs> trickle through. 03:00:07 <ekcs> When requesting these library releases, you should also include the stable 03:00:08 <ekcs> branching request with the review (as an example, see the "branches" section 03:00:09 <ekcs> here: 03:00:10 <ekcs> http://git.openstack.org/cgit/openstack/releases/tree/deliverables/pike/os-brick.yaml#n2) 03:01:02 <ekcs> ok then. let’s end meeting. have a great weekend and a great queens release! 03:01:11 <smcginnis> ekcs: You are correct. 03:01:37 <ekcs> thanks smcginnis ! 03:01:57 <smcginnis> ekcs, masahito: Thanks for checking! 03:02:00 <smcginnis> win 4 03:02:04 <smcginnis> Oops. :) 03:02:13 <ekcs> bye all. #endmeeting 03:02:16 <masahito> smcginnis: thanks! 03:02:18 <ekcs> #endmeeting