18:02:41 #startmeeting 18:02:41 Let the Jenkins meeting commence! 18:02:44 #chair rtyler kohsuke 18:02:44 Current chairs: danielbeck kohsuke rtyler 18:02:55 #info https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda 18:03:08 well, https://wiki.jenkins.io/display/JENKINS/Governance+Meeting+Agenda?nocache 18:03:25 sorry danielbeck, bouncing between all the tabs :) 18:03:29 #topic Recap last meeting's actions 18:03:41 * rtyler was dealing with an alert 18:03:44 #info http://meetings.jenkins-ci.org/jenkins-meeting/2018/jenkins-meeting.2018-02-14-18.00.html 18:03:56 oleg-nenashev two actions from you…? 18:04:15 Blogpost - done 18:04:24 Jumbotron - decided not to do that 18:04:41 okay, great 18:04:46 #topic LTS status check 18:04:50 ogondza around? 18:05:05 * rtyler puts on his flame retardant suit 18:05:07 right 18:05:25 there were a discussion around reverting from 2.107 18:05:33 or whether we should continue as suggested 18:05:40 #info https://groups.google.com/d/msg/jenkinsci-dev/7nR0_kI71xA/TNrMNVlmAAAJ 18:06:00 no consensus, though most people felt for not-reverting 18:06:02 I'd guess I am the only one who voted for fallback to 2.104 18:06:15 oleg-nenashev, yes. and it is perfectly fine 18:06:17 So likely there is a consensus 18:06:21 ack 18:06:32 just not enough to investigate from the reporters :( 18:06:33 I am fine with 2.107 since others vote for that 18:06:51 https://issues.jenkins-ci.org/browse/JENKINS-49543 was backported on the last moment 18:06:57 danielbeck, WDYM? 18:07:04 markewaite: you have done some poking lately too haven't you? 18:07:22 ogondza I checked some of the issues oleg-nenashev was concerned about but not enough information to investigate further 18:07:37 For the record, I am still concerned about landing JEP-200 and XML 1.1 at once. OTOH we need a PLEASE DO BACKUP in guidelines anyway 18:08:08 ogondza JENKINS-49498 :) 18:08:08 right, for me this is a signal for next LTS baseline check as the extra soaking time would make this a lot easier 18:08:20 s/check/selection/ 18:09:03 rtyler Yes, I've been running 2.107 in my test environment since the day it was selected as the version for the release candidate. No failures that I detected. 18:09:13 ogondza: Have you integrated my ping about JENKINS-49543? 18:09:27 so, the tests are running with JENKINS-49543 in 18:09:31 oleg-nenashev, ^ 18:09:38 thanks! 18:09:52 unless it blows up, the (real) rc will be pushed tomorrow 18:09:58 oops, wrong link -- it's pretty minor but JENKINS-49387 seems irritating and simple 18:10:27 Would be great to port JENKINS-49788 just in case, but I am fine if it waits till .2 18:10:44 Could we finally add jenkins-admin to this chat? :) 18:11:30 49388 is lacking urgency IMO 18:11:30 JENKINS-49387 porting would be great for sure 18:11:48 49387 is a very visible and confusing UI regression 18:12:07 agreed JENKINS-49387 seem trivial 18:13:13 so I will add that and _then_ it will be it 18:13:24 looking over the rest of https://issues.jenkins-ci.org/issues/?jql=labels %3D lts-candidate there's plenty that looks useful, but nothing that needs last minute inclusion 18:13:38 ogondza +1 18:14:05 alright, I am done 18:14:10 \o/ 18:14:14 the reporter was grumbling that JENKINS-49498 is a security issue. I do not care much 18:14:20 bitwiseman: you may want to consider some blogging effort around the next LTWS 18:14:23 LTS* rather 18:14:29 oleg-nenashev it's been in there forever so ¯\_(ツ)_/¯ 18:14:49 not great but a good .2 candidate IMO 18:14:58 fine with me 18:15:24 rtyler: giving a bump to JEP-200 and XML 1.1 change awareness. 18:15:37 rtyler: Maybe I will set up a JOM about JEP-200 next week. TBD 18:16:12 anything else on LTS status? 18:16:18 oleg-nenashev: if you wish to do a screencast, that's also something easy to arrange and embed in a blog post 18:16:36 What is ETA of upgrade guideliness PR? 18:16:41 danielbeck: ^^ 18:16:53 before release? 18:16:56 as usual 18:17:31 Would be nice to have them with 2-day advance so that I could review JEP-200 side carefully 18:17:35 right 18:17:37 got it 18:17:44 Though probably I should write that section :D 18:17:59 #action danielbeck to write upgrade guide and publish PR on Monday before release for oleg-nenashev to review 18:18:14 rtyler: Yeah, makes sense 18:18:54 can we move on? 18:19:01 * oleg-nenashev wanted to write a JEP-200 post as well, but he probably needs to finish the FKA "January Remoting Update" blog-post 18:19:09 yes, let's go 18:19:10 moving on 18:19:20 #topic next meeting 18:19:28 #action: oleg_nenashev to prepare a screencast about JEP-200 18:19:33 Mar 14 18:19:56 woop 18:20:00 beware the ides of march 18:20:12 #endmeeting