19:01:07 #startmeeting 19:01:07 Meeting started Wed Jun 11 19:01:07 2014 UTC. The chair is rl1987. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:01:07 Useful Commands: #action #agreed #help #info #idea #link #topic. 19:01:34 don't really know how to use it myself. 19:01:41 hi meeting 19:01:43 #help 19:01:58 rl1987 remember to stick around until the end of the meeting so you can say "#endmeeting". 19:02:05 yes. 19:02:08 hi athena 19:02:14 #topic 0.2.5.5 19:02:25 #topic 0.2.5.5 19:02:28 hm. that seems to be a chair only thing 19:03:22 So, for 0.2.5.5, there are 3 tickets left to review. None is terribly big. I'm tempted to just merge them all. unless athena thinks she can look at them today/tomorrow-ish? 19:05:33 The tickets are #12184, #8746, and #12191. 19:06:31 I am pretty sure that #12191 is correct: my only question is whether to put it in 0.2.5. I lean yes, since it could conceivably be related to #12184 (though I doubt it) 19:07:14 #12184 is pure diagnostic code; it should be a comparatively easy review. 19:07:24 #8746 is process-control code, but should be fairly simple for that 19:07:44 #12184 is something we need to fix, and better diagnostics will help us, so putting that off doesn't seem like an option 19:08:06 and #8746 is a "send SIGINT to the wrong process" bug, so we shouldn't leave that lying around or it might hurt somebody 19:08:15 athena: what do you think about reviewing those? 19:08:29 okay, think i agree with keeping them in 0.2.5 19:08:47 uh, can review when i've gotten closer to being awake :) 19:09:00 think you can get through them today/tonight? 19:10:59 yeah, think so 19:11:19 that would rock. I think 0.2.5.5-alpha might be the last alpha in this series 19:11:25 woot 19:11:30 depending on how well our #12184 and #8387 diagnostics work 19:12:04 #action athena tries to review the 3 remaining 0.2.5.5-alpha needs_review tickets 19:12:38 #action once the remaining tickets are reviewed, nickm starts the ball rolling on getting 0.2.5.5-alpha out. 19:12:46 #commands 19:12:46 Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #rejected #restrictlogs #save #startmeeting #topic #unchair #undo #unlurk 19:13:21 #yolo #twitter #swag 19:14:10 So, the next topic... 19:14:19 #topic planning 0.2.6 and beyond 19:15:20 We have a bunch of tickets in needs_review for 0.2.6 19:15:26 and a bunch of bugs in 0.2.6 19:15:31 and some big features we want to do "soon" 19:16:10 and an ongoing ambition to get releases out more rapidly. 19:16:41 I think we should probably start out by reviewing a bunch of the stuff pending in 0.2.6. 19:17:00 seem plausible? 19:17:19 yeah, think so 19:19:08 maybe we should start with a self-review: foreach patch that we wrote ourselves: do we still like it? Do we still think it should go in as-is? 19:21:25 certainly seems like a good idea for things that have been hanging around long enough to look back at with fresh eyes 19:21:44 I think for some stuff we might say "This is crap and isn't mergeable without tests" 19:21:57 we might even say "This isn't a good idea; nothing would use it!" or "Why would you even" or something. 19:23:12 at that point, we should also think about dev priorities. We have some big ones (hidden services, ed25519 keys, guard node improvements) but IMO we shouldn't say "no 0.2.6 without these". 19:23:38 They are all important, but everything is important. 19:23:49 well, not everything. 19:24:01 I wonder if we should set aside some time once 0.2.5.5 is out for 026-triage 19:24:19 And IMO we should also do an 0.2.5 postmortem. 19:25:02 like, we froze a few months ago. Why did it take so long to get it kinda stable? 19:25:14 did we mis-handle the freeze or what? 19:25:32 or do we really need to plan 3 months dev, 3 months debugging for every release? 19:25:48 * armadev exists 19:25:53 hi armadev 19:26:37 athena: do you want to try to come up with some ideas too, looking back on our 0.2.5.5 schedule and what happened when, or do you think it would be more fruitful for me to try to do that myself? 19:30:23 nickm: probably you yourself unless you want to wait for me to be markedly more alert than at the present moment 19:30:34 ok. then 19:30:49 #action nickm will review what happened with 0.2.5.5 when, and see what mistakes we made. 19:31:28 #action once we have the 3 remaining items merged to master, nickm and athena will look at our own tickets in needs_review/needs_revision for 0.2.6, and see if any are really bad ideas or need more revision. 19:31:40 #action nickm and athena will pick a time to meet for 026 ticket triage 19:32:00 although i'm inclined to say half "yeah, plan debugging time" and half "fewer outside assholes chewing up my life (out of this damn apartment in two more weeks, yay)" 19:32:30 * isis doesn't wish to distract, but wants #12254 to have some feedback so that she can work on it for 0.2.6 19:34:41 * nickm comments on it 19:34:57 super! 19:38:28 anything else for this meeting? 19:39:25 isis: commented 19:40:46 endmeeting? 19:41:05 sure 19:41:42 #endmeeting