- Wednesday, January 7, 2015

release-team@conference.openafs.org

Wednesday, January 7, 2015< ^ >

Room Configuration

Room Occupants

GMT+0
[13:10:32] stephan.wiesand joins the room
[13:10:48] stephan.wiesand leaves the room
[14:18:19] wiesand joins the room
[14:39:32] meffie joins the room
[14:50:31] kaduk joins the room
[14:59:24] Marc Dionne joins the room
[14:59:42] <wiesand> Happy new year!
[15:00:00] <kaduk> Happy new year!
[15:00:15] <Marc Dionne> happy new year to all.  hope everyone had good holidays
[15:00:47] <meffie> happy new year
[15:02:28] <wiesand> Let’s try to get an idea of what 1.6.11pre2 will be and how to get to it?
[15:03:30] <kaduk> Well, we probably want the linux 3.17/3.18 fixes you mentioned (though I haven't reviewed them closely)
[15:03:48] <kaduk> Someone should volunteer to supply the configure switch for 11643
[15:03:56] <wiesand> 11641/2/3 still need to be merged on master, 11643 needs a configure switch.
[15:04:17] <wiesand> Right, a volunteer for that would help...
[15:04:31] <kaduk> I guess we could talk about 11616 and whether we're happy with it as a trivial band-aid
[15:04:53] <wiesand> Marc, is it correct that these (11641/2/3) are all we need for current 3.17/3.18?
[15:05:19] <wiesand> 11616 is not even a pullup from master...
[15:05:32] <Marc Dionne> i think so, yes (11641-3)
[15:06:12] <wiesand> Thanks.
[15:06:42] <wiesand> Ah, Andrew suggested master removes fix_bad_parent entirely and 11616 would be 1.6-only.
[15:06:44] <kaduk> I think the reason the "Do not submit" was there was precisely because it wasn't a pullup from master
[15:07:02] <kaduk> But, it may be that we want to let the branches diverge in this case
[15:09:08] <wiesand> Makes sense. But without more review by folks with real insight, it seems unlikely that it can be merged anytime soon.
[15:09:48] <wiesand> But then, 11641/2/3 need that kind of review too, although they’re in slightly better shape.
[15:10:32] <Marc Dionne> 11616 seems low risk.  it only changes behaviour for a case where things currently crash
[15:10:49] <wiesand> Thanks!
[15:11:04] <kaduk> Yeah, I think 11616 is probably the right thing for 1.6
[15:11:42] <wiesand> Ok. I’ll resubmit it with the commit message changed.
[15:12:37] <wiesand> Ben pulled up 11644 as 11656. This would be nice to have in too?
[15:13:08] <kaduk> yes, not having silently corrupted data would be nice :)
[15:13:40] <Marc Dionne> not easy to trigger, but as it's data corruption it should probably go in sooner rather than later... :)
[15:13:53] <wiesand> Risk?
[15:14:48] <Marc Dionne> i don't see any there
[15:14:58] <kaduk> Seems pretty low-risk to me, though perhaps I should look at the 17 skipped lines before asserting it
[15:15:09] <wiesand> Sounds good, thanks.
[15:16:27] <wiesand> Any potential problems with 11645? (besides the need to have buildot verify it)
[15:17:47] <kaduk> No, 11645 should be fine.
[15:18:02] <wiesand> And then we have 11646/7/8 . These should not have any impact on pre-3.19 kernels, right?
[15:18:08] <kaduk> And, having looked at the 17 skipped lines in 11656, I stand by the low-risk assessment.
[15:18:18] <wiesand> Good, thanks.
[15:19:22] <Marc Dionne> in theory 11646-48 don't affect pre 3.19, but they move some code and ifdefs around a bit
[15:20:13] <Marc Dionne> 11648 in particular.  the other 2 I wouldn't worry about
[15:21:21] <wiesand> Will it be obvious from a smoke test whether or not 11648 introduces problems on older kernels?
[15:22:19] <Marc Dionne> getting the ifdefs wrong would hopefully just cause build breakage
[15:23:53] <wiesand> Thanks. They clearly look like 1.611pre2 candidates to me. I wouldn’t want to block on them though. But it would be really good to get them ready in time.
[15:24:06] <wiesand> What’s the chance that more changes will be required for 3.19?
[15:24:54] <Marc Dionne> not likely, but it's still fairly early in the cycle
[15:25:44] <wiesand> If there’s some chance the these are sufficient, all the more reason to get them into pre2.
[15:26:07] <wiesand> Any other changes urgent to include?
[15:26:33] <kaduk> I doubt it; we should be finishing things up for 1.6.11, I think.
[15:27:14] <wiesand> Yes, it’s overdue :-(
[15:28:01] <wiesand> So, “all it takes is some review and smoke testing”...
[15:29:25] <kaduk> Yeah...
[15:29:41] <kaduk> "We've got some 1.8 candidates that could use some review, too" ;)
[15:30:06] <wiesand> I’ll try to run test builds on my EL5/6/7 systems, hopefully this week.
[15:30:27] <kaduk> *nods*
[15:31:00] <wiesand> Fine, next topic: 1.8 branch. All yours ;-)
[15:32:21] <kaduk> So, I think probably the most important thing for us as a group to do is revive the threads from last month where the Jeffs had started talking about the volume header update times, and maybe there was another thread derived from that as well.
[15:32:45] <kaduk> (I should have tried to keep those going back when they started, but didn't manage to, unfortunately.)
[15:34:01] <kaduk> It looks like Jeff A has been persuaded by Jeff H explicitly pointing out that adding length limits to the vectors in the .xg files (for ptserver name and id lists) is equivalent to applying a local implementation limit and does not change the wire protocol/encoding, so hopefully we can move forward with that.
[15:35:42] <kaduk> There's maybe fourty-odd changes sitting in gerrit with CodeReview=-1 (and not CodeReview=-2) that are not ready for merging as-is, and largely not release blockers.  They are at risk of getting converted to CodeReview -2 and dropped from consideration for the release if they do not see updates soon-ish.
[15:36:49] <kaduk> The list of things with code review +0 or +1 is not much larger, actually, so we're not in terrible shape.
[15:38:03] <kaduk> I didn't get to do much preparation for today's meeting in terms of assembling a new list, but things from last time are still valid, e.g., someone might look at unifying what sorts of messages go to stderr from the command-line tools (IIRC we got a submission to change bos, and pts remains to get converted?).
[15:39:17] <kaduk> But mostly the main message is: review, review, review!
[15:39:39] <meffie> ok, no more egg nog.
[15:39:59] <kaduk> :)
[15:40:31] <kaduk> Given today's limited attendance and my lack of advance preparation, I'm not sure that we need to go into more detail during this meeting.
[15:41:38] <wiesand> Ok. BTW, part of the reason for the lack of minutes during the last week is that I could have gotten around to writing up the stable branch discussions, but would have had a hard time doing it for the 1.8 related ones.
[15:42:20] <kaduk> I guess Marc was maybe going to take another look at 10513
[15:42:37] <kaduk> Ah.
[15:43:23] <wiesand> So I’m planning to send out minutes for the 1.6 part to release-team. If something is added for the 1.8 part by someone else,  we can combine them before sending to -devel. Otherwise I’ll just refer to the transcript on the server.
[15:43:36] <kaduk> My flight left that wednesday afternoon, so I didn't really have time after the meeting to do much of anything :-/
[15:44:48] <wiesand> Not blaming anyone but myself, really.
[15:45:44] <wiesand> But that’s the only way I see to get minutes done at all in the near future. And I think they may help us get reviews.
[15:45:46] <kaduk> Don't blame yourself too hard, though -- you're doing a fine job
[15:45:54] <kaduk> *nods*
[15:46:30] <wiesand> Thanks :)
[15:47:14] <wiesand> Ok, this is probably what we’ll get on 1.8 today... does anyone feel like planning ahead for 1.6.12 now?
[15:47:30] <wiesand> I think this can wait...
[15:47:40] <kaduk> I'm going to sit on my hands, over here ;)
[15:48:35] <wiesand> Fine. Anything else to discuss today?
[15:49:30] <wiesand> Let’s call it a day then. Thanks a lot everyone!
[15:49:40] <kaduk> It's rather cold, over here.
[15:50:00] <wiesand> No true winter here :-(
[15:50:01] <kaduk> (read: no)
[15:50:25] <wiesand> guessed that... bye
[15:50:28] wiesand leaves the room
[15:50:48] kaduk leaves the room
[15:52:12] meffie leaves the room
[18:04:22] Marc Dionne leaves the room
[20:34:44] shadow@gmail.com/barnowlE5B64A04 leaves the room
[20:34:52] shadow@gmail.com/barnowlE5B64A04 joins the room
[20:36:10] shadow@gmail.com/barnowlE5B64A04 leaves the room
[20:37:01] shadow@gmail.com/barnowlE5B64A04 joins the room
[20:41:54] shadow@gmail.com/barnowlE5B64A04 leaves the room
[20:42:04] shadow@gmail.com/barnowlE5B64A04 joins the room
[20:45:48] shadow@gmail.com/barnowlE5B64A04 leaves the room
[20:46:00] shadow@gmail.com/barnowlE5B64A04 joins the room
[21:57:28] kaduk joins the room
[22:06:59] kaduk leaves the room