18:02:32 #startmeeting 18:02:32 Let the Jenkins meeting commence! 18:02:48 #chair kohsuke danielbeck hare_brain 18:02:48 Current chairs: danielbeck hare_brain kohsuke rtyler 18:03:10 kohsuke: my wifi is going on slow motion right now, can you run? 18:03:21 Yeah 18:03:31 #topic Recap last meeting's actions 18:03:34 Let's see 18:03:42 #info http://meetings.jenkins-ci.org/jenkins-meeting/2017/jenkins-meeting.2017-03-15-18.00.html 18:04:15 hare_brain won't be joining us, he's got a meeting conflict fwiw 18:04:19 I added the approved trademarks 18:04:20 There's a bunch of sublicense related actions for danielbeck and allengeer 18:04:25 I added some clear trademark attribution guidelines to the site: https://jenkins.io/project/governance/#trademark 18:04:26 oops, not allengeer but alyssa 18:04:48 pretty much copy and pasted linux foundation's which we defer to 18:04:49 lol im like why is kohsuke talking about me :) 18:04:52 (they can hire lawyers) 18:05:00 my AIs are complete 18:05:05 allengeer: my bad! 18:05:22 allengeer: omg you're in trouble xD 18:05:24 my AIs are too 18:05:47 lars added the necessary attribution on the day of jenkins site iirc 18:05:51 larkruzz is not here, so I guess we should check code conf site quickly 18:05:52 I'm pretty sure I saw that yesterday 18:05:54 OK, great 18:06:08 And alyssat_ is here 18:06:16 i'm here. 18:06:27 we were going through actions you took 2 weeks ago 18:06:30 See http://meetings.jenkins-ci.org/jenkins-meeting/2017/jenkins-meeting.2017-03-15-18.00.html 18:06:50 I'm pretty sure that's what alyssat_ was referring to earlier kohsuke 18:06:50 my AIs are complete. Attributions has been added to proper events pages as well as CB pages 18:07:01 oh 18:07:12 sorry, in my IRC client today you two have the same color 18:07:22 I got that confused with your AIs, rtyler 18:07:35 Now that it's cleared, I think we are good on this 18:07:35 are we blue? 18:07:42 You two are teal 18:07:43 perhaps n azure color 18:07:47 heh 18:07:53 I think that's all the actions from last time 18:07:56 i'm dark blue 18:08:01 emerald green, my favorite color for my favorite people 18:08:07 \o/ 18:08:13 #topic LTS Status check 18:08:23 ogondza 18:08:37 no problem during testing, we are ready to go 18:08:49 great 18:08:50 #action kohsuke to run a release 18:08:57 #action danielbeck to write the upgrade guide 18:08:59 oleg-nenashev: are you ok with https://github.com/jenkins-infra/jenkins.io/pull/764 ? 18:09:17 this is 2.46.1 yeah? 18:09:18 ogondza oleg-nenashev That's best discussed elsewhere 18:09:33 rtyler: yes 18:09:40 #action danielbeck to merge the update center PR for the new baseline once Artifactory index has 2.46.1 18:09:52 kdanithat PR would be a prerequisite to kohsuke running a release though wouldn't it? 18:09:55 omg lag 18:10:03 danielbeck: ^ 18:10:15 who's kdanithat? 18:10:15 rtyler I don't understand the question 18:10:33 oh, it must be "k, daniel, that PR would be ..." 18:10:38 indeed 18:10:46 rtyler which PR? changelog? 18:10:46 that jenkins.io pull request is the changelog isn't it 18:10:57 souldn't that be ready to merge before kohsuke runs the release process? 18:11:14 we have an hour or four, it's fine 18:11:19 I don't think it's a pre-req, yeah 18:11:20 heh 18:11:25 Artifactory is acting up lately wrt indexing 18:11:30 there is no techincal reason I know off 18:11:36 as a user it sucks to have new bits without knowing what they are :) 18:11:44 rtyler don't install them thren 18:11:49 s/thren/sthen 18:11:53 o_o 18:11:55 s/sthen/then 18:11:59 danielbeck: let me try this differently 18:12:06 I assume danielbeck is saying this PR will get sorted out by the time release arrives 18:12:10 yes 18:12:14 people ask @jenkinsci and jump into #jenkins whenever the changelog doesn't exist for the latest listed release 18:12:17 I would like to avoid that 18:12:35 I'll take care of it 18:12:40 kohsuke: heh, basically we're counting on you not releasing until later tonight I presume? :P 18:12:45 "after work" work 18:12:46 :D 18:13:03 Well, there might a bit of that, but we are counting on the time the release process itself takes, plus Artifactory indexing delay 18:13:23 I think we are all happy now, let's move on 18:13:38 sure 18:13:42 #topic Sublicense request, on behalf of JFrog, "Jenkins Community Day" event in Paris 18:13:55 JFrog is planning to host a Jenkins 1 day event w/ 4-6 sessions in Paris on July 11. They are requesting for approval to use the name "Jenkins Community Day". They hope to get 250-300 attendees. Entry price is $50, this is mainly to make sure those who RSVP actually do attend and also to cover food & drinks since we all know how expensive everything is in 18:13:55 Paris. 18:14:18 heh 18:14:23 quiche for everybody! 18:14:34 Between this and the last meeting, IMO it's great that more companies are organizing different events 18:14:35 and croissants :) 18:14:39 alyssat_: are you here asking on behalf of JFrog? 18:14:53 yes. I am here on behalf of JFrog 18:14:53 and french fries 18:14:59 * batmat switches from screen to screen and wondered a few seconds if that was the right one, reading French :) 18:15:01 allengeer: frites! 18:15:17 oui oui! ou est mon frites! 18:15:22 heh 18:15:23 *sont 18:15:40 "où sont mes frites" would be better 18:15:41 I'm comfortable with this request, the usual trademark attribution requirements apply of course 18:15:56 "où sont mes frites, bordel" would be even frenchier... 18:16:02 Anyone who feels otherwise? 18:16:06 yes. I will work with them to make sure proper attribution is included on the webpage 18:16:07 alyssat_: future interactions like this I hope we can encourage companies like jfrog to actually participate in this meeting similar to praqma last time around 18:16:17 batmat: stay on topic or I'll have to kick you into the sein 18:16:19 :) 18:16:35 rtyler: will do 18:16:35 +1 for JGrenouille 18:16:49 All right, moving on... 18:16:55 record it plz 18:17:02 thank you 18:17:19 Who's asking? JFrog Ltd? 18:17:26 #agreed "Jenkins Community Day" sublicense request is granted. The usual attribution apply 18:17:42 I don't know if it's Ltd or Inc or 株式会社 18:17:49 alyssat_: see danielbeck's question 18:17:59 i'm looking this up 18:18:05 I just know them as JFrog 18:18:05 danielbeck: perhaps alyssat_ can update the approved trademark page :) 18:18:15 https://www.jfrog.com/Artifactory/?km_source=google+ppc&km_medium=cpc&km_term=35774400220&km_campaign=682253752&km_keyword=jfrog&km_adid=152106653455&aw_campaignid=682253752&aw_adgroupid=35774400220&aw_device=c&aw_keyword=jfrog&aw_matchtype=e&gclid=CLDomsGp_NICFQJsfgodkMUJcw 18:18:30 #action alyssat_ to update approved trademark usage wiki page 18:18:39 kohsuke that's fine, now I don't care anymore ;-) 18:18:40 ok 18:18:41 kohsuke: /now/ I think we can go to the next topic xD 18:18:48 #action alyssat_ to remove her tail 18:18:52 haha 18:19:08 batmat: huh? 18:19:10 * rtyler thinks batmat may have had too much wine this evening 18:19:24 #topic Java 8 baseline bump heads up 18:19:33 #info a quick advertisement about a proposed Jenkins localization drive : https://groups.google.com/d/msg/jenkinsci-docs/pBn13p7FRH0/wUBgInrPBgAJ 18:19:35 oops 18:19:43 you have more topic now 18:20:02 heh 18:20:09 batmat: this is yours 18:20:10 #info https://jenkins.io/blog/2017/01/17/Jenkins-is-upgrading-to-Java-8/ 18:20:56 so, reminder, the /plan/ was to bump in April, so we're almost there. I've started looking into a PR for this, but this seems a bit more complicated than anticipated. 18:20:57 is everything moving along smoothly batmat? 18:21:01 #info https://github.com/jenkinsci/jenkins/pull/2802 18:21:06 any help you need from others? 18:21:13 I suspect that kohsuke could help in ^ 18:21:27 OK 18:21:42 at least, give guidance. This seems to fail in one subtool, the bridge injector 18:21:45 I offered some hints. 18:21:56 I guess the fix needed in bridge method injector 18:21:57 jglick: yup, saw it just before, thanks 18:22:12 batmat: one thing to keep in mind, we have a LOT of plugins using the buildPlugin global variable in their Jenkinsfiles now, and some are pinning to Java 7 18:22:28 batmat: if you feel like sending emails, you could ping some of those folks and let them know that the end is nigh 18:22:45 batmat unless the core dependency is updates, shouldn't matter 18:22:49 rtyler ^ 18:23:05 ok 18:23:10 rtyler: not sure I get what you mean. Anyway, I suppose this can be handled on ML or IRC, outside the gov meeting 18:23:14 rtyler or do you think plugins won't work? 18:23:34 I'm worried that plugins are explicitly avoiding testing on JDK8 for some reason that might cause breakages for users 18:23:42 it could be just laziness 18:23:56 anyway, it was mostly a heads up as stated, so I'm done. Just a FYI/reminder 18:23:56 but there are "key" plugins which are suggested in the installation process 18:23:59 Or if they know the plugin does not build on 8 then there may be something consistently broken. Anyway, that is their problem. 18:24:06 I just want us to make sure those are kosher 18:24:18 rtyler: if there are any recommended plugins which do this, either remove the pin, or drop them from the list (IMO) 18:24:19 if the PR gets mergeable soonish, then the /plan/ to have the next LTS baseline on Java 8 could still be true 18:24:40 jglick: I agree with that, I just wanted to raise it as sometihng that batmat might be able to drive resolution on 18:24:54 rtyler: ack 18:25:08 OK, sounds like the critical path is to get the jenkins.war with Java8 class files, then to do some tests 18:25:26 batmat: I'll do my part in fixing bridge method injector 18:25:39 kohsuke: would be great, thanks 18:25:43 My initial thinking is that jglick is right that it's just a metter of upgrading ASM 18:25:54 Anything more on this? 18:26:09 kohsuke: I tried it, but it's possible I missed a step. 18:26:16 nope, done from me. 18:26:16 I'll see what I find 18:26:35 #topic a quick advertisement about a proposed Jenkins localization drive 18:27:01 hope y'all find https://groups.google.com/d/msg/jenkinsci-docs/pBn13p7FRH0/wUBgInrPBgAJ interesting 18:27:03 kohsuke: would you or whomever is championing this write a blog post? 18:27:39 Sure, danielbeck, you or me? 18:27:45 rtyler we're not there yet IMO 18:27:48 okay 18:27:58 I assume the post is about "hey WDYT, anyone willing to participate?" 18:28:25 whwnever the initiative is "there" please don't hesitate to use jenkins.io as a mechanism for getting the word out 18:28:37 Will do 18:28:44 #topic next meeting time 18:29:16 #info Next meeting will be April 12th the same time. Thank god time zone change is over! 18:29:30 See you in 2 weeks 18:29:33 #endmeeting