17:00:00 <djmitche> #startmeeting weekly
17:00:00 <bb-supy> Meeting started Tue Dec 18 17:00:00 2018 UTC and is due to finish in 60 minutes.  The chair is djmitche. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:00 <bb-supy> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:00 <bb-supy> The meeting name has been set to 'weekly'
17:00:05 <djmitche> nailed it! :)
17:00:08 <djmitche> #topic Introduction
17:00:13 <djmitche> http://bit.ly/2rup31x
17:00:15 <tardyp> hi
17:00:17 <djmitche> Anyone is welcome to speak
17:00:18 <djmitche> hi!
17:00:20 <rjarry> hi
17:00:26 <djmitche> there's a hard 30-minute time limit
17:00:28 <djmitche> hi rjarry!
17:00:40 <djmitche> anyone else around?
17:01:11 <djmitche> ok
17:01:15 <djmitche> #topic Week in Review
17:01:19 <djmitche> what's new and exciting?
17:03:12 <bdbaddog> Hi!
17:03:43 <djmitche> hi!
17:03:51 <djmitche> tardyp: ^^ new? exciting?
17:04:04 <tardyp> sorry for delay. was interrupted
17:04:20 <tardyp> the news from the week is buildbot.buildbot.net back onlune
17:04:29 <tardyp> and on python3 with buildbot 1.6+
17:04:36 <djmitche> nice!
17:04:49 <tardyp> this is for preparation of the 1.7 release with python2 being deprecated
17:04:58 <djmitche> #info Metabuildbot (https://buildbot.buildbot.net/) is back online, now using python3
17:05:11 <djmitche> I saw some PRs about the deprecation -- have those landed?
17:05:12 <tardyp> I wanted to release this weekend, but there are still some PRs which need to be taken care of.
17:05:59 <djmitche> #info Python-2 deprecation PRs have been merged; release coming soon
17:06:29 <djmitche> skelly: you around? any updates?
17:07:15 <bdbaddog> Be curious how much pushback when people start installing new release with deprecation notices..
17:08:28 <djmitche> yeah
17:09:01 <djmitche> well, that sort of covers the noted topics..
17:09:54 <tardyp> the deprecation PRs, sill have issues with unit tests
17:10:06 <djmitche> oh, interesteing
17:10:07 <tardyp> and we have a regression in the e2e rjarry was talking about
17:10:29 <tardyp> those are very old tests which test exactly the output of stoud
17:10:40 <tardyp> so as soon as you add something they all fail
17:10:48 <rjarry> :D
17:10:56 <bdbaddog> do the deprecations go to stdout or stderr?
17:11:12 <rjarry> in the logs I guess
17:11:12 <tardyp> stdout
17:11:14 <djmitche> #info deprecations are causing a few smoke / e2e test failures that need to be cleaned up first
17:11:22 <tardyp> no its in the stdout of buildbot start
17:11:27 <rjarry> ah ok
17:11:39 <tardyp> they need to be seen. nobody looks at the logs
17:11:55 <rjarry> yep, maybe better to print them on stderr
17:12:26 <tardyp> I still can do that
17:12:35 <bdbaddog> Plus would that fix the tests? ;)
17:12:52 <rjarry> sur un malentendu :)
17:13:01 <rjarry> (don't know how to say that in english)
17:13:34 <djmitche> neither do I :)
17:13:36 <tardyp> well, the tests test stdout and stderr
17:14:00 <rjarry> arf
17:15:20 <djmitche> sounds like that's proceeding anyway.. shall I wrap the meeting up?
17:15:39 <bdbaddog> +1
17:15:42 <rjarry> +1
17:15:49 <tardyp> yep
17:15:52 <bdbaddog> btw.. the weekly emails are still showing up as spam.
17:16:42 <rjarry> cheers all
17:16:58 <djmitche> bdbaddog: yeah, I think that's a symptom of running our own mail server
17:17:03 <djmitche> not sure how to fix that
17:17:06 <djmitche> cheers!
17:17:08 <djmitche> #endmeeting