- Friday, September 7, 2018

release-team@conference.openafs.org

Friday, September 7, 2018< ^ >

Room Configuration

Room Occupants

GMT+0
[11:36:05] wiesand joins the room
[11:57:42] Marcio Barbosa joins the room
[13:00:47] <kaduk@jabber.openafs.org/barnowl> greetings
[13:01:01] <wiesand> hello
[13:01:46] <wiesand> is september 11 the deadline for "your" release ?
[13:02:16] <kaduk@jabber.openafs.org/barnowl> Yes
[13:02:33] <wiesand> ouch
[13:02:48] <kaduk@jabber.openafs.org/barnowl> "Weekned?  What weekend?"
[13:02:50] mvita joins the room
[13:03:05] <kaduk@jabber.openafs.org/barnowl> That said, I think I have a handle on everything needed.
[13:03:08] <mvita> oh, hello
[13:03:16] <wiesand> hello mark
[13:03:16] meffie joins the room
[13:03:26] <wiesand> ben: good to hear that
[13:03:32] <meffie> good morning.
[13:03:46] <mvita> Ben do you need anything from me for that?
[13:04:01] <wiesand> the question is: does it make sense to release a 1.6.22.4, 1.8.1.1 and especially 1.6.23pre1 before that?
[13:04:09] <wiesand> i think not…
[13:04:41] <kaduk@jabber.openafs.org/barnowl> mvita: it would be good if you could look at my updated patchset, but
if you lack time that's okay.  My other question I thought I had for
you I did figure out the answer to.
[13:05:19] <mvita> oh, I'm sorry you were waiting for me.
[13:05:23] <kaduk@jabber.openafs.org/barnowl> I think it would be okay to do 1.6.22.4 and 1.8.1.1 if they're ready.
[13:05:31] <mvita> this week has been a bit of a peanut scramble
[13:05:40] <mvita> but I have time to do stuff today
[13:05:49] <mvita> I will look at your patches
[13:06:20] <wiesand> for 1.6.22.4 I just merged everything and rolled tarballs, to be uploaded after a final test run
[13:06:23] <kaduk@jabber.openafs.org/barnowl> Thanks!
[13:06:33] <wiesand> 1.8.1.1 should be done later today
[13:07:01] <kaduk@jabber.openafs.org/barnowl> Cool
[13:07:12] <wiesand> and 1.6.23pre1 will become 1.6.24pre1 I guess
[13:07:39] <kaduk@jabber.openafs.org/barnowl> Sounds like it, yeah.
[13:07:52] <meffie> because ben will still the number 23?
[13:07:58] <kaduk@jabber.openafs.org/barnowl> yup
[13:08:03] <meffie> steal
[13:08:18] <meffie> ok
[13:08:58] <wiesand> it would be cleaner to cut 1.6.23 from the 1_6_22-branch …
[13:09:44] <wiesand> and then cherry-pick  the 1.6.23 changes onto 1_6_x immediately
[13:10:35] <kaduk@jabber.openafs.org/barnowl> I thought everything on 1.6.22-branch was already on 1.6.x?
Or do you mean that 1.6.x has patches that haven't been in a release
yet?
[13:11:10] <wiesand> the latter
[13:11:43] <wiesand> cutting from 1_6_22-branchwould yield a nice linear history verywhere
[13:11:51] <wiesand> everywhere
[13:12:25] <kaduk@jabber.openafs.org/barnowl> I'll take a look at the current commit tree before finalizing
anything.
[13:13:32] <wiesand> ok, thanks
[13:13:46] <wiesand> i'll be somewhat available during the weekend
[13:13:56] <kaduk@jabber.openafs.org/barnowl> ok, thanks
[13:16:10] <kaduk@jabber.openafs.org/barnowl> So it sounds like we have "1.6.22.4 and 1.8.1.1 out real soon" plus
"next 1.6.x feature release is 1.6.24"; is there more on the stable
front (anything to review, etc.)?
[13:16:52] <mvita> I updated the GCtrans patchset based on your review comments
[13:17:52] <wiesand> re #134654 i think it's not a bug
[13:18:58] <kaduk@jabber.openafs.org/barnowl> I think it's valid tar syntax, yes
[13:19:53] <wiesand> and this line hasn't changed since 2006 - i can take care of the ticket
[13:20:14] <kaduk@jabber.openafs.org/barnowl> Cool, thanks!
[13:22:21] <meffie> >  So it sounds like we have "1.6.22.4 and 1.8.1.1 out real soon" plus
"next 1.6.x feature release is 1.6.24";
should i put that in the release-team notes to openafs-devel mail list?
[13:22:52] <meffie> or just the 1.6.22.4/1.8.1.1 news?
[13:23:04] <wiesand> i think that's it from the stable front (it was said last week that GCtrans can wait for a release)
[13:23:29] <kaduk@jabber.openafs.org/barnowl> I guess just the 16.22.4/1.8.1.1, since the other isn't fully
locked-in yet.  Though these jabber logs are public, so anyone really
interested knows already.
[13:24:21] <wiesand> yes, and if we get the .1's out today it's not even hot news
[13:25:02] <meffie> ok, thanks
[13:25:57] <wiesand> i intend to handle 1.6.22.4/1.8.1.1 with a single announcement and news entry on the webiste - objections?
[13:27:04] <kaduk@jabber.openafs.org/barnowl> Seems okay to me, given that the "new content" of the releases are the
same.
[13:28:50] <wiesand> ok
[13:32:26] <meffie> sounds good
[13:33:17] <kaduk@jabber.openafs.org/barnowl> I'm sorry I didn't get to look at anything for master this week;
between being travelling (but still trying to work remotely) and
working on the other release I just didn't have any time to spare.
[13:33:28] <kaduk@jabber.openafs.org/barnowl> (But I'm back home now.)
[13:34:26] <meffie> new items on master include chroot-sysname (for better docker support)
[13:34:58] <meffie> and i've been spending some time reviewing pat's static-analysis patches
[13:35:08] <kaduk@jabber.openafs.org/barnowl> I saw the email about those new changes, but didn't open them up.
It'll be interesting to see what the implementation looks like.
[13:35:42] <kaduk@jabber.openafs.org/barnowl> I'm also excited about the static-anlaysis stuff getting review;
that's important work to do but does require the sort of careful
review that can be mind-numbing in too large a chunk.
[13:36:07] <meffie> yes. i find i cant be too tired.
[13:36:44] <meffie> there are some "false" alarms, and so some changes can be harmful.
[13:36:51] <kaduk@jabber.openafs.org/barnowl> Exactly
[13:37:15] <kaduk@jabber.openafs.org/barnowl> Were there other (master?) topics people wanted to talk about, or are
we wrapping up?
[13:37:32] <meffie> question: how do we feel about de-orbiting venus/kdump ?
[13:37:33] <kaduk@jabber.openafs.org/barnowl> I've forgotten the state of the buildbot transition, even :-(
[13:37:47] <mvita> kdump: the sooner the better
[13:37:58] <meffie> it triggers a lot of problems with warnings and such. and we dont use it any more.
[13:38:24] <kaduk@jabber.openafs.org/barnowl> "I don't even know what it's for"
[13:38:34] <mvita> it's a diagnostic tool
[13:38:54] <mvita> extracts stuff from (kernel) memory
[13:38:57] <mvita> iirc
[13:39:38] <mvita> is that right, meffie?
[13:40:12] <meffie> yes. for old systems. as far as i know, it is not supported or used. we have dtrace and systemtap now.
[13:40:17] <kaduk@jabber.openafs.org/barnowl> That would fit as an etymology
[13:40:36] <kaduk@jabber.openafs.org/barnowl> It looks like none of rpm/debian/freebsd install it
[13:40:46] <meffie> it reads kernel memory and dumps out stuff from libafs variables
[13:41:12] <meffie> yes, it is not packaged on linux. just hp-ux
[13:41:14] <kaduk@jabber.openafs.org/barnowl> So, signs are pointing to "probably okay to remove", though we should
probably broach it on -info first.  Maybe it's still useful on AIX or
something.
[13:41:30] <meffie> ah, ok.
[13:41:37] <wiesand> chroot-sysname would be a nice feature, but it seems to be per pid rather than per chroot?
[13:41:54] <mvita> as Mike says, dtrace & systemtap, plus supported kernel debuggers (gdb, crash, mdb, etc) obviate the need for kdump
[13:41:58] <kaduk@jabber.openafs.org/barnowl> chroot(3) only works in a single process :)
[13:42:12] <wiesand> and it's children, right?
[13:42:51] <kaduk@jabber.openafs.org/barnowl> yes...
[13:43:03] <meffie> you'd have to ask anrdrew about these patches. they are getting some real world use with docker.
[13:43:30] <mvita> Andrew's linux-native-mounts patchset is also interesting
[13:43:42] <kaduk@jabber.openafs.org/barnowl> Indeed.
[13:44:02] <mvita> I've messed with it a bit, it does what it says on the tin
[13:44:09] <wiesand> per pid makes sense for "classic" docker containers with just a single process, but isn't helpful fo anything spawning further processes :-(
[13:45:42] <meffie> well, that might be a good question to ask?
[13:46:36] <meffie> it could be this is just the first in a series of changes?
[13:46:59] <meffie> to limit the number of gerrits we need to review :)
[13:48:25] <kaduk@jabber.openafs.org/barnowl> That is possible :)
[13:49:41] <meffie> at any rate, it seems to be progress
[13:50:05] <wiesand> is anyone able to smoke test the current HEAD of 1_8_x swiftly?
[13:50:23] <meffie> yes
[13:51:29] <wiesand> now? ;-)
[13:51:46] <mvita> heh
[13:51:49] <meffie> yes, starting a vm to build and smoke test it
[13:51:54] <meffie> with openafs-robotest
[13:52:11] <wiesand> great
[13:53:15] <mvita> I started one as well
[13:53:22] <wiesand> great, thanks
[13:53:53] <wiesand> nb 1.6.22.4 smoke test is fine
[13:54:09] <mvita> "My kingdom for parallel configure support"
[13:54:55] <wiesand> yes, that's what i'm longing for as well
[13:55:49] <mvita> configure is done
[13:57:32] <mvita> Ben, I have your patches and have started looking at them
[13:57:46] <kaduk@jabber.openafs.org/barnowl> yay!
[13:58:33] <kaduk@jabber.openafs.org/barnowl> Do we have anything else for today?
[13:59:18] <mvita> my 1.8.x test failed due to config issues in my testbed
[13:59:26] <wiesand> not yet (just rolling 1.8.1.1 tarballs)
[13:59:26] <mvita> meffie, it's up to you
[14:00:13] <meffie> my vpn hates me :(
[14:00:23] <mvita> it's always sumpin'
[14:01:11] <mvita> <dual tracked on another mtg>
[14:01:42] <kaduk@jabber.openafs.org/barnowl> It sounds like we should wrap this one up, then.
[14:01:46] <kaduk@jabber.openafs.org/barnowl> Any objections?
[14:01:57] <mvita> none here
[14:01:59] <meffie> yes, thanks. i'll run the smoke test ...
[14:02:24] <wiesand> fine, let's adjourn - mike: drop me a mail withe the test result?
[14:02:41] <meffie> (i sorted out my vpn issue)
[14:03:50] <kaduk@jabber.openafs.org/barnowl> Okay.  Thanks everybody!
[14:04:10] <wiesand> Thanks a lot everybody! Expect the ususal "please have a look at the release stuff" mail a bit later…
[14:04:26] <mvita> thanks
[14:19:21] meffie leaves the room
[14:22:07] <mvita> openafs 1.8.x on Fedora 24
[14:22:09] <mvita> Linux f1 4.11.12-100.fc24.x86_64 #1 SMP Fri Jul 21 17:35:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
[14:22:21] <mvita> confirmed (passed automated tests)
[14:23:05] <mvita> [mvitale@f1 sna-openafs-master]$ git l10
      1 e819a01 (HEAD, refs/remotes/origin/openafs-stable-1_8_x) Update NEWS for 1.8.1.1
[14:23:58] <mvita> AFS version: OpenAFS 1.8.1-3-ge819a 2018-09-07 mvitale@f1
[14:24:08] <mvita> (not tagged yet)
[17:13:27] <wiesand> thanks a lot mark
[17:13:48] <mvita> you are welcome
[19:30:06] meffie joins the room
[19:32:26] <meffie> wiesand: : i was able to build and smoke test the current tip of openafs-stable-1_8_x (sorry for the delay, beset by meetings/questions today)
[20:46:24] meffie leaves the room
[21:42:46] mvita leaves the room
[22:17:13] Marcio Barbosa leaves the room
[23:14:12] mvita joins the room