- Thursday, March 24, 2022

release-team@conference.openafs.org

Thursday, March 24, 2022< ^ >

kaduk@jabber.openafs.org/barnowl has set the subject to: openafs release team

Room Configuration

Room Occupants

GMT+0
[14:23:00] mbarbosa joins the room
[15:44:26] mmeffie joins the room
[15:55:37] wiesand joins the room
[15:58:40] <mmeffie> greatings
[15:58:47] <mmeffie> greetings ;)
[15:58:59] <wiesand> Hello
[16:01:29] Cheyenne joins the room
[16:01:34] <Cheyenne> Hello all
[16:04:57] <wiesand> Yay, +1's on all the open changes for stable-1_8_x, thanks. Merging those away will help make things a bit more wieldy.
[16:06:02] <wiesand> I think the one interesting change in the prepare-14387 stack is 14928 .
[16:06:52] <mmeffie> oh i see there are 8 gerrits for 1.8.x that i did not vote on. i'll do that today.
[16:07:27] <wiesand> Pulling that one into a point release feels a bit awkward, but better than the alternative.
[16:07:46] <wiesand> Thanks Mike.
[16:08:27] <Cheyenne> Oh.. 14838 would be nice.. not necessary, but nice.. it removes some complaints from newer autoconf
[16:08:37] <mmeffie> sorry i missed those!
[16:10:14] <wiesand> 14838 is on my list - probably rather for 1.8.9 than 1.8.8.2 though?
[16:10:36] <Cheyenne> that would be fine. -- as I mentioned, it's a would be nice
[16:11:02] <Cheyenne> but not necessary
[16:11:16] <wiesand> Mike: most of those I pulled up shortly after last week's meeting.
[16:12:50] <mmeffie> yes, the emails went into my "gerrit" folder. thank you.
[16:16:17] <wiesand> So, on my list of things to merge "soon", there are the FBSD related ones and the prepare-4387 changes. I hope to get a test build done today and merge tomorrow. That should make the next set of pullups smoother.
[16:16:54] <mmeffie> excellent!
[16:18:53] <wiesand> Maybe I should send mail to -devel asking for review when I have new pullups available? (The feature to invite reviewers in gerrit hates me - but maybe I should try again, haven't for a while)
[16:21:02] <mmeffie> i think adding reviewers in gerrit is the best way.
[16:21:47] <mmeffie> that is how i think most people to track what needs to be reviewed.
[16:22:26] <mmeffie> gerrit sends so much mail, it can get lost though, but i feel that is the best way.
[16:24:56] <mmeffie> it can be hard though, because some people (like Marcio) have multiple gerrit identities and it is not clear from the ui which one to use.
[16:25:17] <wiesand> Ah, it seems to work at least for adding you. Brace ;-)
[16:26:01] <mmeffie> perhaps when ben has some time he can rename the obsolete identities.
[16:26:13] <wiesand> That's all I have for today.
[16:26:35] <mmeffie> andrew is also very responsive to review requests.
[16:27:38] <mmeffie> ok, Cheyenne is checking the new linux prerelease
[16:28:01] <Cheyenne> No new surprises for Linux-5.17 (which GAed). Linux-5.18 pre-rc has a very minor item that will be a trivial fix (the autoconf test will be bigger then the code change)
[16:28:20] <wiesand> As so often…
[16:28:29] <wiesand> Thanks for checking!
[16:30:38] <mmeffie> in other news, Cheyenne and I finished upgrading the buildbot.openafs.org to the current release (3.5.0, up from 2.8.2)
[16:30:47] <wiesand> On other news, I heard it's unlikely that Yadav will return, sadly.
[16:31:11] <mmeffie> yeah, Yadav is busy with other things I have heard.
[16:31:16] <wiesand> Ah, good.
[16:31:45] <mmeffie> Cheyenne did the bulk of the work for the upgrade and is now able to run the ansible playbook to update the buildbot master.
[16:32:28] <wiesand> I'm not a huge fan of ansible, but that's still good.
[16:33:32] <mmeffie> it beats making changes manually. the playbook and files are in the github repo https://github.com/openafs_contrib/afsbotcfg
[16:34:00] <mmeffie> ops fatfingers.
[16:34:18] <wiesand> (it's kind of a personal issue between YAML and me ;)
[16:34:26] <mmeffie> https://github.com/openafs-contrib/afsbotcfg
[16:34:44] <mmeffie> yeah, yaml is not my favorite either.
[16:35:38] <wiesand> Anything else to discuss today?
[16:35:44] <mmeffie> that repo also includes a "molecule" test to create a local master and some local workers for testing before deploying changes.
[16:36:47] <mmeffie> i have nothing else
[16:37:13] <mmeffie> oh, i did
[16:37:45] <mmeffie> thanks for the www.workshop <http://www.workshop> vol release!
[16:38:01] <mmeffie> is there a way we can automate those so i dont have to bug you?
[16:38:17] <wiesand> Ah, right. I did the release but failed to notifiy you about it, sorry.
[16:40:04] <mmeffie> also, i wanted to mention, Mark and I have been getting some mails about GSoC from prospective contributors, so it is looking good so far.
[16:40:20] <wiesand> I don't know. While I have an admin principal, that and the knowledge how to remctl to bring the web changes alive is all I know about the inner workings of g.c.o.
[16:41:21] <mmeffie> hmm, ok.
[16:42:06] <wiesand> The right one to ask for this would probably be jhutz.
[16:42:19] <mmeffie> ok, thanks i'll ask jhutz.
[16:43:30] <mmeffie> thanks wiesand, have a good evening.
[16:43:35] <wiesand> Of course I could create a keytab and a cron job on one of our systems, but I doubt that it would be appreciated ;-)
[16:44:06] <wiesand> Ok, let's adjourn. Thanks a lot Cheyenne & Mike!
[16:44:12] <kaduk@jabber.openafs.org/barnowl> I find it likely that jhutz/cg2v have some existing automation for
remctls that release volumes
[16:44:26] <Cheyenne> Have a good week everyone.
[16:56:33] wiesand leaves the room
[16:57:00] mbarbosa leaves the room
[23:14:32] Cheyenne leaves the room