17:59:47 #startmeeting tsc 17:59:47 Meeting started Thu Feb 22 17:59:47 2018 UTC. The chair is abhijitkumbhare. Information about MeetBot at http://ci.openstack.org/meetbot.html. 17:59:47 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:59:47 The meeting name has been set to 'tsc' 18:00:40 #chair skitt 18:00:40 Current chairs: abhijitkumbhare skitt 18:00:50 #topic Roll-call and agenda bashing 18:00:55 #info rovarga 18:00:59 #info TSC members please info in 18:01:01 #info skitt 18:01:04 #info abhijitkumbhare 18:01:09 #info Thanh Ha 18:01:44 #info rovarga 18:01:47 #info Brady Johnson 18:01:51 for good measure :) 18:01:55 bjohnson_: you are soft man. come on! 18:01:59 #info jamoluhrsen 18:02:07 ha ha, two rovargas 18:02:35 moar p0wer! :) 18:02:55 #info lori 18:03:01 #info LuisGomez 18:03:40 #info busy agenda today, only *very* high priority additional topics please 18:03:47 crickets 18:03:50 which is good 18:04:08 #info anipbu 18:04:15 #topic Oxygen 18:04:52 #info quick note that the TWS call on February 26 will be dedicated to discussing the ODL project goals for 2018 18:05:16 #info no green build yet for Oxygen 18:05:26 #info latest problem was in unimgr which has been removed from autorelease 18:06:00 #info shague 18:06:19 #info Anil Vishnoi 18:06:35 #info rovarga notes that since the branches haven’t been cut, we need to go back to the project plan to figure out where we are 18:06:49 #info (branches are supposed to be cut at the end of M4) 18:06:55 #info rovarga notes that Oxygen is now 4 weeks behind schedule 18:07:57 #info gzhao 18:08:17 skitt, I would like to discuss adding VTN back to O2 release 18:08:26 I had sent mail sometime back 18:08:54 gvrangan, is that the mail sent today at 17:29 UTC? 18:09:20 skitt: yes 18:11:40 gvrangan, let’s see if we have time at the end of the call 18:12:13 skitt: gvrangan if we are talking to cut/lock oxygen we probably want to vet out this idea that VTN is coming back in? 18:12:26 #action zxiiro and abelur to cut the Oxygen branches and lock them tomorrow 18:12:29 jamoluhrsen, good point 18:13:05 #agreed the branches will be cut on February 24 at 23:59 UTC 18:13:23 #undo 18:13:23 Removing item from minutes: 18:13:40 #agreed the branches will be cut on February 23 at 23:59 UTC 18:15:02 #info only patches fixing documented, blocker bugs will be accepted 18:15:52 #undo 18:15:52 Removing item from minutes: 18:15:53 #undo 18:15:53 Removing item from minutes: 18:15:56 +1 Sunday 25th at UTC 23:59 18:16:09 you make a lot of mistakes skitt :) 18:16:18 #agreed the branches will be cut on February 25 at 23:59 UTC 18:16:37 #info only patches fixing documented, blocker bugs will be accepted 18:16:51 jamoluhrsen, I know, I’ll resign my unofficial position of secretary 18:17:06 no no... sorry. you are doing great skitt 18:17:18 jamoluhrsen, thanks, I was playing along ;-) 18:17:47 #info vishnoianil thinks we should have a vote :) 18:18:25 skitt: thanks for much for keeping the notes! You're awesome! 18:18:28 rovarga it was your idea and 3 people agreed and rest of the folks didn't say anything ;) 18:18:46 vishnoianil, he did ask if anyone objected ;-) 18:19:06 #info we need to push the release date out by three weeks 18:19:47 #action abelur to begin branch cutting stable/oxygen on February 25th at 23:59 UTC (Monday morning for him) 18:22:18 #info we need to at least communicate that our release date is slipping 18:22:28 #info even if we can’t agree on a target release date right now 18:24:15 #info rovarga notes that we need three weeks to go from a clean build to a release (because it takes time to qualify a release and get the go votes etc.) 18:25:22 #info formal release will be four weeks after RC0, and SR1 four weeks after that 18:26:06 #topic Nitrogen and Carbon 18:26:12 #info close to getting all CSIT sign-offs 18:26:22 #info still missing SFC 18:26:33 #info dluxapps too 18:26:47 #action rovarga to reach out to dluxapps for CSIT sign-off 18:26:55 #link Carbon Tracking https://docs.google.com/spreadsheets/d/1VcB12FBiFV4GAEHZSspHBNxKI_9XugJp-6Qbbw20Omk/edit?usp=sharing 18:26:59 #action bjohnson_ to take care of SFC CSIT sign-off 18:27:31 #link Nitrogen Tracking https://docs.google.com/spreadsheets/d/1MYyGLFWN2RzUkJl8XMzXQ-3zWuOrUCQpIS6ORbmf4_U/edit?usp=sharing 18:27:48 #action jamoluhrsen to look into the MD-SAL CSIT issue in Nitrogen (which rovarga thinks is likely to be the same as Carbon) 18:28:22 #info jamoluhrsen notes projects have been good at providing information in this cycle, which will be very helpful when looking for regressions etc. in future 18:30:18 skitt: you can undo the action on jamoluhrsen 18:30:20 :) 18:30:21 sorry my Internet dropped 18:30:27 hah 18:30:56 sorry dude :) 18:31:01 yeah 18:31:03 you type way too fast :) 18:31:07 #startvote TSC agrees to release Carbon and Nitrogen SRs on the condition SFC signs off -1,0,+1 18:31:07 Unable to parse vote topic and options. 18:31:40 #startvote TSC agrees to release Nitrogen SR? -1,0,+1 18:31:40 Begin voting on: TSC agrees to release Nitrogen SR? Valid vote options are -1, 0, +1. 18:31:40 Vote using '#vote OPTION'. Only your last vote counts. 18:31:45 #vote +1 18:31:48 #vote +1 18:31:48 #vote +1 18:31:53 #vote +1 18:31:54 #vote +1 18:31:56 #vote +1 18:31:56 #vote +1 18:31:56 #vote +1 18:32:02 #vote +1 18:32:06 #vote +1 18:32:06 #vote +1 18:32:17 #endvote 18:32:17 Voted on "TSC agrees to release Nitrogen SR?" Results are 18:32:17 +1 (11): gzhao, rovarga, skitt, anipbu, LuisGomez, lori, abhijitkumbhare, zxiiro, bjohnson_, vishnoianil, jamoluhrsen 18:33:16 #info above vote is conditional on SFC sign-off for Nitrogen 18:33:25 #info SFC signed-off during the call for Carbon 18:33:59 #startvote TSC agrees to release Carbon and Nitrogen SRs on the condition SFC signs off? -1,0,+1 18:34:12 thanks bjohnson_ 18:34:18 #startvote TSC agrees to release Carbon and Nitrogen SRs on the condition SFC signs off? -1,0,+1 18:34:18 Begin voting on: TSC agrees to release Carbon and Nitrogen SRs on the condition SFC signs off? Valid vote options are -1, 0, +1. 18:34:18 Vote using '#vote OPTION'. Only your last vote counts. 18:34:23 #vote +1 18:34:24 #vote +1 18:34:26 #vote +1 18:34:29 #vote +1 18:34:29 #vote +1 18:34:30 #vote +1 18:34:34 #vote +1 18:34:36 #vote +1 18:34:38 #vote +1 18:34:52 #endvote 18:34:52 Voted on "TSC agrees to release Carbon and Nitrogen SRs on the condition SFC signs off?" Results are 18:34:52 +1 (9): skitt, zxiiro, LuisGomez, shague_, lori, abhijitkumbhare, anipbu, bjohnson_, vishnoianil 18:34:53 #endvote 18:35:24 #topic Managed release model 18:35:50 https://git.opendaylight.org/gerrit/#/c/68382 18:36:06 #link https://git.opendaylight.org/gerrit/#/c/68382 18:36:11 #chair dfarrell07_pto 18:36:11 Current chairs: abhijitkumbhare dfarrell07_pto skitt 18:36:22 duh misunderstood 18:36:44 #link https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/docs-rtd-verify-oxygen/975/html/release-process/managed-release.html 18:37:28 #info dfarrell07_pto only skimming today, everyone should read the above in detail 18:38:29 #info currently lot of overhead on releases, lot of checkpoints which are marginally useful, a lot of busy-work that could be automated or dropped 18:38:55 #info anything non-automated should be very well defined (in terms of how to report it) 18:39:09 #info aim is to make it easier to develop and manage development 18:39:32 #info Unmanaged projects relieved of some overhead 18:40:17 #info Unmanaged projects mostly free to do what they want 18:40:31 #info releases should meet their planned release dates more reliably 18:41:12 #info core projects will have to be part of the managed release 18:41:24 #info other projects can opt in, and the requirements will apply to them 18:41:40 #info "required" projects can’t be kicked out so the requirements can’t be enforced there 18:41:59 #info projects will give up some autonomy to be in the managed release, to give release teams autonomy 18:43:06 #info healthy community requirement: be responsive, all committers subscribed to appropriate lists, good communication re. coming breakages etc. 18:43:54 can we get a freaking picture of dfarrell07_pto's environment right now? 18:44:12 jamoluhrsen, +1 18:44:21 jamoluhrsen: +1 18:44:23 * bjohnson_ we want a picture of dfarrell07_pto in a Kilt! 18:44:24 jamoluhrsen, a selfie of dfarrell07_pto with the ghost living in the castle 18:44:39 can we action dfarrell07_pto to send a picture? :) 18:45:19 #action dfarrell07_pto to take a picture of him giving his meeting with the castle in the background. bonus points if we can feel how cold it is by the photo 18:45:28 #info please provide feedback on the gerrits for the release management patch 18:45:37 +1 jamoluhrsen :) 18:46:21 #info big change is that the TSC will be able to appoint committers in managed projects whose pool of committers is too small 18:48:04 heh ... that is going to be a funny one :) 18:48:06 #info checkpoints are automated as far as possible 18:48:24 #info human involvement is to create a readable summary of the work to be done in the release 18:48:37 #info also to notify any state *changes* 18:48:46 #info and weather items anticipated in the release (as JIRA tickets) 18:49:09 #info everything else is automated: blocker bugs, grievances etc. 18:49:47 #info since the middle checkpoint is automated, it might run multiple times in a release (once a month) 18:51:01 #info final checkpoint will require a report about what was done in the release, and updated docs 18:52:19 #info we need to make it clear that unmanaged projects can still be cool and part of ODL 18:52:31 #info we need to enforce the managed requirements to give them meaning 18:53:32 #info unmanaged projects have some requirements to be included in the distribution archive 18:53:46 #info but we will also document how they can be installed by users even if they’re not part of the release 18:55:32 #info not asking the TSC today, looking for more feedback on the patch 18:55:39 #undo 18:55:39 Removing item from minutes: 18:55:55 #info not asking the TSC to vote today, looking for more feedback on the patch (on the patch, not by email) 18:56:08 #info target is for Fluorine though so please look at this quickly 18:56:17 #info aim is to vote on this next week 18:58:15 #info rovarga's concern is the interplay of the managed release with spun-out projects, which needs to be fleshed out 18:59:32 dfarrell07_pto: thanks for driving that while on pto and in the cold by a castle. rockstar! 18:59:42 #info I think we could start simply collecting SW quality metrics in Fluorine, but not make it a part of the Managed Release process until after Fluorine 18:59:45 rovarga: what is the concern? in our managed model the spun out projects are just consumed. obviously there are date mechanics to be solved 19:00:15 shague_: simple: when outside of the autorelease, the release mechanics are completely disconnected 19:00:42 shague_: which means yangtools-3.0.0 can come in tomorrow, 2.0.2 can come in today 19:01:17 wow, that means at least 65 people will be at the ODL DDF 19:01:24 rovarga: shague_ I think we just need to put some sort of deadline for when autorelease projects will no longer bump to new versions of these things. 19:01:26 shague_: assumptions you guys have about how a SR is assembled are essentially shot :) which does require a slightly different wording/approach 19:02:17 shague_: essentially there need to be integration windows when things outside of autorelease land 19:02:43 shague_: but strictly speaking, those things are completely out of managed release for the entire time of their dev cycle 19:02:44 #info we will have a room for 50 people at the ODL DDF, and we could probably cram in around 70 people 19:03:09 rovarga: agreed. WE made a simple assumption that at the beginning of the release we have a certain version. if the spun out projects wants something else in to the MR, then we need to factor that in early 19:03:14 so we should show up with good Blu-rays then, right? 19:03:21 #agreed Thanks phrobb and CaseyODL for upgrading the room arrangements for the DDF 19:03:31 * bjohnson_ someone bring a playstation for the 90 inch TV we will have ;) 19:03:38 shague_: yeah, but obviously the release plan needs to account for things like yangtools-2.0.0 landing this cycle 19:03:45 ahead of time, obviously 19:04:06 #topic cookies 19:04:13 #endmeeting