18:02:17 #startmeeting 18:02:17 Let the Jenkins meeting commence! 18:02:32 #chair hare_brain abayer rtyler 18:02:32 Current chairs: abayer hare_brain kohsuke rtyler 18:02:41 #info https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-October17thMeeting 18:02:54 #topic recap of actions 18:03:16 #info https://issues.jenkins-ci.org/browse/MEETING 18:03:16 Sorry if this isn't the right place to be asking this, but is there any way of applying a filter to the job log? We have tons of branches at the moment and it would be nice if the first page or two of every build wasn't just a bunch of "Seen branch in repository ..." lines. Is this currently possible? 18:03:55 faulkner: meeting in session --- let's do that later 18:04:23 I guess I need to deliver FreedomSponsor guest post 18:04:29 I'll do that 18:04:32 and before I forget 18:04:46 #action kohsuke to finish up the jenkinsci-cert@googlegroups.com setup and initial additions 18:05:10 #topic Picking next LTS 18:05:24 #info http://jenkins-ci.org/changelog 18:05:45 any suggestions? 18:05:48 the context for those who are new: it's about time we decide the next base release for LTS 18:06:07 let's see here 18:06:18 Last week, someone came here into the channel was was campaigning for a version that has the lazy loading feature. 18:06:21 I forget who that was. 18:06:34 It's still probably too new 18:06:42 I would agree. 18:06:51 +1 18:06:52 I know 1.485 was pretty bad, while 1.486 is good, that's the very latest 18:06:57 hm, I would prefere not to incelude lazy loading (howver it's greate feature) 18:07:18 then there's aheritier's pet peeve Maven bug that we probably need to avoid 18:07:19 I think 1.486 still has a few lazy loading related issues in it. 18:07:32 oldelvet: OK. I should do a sweep 18:07:39 We've been using 1.475 here with no problems 18:07:56 1.471 also looks like it's got very good community ratings 18:08:00 aheritier's pet peeve problem crept in in 1.481 18:08:50 1.466 to 1.471 isn't much of a jump 18:08:58 isn't 1.471 too close to 1.466 (current LTS)? 18:08:58 1.486 seemed to have some fairly weird build cause messages as well (builds that didn't relate to current were shown in addition to actual cause) 18:09:19 nanonyme: if you can file a ticket about that, that'd be good 18:09:20 We can find a more recent release. I was just giving data points. 18:09:22 Project jenkins_main_trunk build #2012: SUCCESS in 47 min: http://ci.jenkins-ci.org/job/jenkins_main_trunk/2012/ 18:09:22 * Jesse Glick: [FIXED JENKINS-15426] Run animal-sniffer:check by default (-DskipTests suppresses). 18:09:23 * Jesse Glick: Miscellaneous POM warnings. 18:09:25 JENKINS-15426:Run animal-sniffer:check as part of build (Resolved) http://jenkins-ci.org/issue/15426 18:09:46 what about 1.480? 18:10:37 interestingly 1.479 has a better rating but I agree that 1.480 should be more stable than 1.479 18:10:51 Yeah I was going to say the same thing. 18:11:00 Either 1.479 or 1.480 seem OK to me. 18:11:21 (Said without any experience with either version.) 18:11:32 Let's do 1.480 18:11:38 +1 18:11:43 the behaviour.js fix is kind of important 18:12:11 vjuranek: what's the time frame for a release? 18:12:55 kohsuke: let's say 3 weeks? (I'm quite bussy past few months:-() 18:12:55 RC by the next Wed and two more weeks to release? 18:13:02 yes 18:13:04 I guess we agreed 18:13:23 #agreed next LTS will be based on 1.480 18:13:34 * vjuranek needs to implement more selenium tests to speed up testin :-( 18:13:49 #agreed the goal is to get to RC by next Wed and 2 more weeks for a release 18:14:10 Yes, let's push that ball rolling a bit more 18:14:45 #info there's http://github.com/jenkinsci/selenium-tests that we are trying to improve as the blackbox integration test. soliciting more volunteers 18:15:01 the quality came high on the survey's intermediate result, too 18:15:14 moving on... 18:15:29 #topic Advertising survey on http://jenkins-ci.org/ 18:15:50 lisa wanted me to advertise the Jenkins survey a bit more, which runs until the end of October, I believe 18:16:13 #info jenkins-ci.org/survey 18:16:52 I'm very happy to put the banner in but because I didn't want to do it unilaterally 18:17:17 I'd like to get the sense of how people feel about it 18:17:48 as the results will be sgared with community, I don't see any problem here... btw: was is announced on mailing lists? (if yes, I completely missed it) 18:18:10 yes, the result will be shared like the last year 18:18:22 #action kohsuke to send in the survey announcement in e-mail 18:18:41 kohsuke, vjuranek hi, did you ever think about isolations during builds in jenkins? 18:19:12 hare_brain: abayer: any thought? 18:19:17 kohsuke were you thinking about a banner on the jenkins-ci.org home page? 18:19:26 yes, just like JUC banner 18:19:35 question: i have a junit running in jenkins but the stdout for a particular test seems to encompass the entire test suite. any idea why this is the case (expected?). 18:19:37 Sorry, distracted - fine by me. 18:19:53 KostyaSha: cheezey: meeting in session, please postpone those Qs until after the meeting 18:20:03 Fine by me. I was just thinking about what's the most effective place to show the banner. 18:20:06 oh, sorry 18:20:18 OK, I think I'll add it then 18:20:43 #agreed people see no problem adding a banner to the http://jenkins-ci.org/ page, 18:20:50 #action kohsuke to add it until the end of October 18:21:01 I've already forgotten what the JUC banner looked like. Did that show up on wiki and jira as well, or just on jenkins-ci.org home? 18:21:20 hare_brain: it was on all 3 places 18:21:36 OK. So you'll put it on all three for this as well? 18:21:54 If I may, sure! 18:22:03 I think I'll add a smaller one this time that's not too tall 18:22:45 If the goal is to maximize the chances of getting responses, I think wiki and jira probably get more visitors than the home page. 18:22:56 change log, too. 18:23:12 yes, and people using Jenkins for a while (whom we want to hear from) would most likely go there 18:23:31 #action kohsuke to add a banner to http://jenkins-ci.org/, wiki, and issues 18:23:43 hehe, yeah. harly a day goes by that I wouldn't study the changelogs ;) 18:24:04 #topic next meeting 18:24:27 Halloween! 18:24:40 Is it a holiday in the US? 18:24:41 fyi, I'll be on an airplane for the next meeting, but given how distracted I was this time, that's probably ok. =) 18:24:50 Well, it's not a day off. 18:25:23 OK, then I think we can still do one in 2 weeks 18:25:24 I'm sure kids would want to be able to collect (and eat) candy all day. 18:25:30 +1 18:25:48 #agreed next meeting will be in 2 weeks, the same time 18:25:53 abayer: where are you heading to? 18:26:05 JenkinsSurvey has difficult questions... 18:26:23 abayer: maybe you need a CIA post + T-shirt + stickers? 18:26:35 in any case, I think that's it for today 18:26:44 I'll be on my way back from the trip I leave on this Saturday - Berlin for a few days, then Bulgaria for Java2Days (and my Jenkins Power Tools talk, which will also go up on youtube) and then back to Berlin for a couple more days, and then home. 18:26:45 unless anyone else wants to bring up anything 18:26:49 Wow, I think that's a record for quickest meeting. 18:26:53 heh 18:27:06 #endmeeting