- Wednesday, July 26, 2017

release-team@conference.openafs.org

Wednesday, July 26, 2017< ^ >

Room Configuration

Room Occupants

GMT+0
[11:20:30] meffie joins the room
[14:59:36] wiesand joins the room
[15:01:23] <kadukoafs@gmail.com/barnowl35A66400> Good day everyone
[15:01:24] <wiesand> good morning usa
[15:03:00] <meffie> greetings wiesand
[15:04:10] <wiesand> So what's up? Any Linux news, besides those "designated initializers" now required for a few more structs?
[15:04:40] <jhg> good morning
[15:04:53] <meffie> just that one so far.
[15:05:02] jhg nods
[15:05:43] <wiesand> Great. We can expect buildbot to succeed on linux-daily/rc as of today then?
[15:06:52] <wiesand> (since Ben merged 12663 this afternoon)
[15:07:28] <wiesand> The linux-enoent-caching-fixes topic was not for 1.6, right?
[15:07:35] <meffie> yes, it should.
[15:07:52] <kadukoafs@gmail.com/barnowl35A66400> EAMBIGUOUS
[15:07:55] <meffie> next build is scheduled for 12 today
[15:08:18] <meffie> heh
[15:08:36] <jhg> wiesand: buildbot should pass. fwiw, robotest does as well.
[15:08:51] <wiesand> NIce.
[15:09:02] <wiesand> Ben: I'm being dumb again...
[15:09:14] <wiesand> What's ambiguous?
[15:09:26] <kadukoafs@gmail.com/barnowl35A66400> At first I thought Mike's "yes, it should" was replying to the
linux-enoent-caching-fixes question
[15:09:46] <meffie> sorry, ETOOSLOW
[15:09:58] <wiesand> ETOODUMB
[15:10:04] <kadukoafs@gmail.com/barnowl35A66400> And in that context I couldn't tell whether the fixes were or were not
needed for 1.6.  But I guess I also couldn't tell what it was even
replying to, which is failure on my end.
[15:10:06] <meffie> i'm that too.
[15:10:35] <meffie> linux-enoent-fixes are for 1.8.x (not 1.6.x)
[15:10:58] <mvita> oh, sorry, just remembered this...
[15:11:03] <wiesand> Thanks for the confirmation Mike.
[15:11:20] <wiesand> Mark: remembered what?
[15:12:29] <mvita> this meeting… I've not been "present"
[15:12:30] <meffie> maybe he means he just remembered the meeting
[15:13:38] <wiesand> Besides Linux 4.13 (of course….), the major topic for 1.6.22 was supposed to be "ubik fixes" IIRC. Could someone issue a "release managers summary" on that?
[15:14:06] <kadukoafs@gmail.com/barnowl35A66400> Sorry for the continued slowness on master.
I had a lot of excitement this weekend that cut into my review time.
[15:14:33] <wiesand> I prefer slowness over haste.
[15:15:11] <wiesand> Want to share what happened?
[15:16:09] <kadukoafs@gmail.com/barnowl35A66400> On a day when the high temperature was 108 F, we lost power for a few
hours.  Even at about 8pm when we finally were forced to seek out the
car's A/C, I think it was still 100 F (!).  Luckily, power was
restored and the power company's outage status website told us that,
so we could return home.  Just in time for a severe thunderstorm to
pass through, and have lightning either strike or nearly strike the
building, with side effect of setting off the fire alarm.
[15:16:54] <meffie> wow.
[15:17:23] <wiesand> The true cost of global warming...
[15:17:42] <kadukoafs@gmail.com/barnowl35A66400> The lightning also seems to have fried part of my local network (maybe
just a switch or switchport), an issue which was compounded by some
incorrect ping commands while trying to swap cabling around.  So I
didn't get the VM with my email client back up until the next day.
[15:18:01] <mvita> yikes
[15:18:21] <kadukoafs@gmail.com/barnowl35A66400> So that was exciting.
[15:18:29] <mvita> 108 is impressive
[15:18:52] <mvita> are you in St. Louis?
[15:18:59] <kadukoafs@gmail.com/barnowl35A66400> Yeah, St. Louis.
[15:19:12] <mvita> that's astonishing
[15:19:50] <kadukoafs@gmail.com/barnowl35A66400> Anyway, I took another look at a couple of the ubik changes this
morning -- 12613 is +2'd, and I think the locking is still not quite
right on 12609.  (I'm a little worried about increasing the scope of
the DB lock so much there, but my tentative analysis was that it was
okay.)
[15:19:59] <wiesand> When I visited death valley, it was just slightly hotter.
[15:20:32] <mvita> I was going to mention Death Valley as well - 108 is even hot there
[15:21:18] <kadukoafs@gmail.com/barnowl35A66400> And I've got 12592 up in a browser tab.
I know Jeffrey still thinks there should be better alternatives, but
trying to develop them feels riskier than this approach to me, so I'm
inclined to defer such attempts until post-1.8 and try to take this
pretty much as-is (once I finish review, of course).
[15:21:39] <meffie> sounds good.
[15:21:56] <mvita> cool
[15:22:08] <meffie> can we add a gerrit topic on these ubik changes?
[15:22:32] <kadukoafs@gmail.com/barnowl35A66400> Sure; any proposed text?
[15:22:47] <meffie> hrrmm.
[15:23:06] <mvita> "Here there be dragons"
[15:23:22] <wiesand> "ubik-urgent" ?
[15:23:32] <meffie> ubik-write-after-recovery-fixes ?
[15:24:02] <meffie> ubik-fix-write-after-recovery ?
[15:25:08] <kadukoafs@gmail.com/barnowl35A66400> Seems reasonable.
[15:25:37] <wiesand> Anyway, I think we're done with 1.6.x for today, so feel free to switch to 1.8 mode.
[15:27:37] <kadukoafs@gmail.com/barnowl35A66400> I also took a couple of the changes from the list from last week
[15:28:05] <kadukoafs@gmail.com/barnowl35A66400> 12652 (xserver deadlock) and 12638 (d_splice_alias/d_lookup race)
[15:28:47] <meffie> oh, 12653 was merged! great!
[15:29:48] <wiesand> We're in 1.8 mode, so I'll defer the question which of those are for 1.6.x to next week ;-)
[15:29:50] <meffie> wiesand: 12652 is for 1.6.x
[15:29:52] <kadukoafs@gmail.com/barnowl35A66400> I started looking for the list of things to be done post-branch on 1.8
and master respectively, but don't remember if that was in mail or
jabber.  (Apparently google doesn't index our jabber logs; not sure
whether that was intentional or due to the 403 at the top-level index)
[15:30:10] <meffie> 12653: is master/1.8.x only
[15:30:50] <meffie> i'll push a 1.6.x version of 12652
[15:31:17] <kadukoafs@gmail.com/barnowl35A66400> I did find in email a list of things (changes) to be done
pre-branching, but that was just before the meeting so I didn't
confirm that they're done yet
[15:32:03] <wiesand> Mike: ok, thanks
[15:32:26] <kadukoafs@gmail.com/barnowl35A66400> So I think the 1.8 action items are the list from last week and
finding the list of post-branch tasks...
[15:34:55] <wiesand> Looks like we're finished for today?
[15:35:25] <kadukoafs@gmail.com/barnowl35A66400> Yeah, I don't have any other topics.
[15:35:29] <kadukoafs@gmail.com/barnowl35A66400> (review review review!)
[15:35:35] <wiesand> Anyone?
[15:35:43] <meffie> thanks, i have nothing else.
[15:35:47] <kadukoafs@gmail.com/barnowl35A66400> And if people want to help look for the old list of tasks that would
be useful, but I can do it.
[15:35:49] <mvita> nothing here
[15:36:07] <jhg> I'me good
[15:36:13] <wiesand> Let's adjourn then. Thanks a lot everyone!
[15:36:26] <kadukoafs@gmail.com/barnowl35A66400> Thanks everyone!
[15:37:03] wiesand leaves the room
[15:37:10] <mvita> I found this in an email from Feb 2016
[15:37:14] <mvita> 1.8.x
Ben requested ongoing reviews for the following topic branches targeted for inclusion in 1.8.x:
- akeyconvert
- rxgen-size_t-workaround
- externalize-log-rotation
[15:38:33] <mvita> found a better one, forwarding to the mailing list
[15:41:14] <mvita> ah, no, it's a list of tasks that were blocking the 1.8x pre-release
[15:41:55] <kadukoafs@gmail.com/barnowl35A66400> Ah, the one I'm thinking of is like "bump version numbers", "remove
stub rxgk bits from 1.8 branch", "remove lwp", etc.
[15:42:32] <mvita> sorry, I don't have that one
[15:43:33] <meffie> https://wiki.openafs.org/archive/OpenAFS18Notes/ ?
[15:44:18] <kadukoafs@gmail.com/barnowl35A66400> Yeah, that!
[15:44:21] <kadukoafs@gmail.com/barnowl35A66400> Thanks!
[15:44:27] <mvita> cool
[15:45:11] <meffie> ok, have a good day everyone.
[15:51:39] meffie leaves the room
[16:51:57] meffie joins the room
[20:05:27] kadukoafs@gmail.com/barnowl35A66400 leaves the room
[20:05:39] kadukoafs@gmail.com/barnowl35A66400 joins the room
[22:39:53] meffie leaves the room