14:01:20 <tflink> #startmeeting fedora-qadevel
14:01:20 <zodbot> Meeting started Mon Oct 12 14:01:20 2015 UTC.  The chair is tflink. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:20 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:01:21 <tflink> #meetingname fedora-qadevel
14:01:21 <tflink> #topic roll call
14:01:21 <zodbot> The meeting name has been set to 'fedora-qadevel'
14:01:27 * lbrabec is here
14:01:32 * mkrizek is here
14:02:01 * kparal is here
14:03:19 <tflink> apologies for forgetting the announcement
14:04:22 <tflink> let's get started
14:04:28 <tflink> #topic Announcements and Information
14:04:35 <tflink> #info f23 final freeze starts 2015-10-13
14:04:35 <tflink> #info gave taskotron overview talk to infra - tflink
14:04:35 <tflink> #info working towards emitting fedmsgs in stg - mkrizek
14:04:35 <tflink> #info disposable clients fixes - mkrizek
14:04:36 <tflink> #info took over splitting libtaskotron into modules - mkrizek
14:04:38 <tflink> #info runner refactoring done - lbrabec
14:04:51 <kparal> #info code reviews - kparal
14:04:55 <tflink> any additions, questions or comments?
14:05:11 <mkrizek> not here
14:05:25 <lbrabec> nope
14:06:13 <tflink> ok, moving right along to
14:06:21 <tflink> #topic disposable-develop merge timeline
14:07:17 <mkrizek> do we want to wait with merging until modularization is done?
14:07:26 <tflink> that's what I was wondering
14:07:42 <kparal> I don't think it's necessary
14:07:53 <kparal> let's create a merge diff in phab and start gathering comments
14:08:16 <tflink> it'd be nice to get rid of the 2 branches
14:08:41 <mkrizek> how do we approach the fixes in that merge review? who's going to do fixes?
14:09:01 <tflink> is there a volunteer?
14:09:14 <kparal> whoever's willing to, as usual :)
14:09:39 <mkrizek> so we create a ticket for each concern
14:09:57 <tflink> that makes as much sense as anything
14:10:15 <tflink> I was hoping that there wouldn't be many ticket-worthy merge issues, though
14:11:02 <mkrizek> I was just curious on how do we track the changes and/or how do we update the merge diff
14:11:09 <kparal> we can possibly resolves some of the tickets after the merge. but at least we'll compare the diff and figure out whether there are some concerns or not
14:11:23 <mkrizek> ok, makes sense
14:11:37 <tflink> yeah, let's see how bad it really is before we worry about the rest
14:11:46 <tflink> it might be reasonably do-able by one person
14:12:03 <kparal> I think it's fine if whoever's making some change just commandeers that revision. or if it's not critical, file in a ticket and append a diff there, can be pulled after the merge
14:12:26 <tflink> that's a good way to put it
14:12:48 <tflink> get the diff done with as few changes as required and handle any other issues separately
14:13:29 <tflink> this will be big enough that we may miss a few things on the first pass, anyways
14:13:39 <kparal> technical question - we will probably want to do a non-squash merge to preserve history, wdyt tflink?
14:13:56 <kparal> the downside is that the history will no longer be a straight line
14:14:22 <kparal> and quite a few merge commits in it too
14:14:32 <tflink> yeah, there's so much change that I'd rather not squash the history
14:14:39 <kparal> ok
14:15:01 <tflink> as much as I'm not a fan of merge commits, it'll be a bit of a necessary evil here, i think
14:15:10 <mkrizek> agreed
14:15:10 <kparal> I have no idea how bisect works in such cases, but we haven't needed it yet, so it's probably not much of a concern
14:15:54 <tflink> i think this'll be a bit of a special case
14:16:18 <tflink> unless we want to freeze develop, rebase disposable-develop and test that for a while
14:16:46 <kparal> rebasing would be a lot of work
14:17:09 <tflink> rebase/update
14:18:07 <tflink> but i don't see us doing much with the current develop anytime soon, so I'm not sure that extra effort would be worth it
14:18:43 <tflink> if we needed some critical fix to the older code suddenly, we can do it off master as a hotfix and merge it back into develop
14:19:02 <tflink> thoughts? volunteers?
14:19:38 <mkrizek> I can send the merge diff for a review
14:19:45 <tflink> cool, thanks
14:19:47 * mkrizek is taskless anyway
14:20:20 <mkrizek> I can do that tomorrow, objections?
14:20:23 <tflink> it looks like the module code is pretty much done to the point where I can probably submit a review today
14:21:04 <tflink> but that can be a PoC review and we can merge it in after the disposable-develop closure
14:21:34 <kparal> sounds good
14:22:15 <tflink> the only potiential snag here is that I'm on PTO starting Thursday
14:22:22 <tflink> but I can hand off the module code
14:23:11 <mkrizek> I guess we'll see how the module code review goes
14:23:28 <kparal> tflink: Thursday till when?
14:23:35 <tflink> kparal: next wednesday
14:23:46 * kparal putting that into PTO calendar
14:23:52 <tflink> kparal: it's already there
14:24:00 <tflink> or should be unless I messed something up
14:24:02 <kparal> I don't see it
14:24:14 <kparal> might be in your personal calendar
14:24:14 * mkrizek doesn't see it either
14:24:21 <tflink> bah, wrong calendar
14:24:30 <kparal> usual mistake :)
14:24:42 <tflink> i thought I added it
14:25:37 <tflink> #action tflink to submit libtaskotron module review
14:25:50 <tflink> #action mkrizek to submit diff for disposable-develop merge
14:26:41 <tflink> anything else about the upcoming merge to cover here?
14:27:23 * kparal doesn't have anything
14:27:29 * tflink doesn't think so and takes silence as a no :)
14:27:32 <tflink> moving on to
14:27:46 <tflink> #topic Tasking
14:27:57 <tflink> does anyone need tasks?
14:28:46 * mkrizek is fine with the one he's just got
14:29:05 * lbrabec still has something in phab
14:29:33 <tflink> ok, I'll likely pester folks again on Wednesday :)
14:30:19 <tflink> #topic Next Week's Meeting
14:30:48 <tflink> I won't be available to chair next week - is someone else willing or do we just skip the meeting?
14:31:04 <mkrizek> let's skip the meeting! \o/
14:31:19 <kparal> \o/
14:31:33 <lbrabec> +1
14:31:44 <tflink> sounds like a decision is made there
14:32:01 <tflink> #info 2015-10-19 qadevel meeting is canceled
14:32:18 * tflink will send out a notice before leaving
14:32:42 <tflink> #topic infra/sysadmin coverage next week
14:33:30 <tflink> while I'm on PTO, I'm not even going to have cell coverage so I wanted to make sure there that there was coverage in case something goes wrong with our taskotron deployments
14:33:31 <kparal> oh, and I'm at Fedora InstallFest at a local university on 19th Oct anyway
14:34:52 <tflink> mkrizek: do you mind if I tell infra that you'll be covering the taskotron systems?
14:35:46 <mkrizek> nope I don't mind
14:36:18 <tflink> k, thanks
14:36:26 <tflink> #topic open floor
14:36:38 <tflink> anything else that should be covered?
14:36:41 * mkrizek is not sure if me being coverage is better than no coverage :D
14:36:51 <mkrizek> nothing here
14:37:01 <tflink> mkrizek: you know how the bits are put together and what's resident where, no?
14:37:10 <tflink> if not then I need to be better about knowledge sharing
14:37:55 <mkrizek> I knew that at some point, depends on what I managed to remember :)
14:38:27 <tflink> I really don't want to be the only one who knows how the bits are put together
14:38:36 <tflink> that kind of bus factor scares me
14:39:03 <mkrizek> I'll look into it tomorrow and will ask you questions before you leave
14:39:11 <tflink> sounds good to me
14:39:24 <tflink> I'm planning to rebuild stg today before freeze sets in
14:39:40 <tflink> stg isn't frozen but rebuilding it does require some changes to frozen systems
14:40:57 <tflink> if there's nothing else, setting the fuse
14:42:55 <tflink> thanks for coming, everyone
14:43:00 * tflink will send out minutes shortly
14:43:03 <tflink> #endmeeting