18:00:47 #startmeeting 18:00:47 Let the Jenkins meeting commence! 18:01:12 #topic really just wanted to check the LTS status 18:02:04 OK, so there's one regression reported from James 18:02:31 the test graph? 18:02:42 JENKINS-25340? 18:02:44 JENKINS-25340:lost trend history after skipping build (Reopened) https://issues.jenkins-ci.org/browse/JENKINS-25340 18:05:52 Yes, JENKINS-25340 18:05:54 JENKINS-25340:lost trend history after skipping build (Reopened) https://issues.jenkins-ci.org/browse/JENKINS-25340 18:06:08 in 1.580.1 that's already in junit plugin, so shouldn't matter 18:06:25 it's a regular change that went into 1.576 as JENKINS-23945 18:06:26 JENKINS-23945:Test result trend breaks lazy-loading (Resolved) https://issues.jenkins-ci.org/browse/JENKINS-23945 18:06:44 Right, yes, I agree with jglick 18:07:33 Agree about what? 18:08:01 "No plans to fix until core provides a safer way of looking for builds by number."? 18:08:24 Or that we do not care about it in the context of LTS because it is in a plugin? 18:08:25 That the fix is in the plugin, so it shouldn't block the release 18:09:12 agreed 18:09:26 ogondza: actually, I see that the email was sent yesterday that we started RC testing 18:09:37 I guess it means we are slipping 2 weeks? 18:10:20 kohsuke: I have enough time to do my part anyway. Do not think it is necessary 18:10:58 kohsuke you emailed the dev list on the 19th, do you think anyone's waiting for ogondza to announce start of testing? 18:11:17 OK, sounds like I'm hearing we can ship today as planned? 18:11:39 danielbeck: yeah sorry, forgot to send it on time 18:12:25 kohsuke: I believe so, also in ATH looks good aside of JENKINS-25264 18:12:27 JENKINS-25264:Scriptler add script fails with java.io.IOException: failed to update git repo (Open) https://issues.jenkins-ci.org/browse/JENKINS-25264 18:13:02 #agreed 1.580.1 release today 18:13:15 I got some work to do in that case! 18:13:40 That's all I wanted to cover today 18:13:44 Should we just wrap this up? 18:14:52 #topic next meeting 18:15:11 There was (another) discussion about the usefulness of weekly RCs. 18:15:33 #info Nov 12th, same time (pegged to US time zone, so watch out for the change in your local time zone) 18:16:10 I'm doing this from a meeting, so I don't have bandwidth today to do it 18:16:28 I'll plan that for the next governance meeting 18:16:59 well, add a line to the agenda page :-) 18:17:09 Thanks 18:17:11 #endmeeting