18:00:08 #startmeeting 18:00:08 Let the Jenkins meeting commence! 18:00:19 #chair danielbeck kohsuke 18:00:19 Current chairs: danielbeck kohsuke rtyler 18:00:26 #topic Last meeting actions 18:00:31 http://meetings.jenkins-ci.org/jenkins-meeting/2018/jenkins-meeting.2018-02-28-18.02.html 18:00:45 danielbeck and oleg-nenashev are the only ones with an action from last time around 18:01:35 * rtyler waits for our friends in the .eu to wake up 18:01:36 :) 18:01:42 hello 18:01:48 #info https://www.youtube.com/watch?v=Vfnc9t1RuYA - screencast about JEP-200, kudos to bitwiseman and jglick 18:02:24 Youtube always chooses Chuck Norris for the landing image 18:02:41 o_O 18:03:21 anything else on this oleg-nenashev ? 18:03:41 #info 2.107.1 upgrade guide is in place: https://jenkins.io/doc/upgrade-guide/2.107/#upgrading-to-jenkins-lts-2-107-1 (danielbeck's action item) 18:03:47 that's it from me 18:04:10 would appreciate reviews of https://github.com/jenkins-infra/jenkins.io/pull/1448 though 18:05:22 okay, I don't think there are any other last meeting actions we need to cover 18:05:29 ogondza: are you with us this fine afternoon? 18:05:37 rtyler, sure 18:05:45 wunderbar 18:05:51 #topic LTS status check 18:05:54 the floor is yours ogondza 18:06:20 most of the testing was done internally 18:06:31 public ci is getting less and less stable 18:06:43 this is ci.jenkins.io? 18:07:02 rtyler, there is not LTS test there yet 18:07:15 jenkins.ci.cloudbees.com 18:07:31 oh, well that's not surprising to me then :P 18:07:36 ogondza: is that public? 18:07:40 No notable regressions reported 18:07:44 ogondza: do you have any tickets floating around INFRA for moving that workload over to ci.jenkins.io 18:07:55 rtyler, not that ci.jenkins.io would be any more stable for ATH :P 18:07:56 bitwiseman: yes, that's an old DEV@Cloud instance that CloudBees provisioned for us once upon a time 18:08:10 0_o 18:08:13 ogondza: raul just did a tremendous amount of work to make sure that we can get at least the smoke suite stable and running for PRs 18:08:38 ogondza: I guess my point is, what can I do to help you forget jenkins.ci.cloudbees.com forever and ever :) 18:08:54 (into the mists of time) 18:09:00 rtyler, lets track this and have a look offline 18:09:07 okie doke 18:09:21 aside from that, I guess we are ok to go 18:09:26 #action rtyler to follow up with ogondza about migrating LTS testing into ci.jenkins.io 18:09:53 the serialization fix James requested was not integrated into .1 as it was not merged in time 18:09:55 We have some unresolved regressions, but the upgrade guidelines include the "Known issues" section, to be extended 18:09:56 for my own remembering what's this LTS baseline again? 18:10:03 2.107.x 18:10:36 #info 2.107.1 is ready to go from ogondza's perspective 18:10:41 kohsuke, can you please cut the release? 18:11:00 he's unfortunately in a meeting conflict right now (I am in the same office and can hear him through the wall) 18:11:08 #action kohsuke to cut the 2.107.1 release 18:11:16 that should do it, thanks 18:11:35 anything else we should cover on this topic ogondza? 18:11:44 rtyler, nothing I know of 18:12:02 oleg-nenashev: who typically writes the upgrade guidelines, danielbeck? 18:12:08 yes 18:12:09 yes 18:12:39 oleg-nenashev: can I ask you to sync with danielbeck to make sure the upgrade guidelines for 2.107.1 includes the known issues for changes which didn't make the train? 18:13:02 rtyler: Yes, we will update the page 18:13:28 okie doke, thakns 18:13:57 moving on then 18:14:10 #topic Trademark sublicensing request "CloudBees Jenkins Metrics" 18:14:21 #info context for the request https://groups.google.com/forum/#!msg/jenkinsci-dev/7m9bz6KkVv4/gd8qhk6cAQAJ 18:14:47 at a high level, a feature/product thingie that cloudbees does used to be called CloudBees Jenkins Analytics 18:14:59 they're now wishing to rename/change the product and call it "CloudBees Jenkins Metrics" 18:16:02 #info previously accepted sublicense requests can be found here: https://wiki.jenkins.io/display/JENKINS/Approved+Trademark+Usage 18:16:34 any questions, thoughts, opinions? 18:17:14 There was general agreement on that email thread. 18:17:31 My comments are in the mailing list. I see no serious obstacles for such requests 18:18:37 * rtyler nods 18:18:57 There was a concern about overlap with the existing Metrics Plugin, but the plugin maintainer is fine + the requester is going to work on disambiguation. No other major concerns in the list 18:19:29 * rtyler nods 18:19:50 this all feels fairly rote and boring to me, so let me ask this differently 18:19:54 are there any objections? 18:20:36 * rtyler will give it a couple minutes just to be sure 18:22:13 +1 here 18:22:45 +1 from me as well 18:23:16 * rtyler yawns loudly 18:24:07 #info CloudBees is expected to follow and enforce the appropriate trademark attribution policies for sublicenses https://jenkins.io/project/governance/#trademark-attribution 18:24:16 (same with everybody else) 18:24:25 yup 18:24:43 considering the general agreement on the thread, and lack of disagreement/concerns here.. 18:25:00 #agreed CloudBees granted a trademark sublicense for "CloudBees Jenkins Metrics" 18:25:11 * rtyler can never remember if it's agreed or agree 18:25:25 #topic Next meeting 18:25:30 * rtyler consults the calendar 18:25:48 Looks like March 28th is the next scheduled meeting 18:25:53 which will still be scheduled at 18:00 UTC 18:26:03 I don't know if europe messes with their clocks before then or not 18:26:15 #info next meeting March 28th at 18:00 UTC 18:26:20 anything else before we wrap? 18:26:46 #endmeeting