20:01:09 #startmeeting diskimage-builder 20:01:10 Meeting started Thu Sep 15 20:01:09 2016 UTC and is due to finish in 60 minutes. The chair is cinerama. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:01:11 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:01:11 hi 20:01:14 The meeting name has been set to 'diskimage_builder' 20:01:32 our agenda is here 20:01:36 #link https://wiki.openstack.org/wiki/Meetings/diskimage-builder 20:01:56 #topic Bugs process 20:02:23 so greghaynes wanted to talk about the bugs process - whether we should use launchpad or not & cleaning it up 20:02:36 i closed out ~25 bugs last week when i had a look 20:02:46 is there really any other option than launchpad? 20:02:51 storyboard 20:03:06 aiui there is a migration process that can be done 20:03:14 i haven't looked in on storyboard in a while but my impression is that it's more suitable for some kinds of tasks than others 20:03:20 s/is/was/ 20:03:51 we also have influence on what it is suitable for since we have the principle authors as part of the project 20:03:59 i think the main point was really that if we're going to continue to use this we need to clean up any old-n-crusty stuff 20:04:02 this is tru 20:04:35 an auto-close of old bugs might be ok? i know devstack amongst others has done that periodically 20:04:37 even if we do import we still need to cleanup 20:04:50 i can do some bug triage 20:05:04 that seems reasonable 20:05:11 bkero, that would be great if you want to pitch in 20:05:13 I'm sure there will be some things in there that I can't handle myself, but can always ask in channel. 20:05:20 bkero, please do 20:06:09 i had thought about having a more organized bug scrub day but i don't think that's going to work with people's schedules and/or primary responsibilities 20:06:33 anyone have any other thoughts on bug tracker? 20:07:25 not really, i think the honest fact is that if anyone is reporting a bug and expecting someone else to fix it, their odds of that happening are very low 20:08:09 but i don't think that is a dib exclusive problem 20:08:53 this is true. i'm not sure what we can do about that aside from recruiting more people to work on the project, marking bugs as lhf, etc 20:09:47 the other part of the bugs agenda item, which might help with this, is whether we should add a bugs section to the meeting. 20:09:59 i'm broadly in favor of this but not sure exactly what form it should take 20:10:24 possibly discuss new or important in-progress bugs? 20:10:48 add it to the agenda once its identified to be important? 20:11:37 could be good, then folks will have an opportunity to review them prior to the meeting 20:12:28 anyone have any other thoughts on that? 20:12:50 yes, if we have a list before we start, that seems to bound the time we would spend on it 20:13:47 which is probably a good thing 20:14:07 i'm going to say 20:14:31 #agreed Add key bugs discuss to meeting agenda 20:14:47 ok next main topic 20:14:54 #topic Dib 2.0 20:15:16 so we have the feature branch now 20:15:32 the main topic proposed was whether we should cut an RC 20:15:37 thoughts? 20:15:37 yes i merged most of our things from the 2.0 list in there 20:15:53 there's still something wrong with tripleo i haven't got to the bottom of 20:16:22 and i want to merge the "put elements under python package" + "diskimage-builder as entry-point" changes 20:16:26 the "pythonic dib" stuff 20:16:41 that sounds good 20:16:48 i'm trying to figure out how i can do that without causing very annoying merge issues 20:17:16 but so far, trying to use symlinks fails -- something in setuptools/pbr/... doesn't like it 20:17:48 https://review.openstack.org/#/c/367156/ is what i'm talking about 20:17:56 hmm 20:18:14 btw might be good if we can update the etherpad 20:18:23 #link https://etherpad.openstack.org/p/dib2.0 20:18:25 also i don't think i pushed it, but i have a similar change to remove the dependency for dib-utils 20:18:29 with the current status of the branch 20:18:48 last i spoke to greghaynes & spamaps both were in favour of removing our dependency on that 20:19:20 *but*, in a world where people know to "pip install" dib, it's also less of an issue 20:19:30 right 20:19:34 makes sense 20:19:41 yeah, i can update etherpad 20:20:06 thanks 20:20:53 any other thoughts on 2.0 20:21:40 not really from me 20:22:32 ok 20:22:56 #topic Open discussion 20:23:01 ok it's all you 20:23:12 just on release notes 20:23:22 good topic 20:23:29 generally before a release i've been backtracking and adding something with important changes 20:23:38 obviously the idea of reno is to add notes to changes as they come in 20:23:50 so i think it's fair enough to request them in reviews 20:23:53 for sufficient changes 20:24:05 yes, it looks like we've done per-release ones in the past but we should possibly move away from that 20:24:14 makes it easier when we go to release i think 20:25:02 things that change the behaviour of elements, scripts etc seems like a good bar 20:25:33 yep, or significant bugs fixed, that people might google for and hit the relnotes 20:27:24 #agreed Move to request release notes to be submitted with review 20:28:10 anyone have any reviews that want special attention at the moment? i've been working on other projects this week so i haven't looked much 20:32:01 okay 20:32:12 shall we wrap up for now? 20:32:28 that's all from me 20:32:49 bkero: unless you have anything, we'll close 20:33:46 ok thanks everyone 20:33:50 #endmeeting