18:01:26 #startmeeting 18:01:26 Let the Jenkins meeting commence! 18:01:32 #chair kohsuke danielbeck hare_brain 18:01:32 Current chairs: danielbeck hare_brain kohsuke rtyler 18:01:51 Hmm, https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda is empty 18:01:54 #topic Last meeting actions 18:02:02 yep, so we'll do the usual real quick 18:02:07 sounds good 18:02:15 the only action was the release 2.19.2 18:02:16 #info http://meetings.jenkins-ci.org/jenkins-meeting/2016/jenkins-meeting.2016-10-26-18.00.html 18:02:18 which happened yeah? 18:02:24 yep 18:02:31 \o/ 18:02:37 moving on then :D 18:02:42 #topic LTS status check 18:03:05 ogondza isn't around 18:03:13 ruh roh 18:04:08 well.. 18:04:16 danielbeck: do you know anything about where we are? 18:04:21 backporting started for .3 didn't it? 18:04:31 fairly active at https://groups.google.com/d/msg/jenkinsci-dev/Ejm1LrMf4h0/Hhz9HDwnAgAJ 18:05:11 Seems there's one outstanding backport which will be included with https://github.com/jenkinsci/jenkins/pull/2627 as followup 18:05:20 Active discussion about the B.O. I18N backport last I saw. 18:05:36 oleg-nenashev: you around? 18:05:38 right 18:06:37 I suppose the status is “wrapping up”? 18:06:41 heh 18:07:00 if there's nothing that needs to be discussed here as far as the LTS for 2.19.3 is concerned, then that's no big deal IMO 18:07:05 right 18:07:32 anything else on this topic? 18:07:39 #action danielbeck to send another UTC reminder to the dev list 18:07:53 (it's not like ogondza to miss a meeting) 18:07:53 rtyler: Sorry, was offline 18:08:24 oleg-nenashev: are there any issues around the LTS that you want to raise while we're on the topic? 18:08:30 i think the RC is more or less ready. Yesterday we integrated the most of the stuff 18:08:50 The only left issue is BlueOcean localization patch 18:09:19 looking for the thread 18:09:24 I think we should move on 18:09:30 oleg-nenashev we linked that above already 18:09:41 oleg-nenashev so if that's all, we're up to date 18:09:45 nice 18:09:48 \o/ 18:09:57 JENKINS-35845 is pending, other stuff is integrated 18:10:14 I'm going to throw a heads-up topic in real quick 18:10:20 kohsuke: Maybe off-topic, but we need remoting-3.1 release for the next LTS 18:10:27 oleg-nenashev: already done 18:10:30 ty 18:10:36 #topic Some release archives served via Azure blob storage 18:10:49 this is just a heads-up for posterity to be honest 18:11:08 #info right no we're seving HTTPs downloads for pkg.jenkins.io for debian/opensuse/redhat repositories via Azure blob storage 18:11:30 So long as there are backups elsewhere, sounds fine. 18:11:33 we're not fronting any more traffic via Azure right now just because I don't have enough data on whether it's been successful thus far or not 18:11:45 what defines success? 18:12:00 lack of complaints :P 18:12:13 well, also there are Azure metrics which show less than 100^ deliverability success rates 18:12:27 I have a support call with Microsoft tomorrow to ask more about what that metric means 18:12:46 if they're just tracking clients' connection resets, then that's not a concern 18:13:05 jglick: Azure blob storage is geographically redundant 18:13:55 danielbeck: I'm also using this experiment to get an idea of whether my cost models are correct 18:14:30 but please keep an eye out for IRC, mailing list, or twitter traffic which might suggest end-users are seeing anything other than stellar experiences with these downloads 18:14:48 any questions befoer moving on? 18:14:55 no 18:15:20 #topic Next meeting 18:15:43 Nov 23rd is the week of thanksgiving in the US 18:15:55 not a big deal, but there might be a fair bit of vacations floating around then 18:16:00 any qualms with that day? 18:16:11 not from me but we could ask on the dev list 18:16:30 * oleg-nenashev is out on 23rd 18:16:33 considering t he agenda for the past two meetings, I don't think we should skip 18:16:39 FWIW 23rd is LTS baseline selection 18:16:42 it'll likely be quick 18:16:53 yes, we need it 18:16:53 LTS baseline selection! 18:16:55 Let's stick to the schedule 18:17:09 okay 18:17:17 #info next meeting Nov 23rd 18:17:21 #endmeeting