- Thursday, June 23, 2022

release-team@conference.openafs.org

Thursday, June 23, 2022< ^ >

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

Room Configuration

Room Occupants

GMT+0
[03:01:14] mvitale leaves the room: Replaced by new connection
[03:01:48] mvitale joins the room
[15:56:12] wiesand joins the room
[15:58:33] meffie joins the room
[16:02:43] Cheyenne joins the room
[16:03:01] <Cheyenne> Hello all
[16:03:22] <mvitale> ot
[16:03:30] <mvitale> it's that time already
[16:03:51] <meffie> greetings
[16:07:24] <mvitale> stepping away for a minute, brb
[16:12:02] <wiesand> hello, sorry for being late
[16:14:55] <wiesand> I don't have much to talk about today, except plans…
[16:15:45] <wiesand> these are to start merging the 1.8.8.2 stack over the weekend (or finding out why I wouldn't…)
[16:16:30] <wiesand> NB I liked the workshop last week.
[16:16:33] <mvitale> back
[16:16:47] <mvitale> oh, good, I'm glad you liked the workshop
[16:17:38] <meffie> thanks for participating in the workshop.
[16:17:49] <mvitale> it was good to see you there, and other AFS admins as well
[16:20:48] <kaduk@jabber.openafs.org/barnowl> Oops, was caught up in my other meeting and forgot to look at this
window
[16:20:56] <wiesand> Looks like Christof succeeded with his tumbleweed build thanks to Cheyenne's help. Those notes may help me too.
[16:21:36] <wiesand> Though I know there's another mail regarding that stack from Cheyenne still slumbering in my Inbox.
[16:21:46] <Cheyenne> wiesand: all the commits are "in order", so if you grab 14946 you should have everything that needs to be merged in one linear branch (except for the NEWS and make release)
[16:22:36] <wiesand> Yes, I think you already told me. I'll give it a try and cry for help if I need it. Thanks.
[16:22:39] <Cheyenne> tumbleweed is going to need the 5.18 patches which are still in review on master
[16:23:14] <Cheyenne> just holler if you need help -- I'll check email over the weekend when I can :)
[16:23:27] <wiesand> Thank You!
[16:23:31] <kaduk@jabber.openafs.org/barnowl> Did my comments on the last 5.18 patch make sense?  I didn't get to look at
your response yet
[16:23:45] <kaduk@jabber.openafs.org/barnowl> (and I see that there's 5.19 stuff in there now, too, which I haven't
looked at yet)
[16:25:14] <Cheyenne> kaduk_jabberopenafsorg: yeah.. I'm taking another look at 14953.  It is quite possible I mis-understood something in there, so more eyes are very helpful.
[16:26:00] <kaduk@jabber.openafs.org/barnowl> Well, I'm pretty sure that I misunderstood at least one thing, too :)
(okay, I skimmed the responses to my comments)
[16:26:03] <Cheyenne> the 5.19 changes were straight forward (only big issue is my bad choice of naming things :)
[16:26:26] <meffie> wiesand: i found a nice/easy way to show the order of commits to be merged by gerrit number.
[16:28:00] <mvitale> ooh, do tell!
[16:28:21] <meffie> https://pastebin.ubuntu.com/p/4WwkvsdhSf/
[16:28:42] <meffie> > wiesand: all the commits are "in order", so if you grab 14946 you should have everything that needs to be merged in one linear branch (except for the NEWS and make release)
[16:29:15] <meffie> that, plus some git fu gives you the list by gerrit number in order. i'll post an email.
[16:29:21] <Cheyenne> oohhh. that's nice meffie :)
[16:29:31] <mvitale> thanks, Mike
[16:30:06] <kaduk@jabber.openafs.org/barnowl> That looks like `git log --oneline --decorate` output in a repo that
has fetched all the changes/* refs
[16:30:07] <meffie> git log --oneline --reverse --decorate origin/openafs-stable-1_8_x..HEAD >/tmp/changes
[16:30:28] <meffie> yes, pull the .git/config stuff to grab all the changes
[16:31:08] <kaduk@jabber.openafs.org/barnowl> [remote "origin"]
        url = ssh://gerrit.openafs.org/openafs.git
        fetch = +refs/heads/*:refs/remotes/origin/*
        fetch = +refs/changes/*:refs/remotes/origin/changes/*
[16:31:14] <kaduk@jabber.openafs.org/barnowl> that last line being the key one
[16:31:33] <kaduk@jabber.openafs.org/barnowl> N.B. I have a separate repo where I do this, as it bloats local
operations a bit much for my "daily use" repo
[16:31:37] <meffie> 43 [remote "gerrit-changes"]
44     url = ssh://gerrit.openafs.org/openafs.git
45     fetch = +refs/heads/*:refs/remotes/gerrit/*
46     fetch = +refs/changes/*:refs/remotes/gerrit/changes/*
[16:31:56] <meffie> yes, you'll want to do this in a sandbox repo
[16:32:27] <wiesand> Thanks!
[16:32:40] <meffie> i'll write up the steps and post to release-team
[16:35:32] <meffie> i suppose once you have that list, it should be possible to use the gerrit ssh commands to merge them in order in one swoop.
[16:36:06] <meffie> that might be a bit scary tho.
[16:39:22] <meffie> back to changes... 15038 (Avoid more out of bounds indexing when checking volume names) is in response to the bug pointed out by IBM during the workshop.
[16:40:05] <meffie> it's a tiny change, i hope it can go in (there are possible followup clean-up changes we could do for master)
[16:40:22] <kaduk@jabber.openafs.org/barnowl> Yup, I saw that go by but haven't had a chance to actually look at it
yet.
[16:40:28] <meffie> thanks!
[16:40:50] <kaduk@jabber.openafs.org/barnowl> I think I may have not mentioned for this context that I switched
roles within Akamai a couple weeks ago and am getting up to speed with
my new team
[16:41:13] <meffie> ah, cool! anything you can tell?
[16:41:30] <kaduk@jabber.openafs.org/barnowl> And the team is moving fast -- today we have a seven-hour batch of
meetings scheduled to do the first run at one of our key deliverables
[16:41:48] <meffie> yikes
[16:42:10] <kaduk@jabber.openafs.org/barnowl> It's a team that's looking at providing company-wide architecture
guidance/standards to improve the reliability and resiliency
properties of our systems
[16:43:10] <wiesand> So, all success with that!
[16:43:22] <kaduk@jabber.openafs.org/barnowl> Thanks!
[16:45:17] <meffie> Yes, best of luck!
[16:46:09] <kaduk@jabber.openafs.org/barnowl> Anyway, the key point for right now is that I'm distracted since I'm
in that other meeting as well.
[16:46:32] <Cheyenne> Oh.. on a buildbot->gerrit related topic.. there was an update to sort the buildbot results so that failures are grouped together
[16:46:45] <kaduk@jabber.openafs.org/barnowl> But I think finishing up Cheyenne's list of 5.18 work is my priority
for master, and I want to get to the 5.19 stuff faster than I got to
5.18
[16:46:58] <meffie> and i added an AlmaLinux9 buildbot worker this week.
[16:47:32] <wiesand> That's all very goos news.
[16:47:44] <meffie> Sounds good, thanks Ben!  motion to adjourn to let ben get back to the $dayjob :)
[16:47:47] <Cheyenne> as I mentioned earlier the 5.19 changes were really simple (pretty mechanical actually)
[16:47:51] <kaduk@jabber.openafs.org/barnowl> good news, even :)
[16:48:12] <wiesand> fat fingers…
[16:48:40] <Cheyenne> I'll also go through the feedback I got from Christof on the tumbleweed changes.
[16:48:50] <meffie> excellent, thanks
[16:48:59] <Cheyenne> Q: should I just push my stack out to github and let folks know it's there?
[16:49:36] <meffie> it's not already there?
[16:50:02] <Cheyenne> yes -- but I didn't really tell anyone..
[16:50:12] <meffie> (your sandbox github that is)
[16:50:26] <Cheyenne> (correct)
[16:50:47] <wiesand> dropping a line to release-team (maybe even devel) won't do harm
[16:51:11] <Cheyenne> Oh... master commits for tumbleweed.. 13136, 15029, 14956, 14956, and 14953 (which is the 5.18 commit)
[16:51:44] <Cheyenne> Okay.  thanks :)
[16:52:14] <wiesand> Motion to adjourn sustained. Let Ben focus on his $dayjob meeting.
[16:52:23] <wiesand> Thanks a lot everybody!
[16:52:27] <Cheyenne> sounds good.  Have a good week everyone.
[16:52:42] <meffie> thanks all, be well
[16:58:29] meffie leaves the room
[19:39:42] wiesand leaves the room