16:05:50 <tardyp> #startmeeting weekly
16:05:50 <bb-supy> Meeting started Tue May 23 16:05:50 2017 UTC and is due to finish in 60 minutes.  The chair is tardyp. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:05:50 <bb-supy> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:05:50 <bb-supy> The meeting name has been set to 'weekly'
16:05:56 <tardyp> anybody here?
16:06:00 <bdbaddog> Here
16:06:09 <tardyp> djmitche: is on a flight today
16:06:21 <bdbaddog> that's usually my line.. ;)
16:07:39 <tardyp> so this will be a very light meeting then
16:07:41 <tardyp> https://titanpad.com/buildbot-agenda
16:07:49 <tardyp> #topic week in review
16:08:18 <tardyp> the big story of the week if a number of regressions due to updating dependencies
16:08:41 <tardyp> #info moving buildbot project to pyup.io
16:09:10 <tardyp> so that we can have the time to fix issues without rushing into workarounds
16:09:43 <tardyp> big pylint update patch https://github.com/buildbot/buildbot/pull/3251
16:09:53 <tardyp> to keep up with latest pylint version
16:10:06 <tardyp> any suggestion?
16:10:44 <tardyp> also pylint builds start to crash because the exceed the 1GB limit of the docker containers https://github.com/PyCQA/pylint/issues/1495
16:10:53 <bdbaddog> So the idea is to automatically upgrade all pacakges?
16:11:07 <tardyp> it is to upgrade the package via PR
16:11:12 <tardyp> so that other PRs are not impacted
16:11:31 <tardyp> previously we just ran on tip, and we had to quickly fix and relaunch PRs when there are issues
16:11:52 <tardyp> now if there is a problem it can be taken in account via the PR
16:12:19 <tardyp> pyup is creating a branch in main buildbot repo, and maintainers can ammend that branch to fix the compat issues
16:12:29 <bdbaddog> gotcha.
16:12:39 <tardyp> #topic releases
16:12:44 <bdbaddog> does it take into account dependencies of the various packages?
16:12:49 <tardyp> #undo
16:12:49 <bb-supy> Removing item from minutes: <ircmeeting.items.Topic object at 0x806961350>
16:13:16 <tardyp> you have to maintain a requirements.txt with all deps of deps inside
16:13:37 <tardyp> eventually I need to move to requirements.in, so that we can have deps of deps managed automatically
16:14:05 <tardyp> eve has a nice way of doing this: https://bitbucket.org/scality/eve/src/9f796833b0f1840c985fa319dac027057b683db0/requirements/?at=development/1.2
16:14:32 <tardyp> #topic release
16:14:36 <tardyp> no release planned this week
16:14:46 <tardyp> any other topic?
16:14:53 <skelly> nothing from me
16:15:27 <tardyp> ok then lets wrap up!
16:15:34 <tardyp> #endmeeting