18:00:53 #startmeeting 18:00:53 Let the Jenkins meeting commence! 18:00:58 #chair danielbeck kohsuke_ 18:00:58 Current chairs: danielbeck kohsuke_ rtyler 18:01:07 danielbeck: you running this one or am I again? :) 18:01:18 present 18:01:22 rtyler I'm here now 18:01:25 o/ 18:01:32 #info https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda 18:01:41 #topic Recap last meeting's actions 18:01:55 #info http://meetings.jenkins-ci.org/jenkins-meeting/2018/jenkins-meeting.2018-03-14-18.00.html 18:02:09 rtyler ogondza you had an item 18:02:18 (2.107.1 is obviously out :-) ) 18:02:21 o/ 18:02:28 it it 18:02:47 I did followed up w.r.t. moving LTS tests to ci.j.io 18:02:48 * kohsuke_ joins a little late 18:03:07 ogondza: I've been so swamped I cannot honestly remember what we talked about 18:03:19 designed, tracked, scheduled for next 2 weeks 18:03:28 rtyler, not a problem - nothing for you to do 18:03:41 yey 18:03:49 \o/ 18:04:01 let's move on then 18:04:08 thanks for runATH() by the way, adopted it in my test flows 18:04:12 works great 18:04:21 \o/ 18:04:21 #topic LTS status check 18:04:30 ogondza :) 18:04:38 last minute backport added couple of hours ago 18:04:42 tests in progress 18:04:48 the java 9 error? 18:05:03 and Java 10 :( 18:05:13 provided nothing blows up, RC will be tomorrow 18:05:22 JENKINS-49737 is part of it 18:05:40 that is that last minute backport 18:05:45 ok 18:05:54 yes, that's the one oleg-nenashev and I were referring to 18:05:55 thanks! 18:06:07 JEP-200 regression is also ported 18:06:16 which one? :P 18:06:22 when do we start supporting these releases, btw? :P 18:06:23 next topic :D 18:06:25 too soonnnn 18:07:02 Java 9+ is a *big* chunk of work, contributions welcome (c) 18:07:21 #info https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.107.2-fixed 18:07:22 woah 18:07:23 * batmat +1 18:07:33 #info https://issues.jenkins-ci.org/browse/JENKINS-40689 18:07:37 yeah, spent a week on that a while ago 18:07:53 ogondza: I think we lack the bandwidth and the driver to make Java 9 support happen 18:08:43 We will have to do that at some point tho. Sooner or later 18:08:45 I have some thoughts wrt how we should do it, which I discussed offline with people like oleg-nenashev but if you have any thoughts on how to tap into broader contributor community, that'd be greatly appreciated 18:08:52 kohsuke_: Have we measured the set of Java 9 failures. 18:08:53 a topic for the dev list perhaps, but not now 18:09:04 danielbeck: sorry 18:09:16 danielbeck: got it. 18:09:22 agreed, separate topic 18:09:22 agreed, sorry for the rant 18:09:23 shall we move on from LTS status? 18:09:32 please 18:09:36 #topic JEP-200 update 18:09:40 oleg-nenashev this is yours 18:09:45 #info: JEP-200 has been released in 2.107.1, announcement: https://jenkins.io/blog/2018/03/15/jep-200-lts/ 18:10:05 TL;DR: https://usercontent.irccloud-cdn.com/file/NaOCz675/Screen%20Shot%202018-03-28%20at%2011.00.32.png 18:10:25 We have got 20 JEP-200 issues since 2.107.1 release 18:10:27 heh 18:10:30 I don't understand why you take a new screenshot of that every day 18:10:42 :D 18:10:44 :P 18:10:46 #info We hit one regression in the core (JENKINS-50237), backported to 2.107.2 + workaround 18:11:00 #info The most of the serious regressions are fixed. The biggest issue is Google OAuth Plugin (JENKINS-50216), >3000 installations 18:11:20 We got a response from a maintainer, but we have issues with Google CLA required to submit patches 18:11:43 All other plugins are niche or obsolete ones 18:11:58 Though we had another round of fixes in Maven/Subversion 18:12:15 D: 18:12:30 Maven's still used way too much :( 18:12:38 So... Does anybody have any questions? If no, read the blogpost and upgrade ;) 18:13:08 #info Community ratings for 2.107.1 LTS is good (similar to previous ones) 18:13:26 * batmat thinks about JENKINS-46684... 18:13:31 So likely we didn't really nuke everybody, waiting for April 01 community stats 18:13:33 oleg-nenashev thanks for handling this. I cannot imagine the amount of work. Whenever I see you edit the wiki page and it's a plugin with 62 installs… 18:13:55 We had 100 JIRA issues since the release 18:14:02 1.5 per day avg. 18:14:19 ouch 18:14:36 ~70 affected plugins so far. Yeah, some fun 18:14:53 oleg-nenashev thanks for the update 18:14:57 wow 18:14:58 Thanks to all reviewers and plugin maintainers who help us to keep it contained 18:14:59 Many of the fixes I would have made anyway… 18:15:09 Indeed heroic work from oleg-nenashev. Hats off to him. 18:15:18 + jglick 18:15:22 Actually also kudos to jglick 18:15:32 * batmat frantically looks for an hats off emoji 18:15:33 But it also underscores the need to approach this kind of changes differently in the future 18:15:52 Sorry for missing jglick. No disrespect intended 18:15:59 Yes, looking forward to see Essentials and related features 18:16:04 depublish early, depublish often? 18:16:18 jglick says the guy who re-published a plugin that had been removed :P 18:16:29 heh 18:16:48 #action all to contribute to Jenkins Essentials 18:17:04 hah 18:17:09 perhaps time to look at how Drupal et al are doing this. Maybe we actually need to move towards semantic versions. 18:17:34 Ok, any questions? 18:17:43 (looks like I'm derailing my own meeting here, sorry about that) 18:17:53 kohsuke oleg-nenashev : Perhaps we should have a meeting/thread to discuss how to do JEP-200 level changes better 18:17:56 in the future. 18:18:06 At least capture lessons learned. 18:18:07 I am going to start a post-mortem 18:18:23 But yes, we can do a meeting 18:18:40 It's my action item for the next weeks 18:18:49 great 18:18:58 So far it's not nearly a "post-mortem" :D 18:19:00 anything else, or shall we move on? 18:19:09 +1 18:19:13 bitwiseman: +1 18:19:19 oleg-nenashev: Zombie 18:19:20 "semantic versions" +1 18:19:51 #topic GSoC update 18:19:56 oleg-nenashev also yours 18:20:00 ooh 18:20:09 #info GSoC Student application period is over. More info about GSoC: https://jenkins.io/projects/gsoc/ 18:20:11 heh 18:20:14 busy day for oleg-nenashev 18:20:15 :) 18:20:23 #info We got 15 finalized proposals which passed initial filters (eligibility, draft state, etc.) 18:20:49 15?! 18:20:52 It's significantly less than in 2016, but there are multiple reasons for that. Both internal and external factors 18:21:10 to clarify, are there 15 _good_ proposals? 18:21:23 or are there 15 proposals that were successfully submitted? 18:21:27 We have been engaged by ~40 students 18:21:45 15 proposals which passed initial filters 18:21:59 Number of good proposals... ehm... is less 18:22:19 But we definitely have good proposals and mentors for several projects 18:22:28 #info GSoC org admins and mentors are reviewing proposals. Final list of student projects will be announced on April 23 18:22:37 So yeah, for the next month it will be pretty silent 18:22:55 how many slots are we asking for? That's now, right? 18:22:56 If you are tired about the GSoC spam in the dev lists, sorry 18:23:12 it's not spam 18:23:28 #info Deadline for project slots request is April 8. Number of slots - TBD 18:24:45 oleg-nenashev thanks 18:25:02 batmat +1 I'd be happy to unsubscribe anyone who complains 18:25:05 Anyway, anybody in this chat is welcome to contribute to GSoC in 2019 18:25:20 We lack active mentors, and it hammers GSoC activity a lot 18:25:44 Obviously, I do not grumble. It is a significant commitment 18:26:33 again, thanks for handling this oleg-nenashev, I can't even imagine the time commitment 18:26:40 If there are any questions, I am ready to answer 18:26:54 Kudos oleg-nenashev 18:27:00 danielbeck: Actually not *that* much for GSoC 18:27:22 This year I was reusing docs mostly. But communications soak a lot of time 18:27:33 Thanks a lot to martinda for sharing the load 18:27:40 And to schristou 18:28:29 OK, seems that's it 18:28:37 thanks oleg-nenashev for the update 18:28:46 #topic next meeting 18:28:59 April 11, same time same channel 18:29:03 \o/ 18:29:11 thanks everyone! 18:29:14 #endmeeting