- Thursday, May 5, 2022

release-team@conference.openafs.org

Thursday, May 5, 2022< ^ >

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

Room Configuration

Room Occupants

GMT+0
[09:29:21] mvitale leaves the room: Replaced by new connection
[09:29:22] mvitale joins the room
[14:37:10] mvitale leaves the room
[14:41:33] mvitale joins the room
[15:57:35] meffie joins the room
[15:57:43] <meffie> greetings.
[15:59:30] wiesand joins the room
[15:59:47] Cheyenne joins the room
[15:59:56] <Cheyenne> hello all :)
[15:59:58] <kaduk@jabber.openafs.org/barnowl> greetings!
[16:00:02] <wiesand> Hello
[16:01:41] meffie currently working on my workshop talk submission.
[16:01:53] <meffie> due today!
[16:03:18] <wiesand> Good. I'm afraid I won't be able to present.
[16:03:41] <wiesand> In fact I have yet to register I think
[16:04:19] <meffie> Ben, would you be able to give an "openafs report" ?
[16:04:36] <mvitale> hello
[16:05:12] <kaduk@jabber.openafs.org/barnowl> I am actually not sure I will be able to attend, which precluded me
from thinking about submitting a proposal for a talk
[16:05:27] <meffie> oh, that's unfortunate.
[16:05:40] <kaduk@jabber.openafs.org/barnowl> Indeed.
[16:06:09] <mvitale> maybe you could pull together some notes and one of us could present it on your behalf?
[16:06:41] <mvitale> pre-recording is also an option
[16:06:42] <kaduk@jabber.openafs.org/barnowl> That's plausible
[16:07:35] <meffie> here is the text from last year's schedule:
[16:07:44] <meffie> Abstract:
Updates on work that has been done for the OpenAFS stable release branches, work that is merged to the main development branch but not expected to be incorporated into the current stable release branches, and the status of planned future work.
[16:07:54] <mvitale> We would really like to hear from you, O Captain, My Captain    ;-)
[16:08:11] <kaduk@jabber.openafs.org/barnowl> I will see what I can do :)
[16:09:23] <mvitale> Stephan, maybe you could consider the same options, and for the same reasons:  we appreciate your work and value your perspective
[16:10:15] <meffie> since the cfp is due today, i think it would be best if i submit a cfp proposal today and mark or i can present on your behalf if you are not able to attend?
[16:13:12] <wiesand> sounds good - worst case, this slot could host contributions from bot Ben and me - I just can't commit to anything right now
[16:13:25] <wiesand> But at least I just registered
[16:13:44] <kaduk@jabber.openafs.org/barnowl> I guess I was not sure if Mike's proposal was for one slot each for
Stephan and me, or one combined slot.
[16:13:45] <mvitale> understood
[16:13:58] <kaduk@jabber.openafs.org/barnowl> (I'm happy to make either work.)
[16:14:12] <mvitale> agreed, whatever suits
[16:14:26] <meffie> I thought just one slot, and just reuse the text from last year.
[16:14:43] <kaduk@jabber.openafs.org/barnowl> That makes a good bit of sense; please go ahead and make the
submission
[16:14:52] <meffie> ok, thank you.
[16:15:07] <mvitale> Thank you!
[16:17:28] <mvitale> today we are seeing a last minute surge of talk proposals, so that's encouraging as well
[16:17:34] <kaduk@jabber.openafs.org/barnowl> :)
[16:22:57] <kaduk@jabber.openafs.org/barnowl> I don't think I have many topics for today, as last week's travel
covered the weekend which would be the main chance for me to do AFS
work.
[16:23:56] <Cheyenne> Well.. on a Linux-5.18 front.  The patch has been pushed to gerrit and is waiting for review.  There is no functional change for kernels prior to 5.18
[16:24:16] <kaduk@jabber.openafs.org/barnowl> That was indeed the only topic I was going to have for today :)
[16:24:37] <kaduk@jabber.openafs.org/barnowl> I did take a look at the patch, and it looks like some mostly-cosmetic
changes have already been proposed
[16:24:51] <kaduk@jabber.openafs.org/barnowl> The fundamental mechanisms seem sound, though.
[16:25:33] <Cheyenne> I'm hoping.  Will be helpful to have a 2nd pair of eyes look at the change :)
[16:25:56] <meffie> i've finished a number of non-afs backlog things here, so started updating old gerrits i submitted which have comments on them.
[16:26:25] <kaduk@jabber.openafs.org/barnowl> I did not actually read the linux docs for readahead, though :-/
[16:26:34] <meffie> and hope to be more active in the reviews.
[16:29:41] <wiesand> only news I have is that I did the bookkeeping on that Linux-5.17 stack pulled up by Michael - nice set of path conflicts
[16:30:06] <wiesand> 14953 clashes too
[16:30:22] <kaduk@jabber.openafs.org/barnowl> A reminder that we cannot defer the "next stable branch" topic
indefinitely, hmmm
[16:30:49] <wiesand> I really have to get cracking merging stuff, or things will become absolutely unwieldy within weeks
[16:31:35] <Cheyenne> I believe most of the conflicts are around the decision to include or not include some of the autoconf updates
[16:31:43] <wiesand> and maybe they already are
[16:32:14] <meffie> have you tried cherry-picking on a local branch to see if there are merge conflicts?
[16:32:16] <Cheyenne> (for the 14946 stack that is)
[16:32:46] <wiesand> are you saying 14924..46 aren't acutally required?
[16:33:02] <Cheyenne> I have a local branch that I've cherrypicked the 14946 stack
[16:33:42] <Cheyenne> yes 14945/14946 are required, the 14942-14943 is "support" for those 2
[16:35:20] <Cheyenne> (the local branch that I have also pulls in the patches for gcc-11 and clang-13 support as well)
[16:35:46] <wiesand> of course, 45/46 are the ones that clash
[16:37:13] <wiesand> give me another week to make some progress, and if it really doesn't work out we should probably try something radically different
[16:37:29] <kaduk@jabber.openafs.org/barnowl> ok
[16:37:37] <Cheyenne> Okay
[16:38:40] <wiesand> and that might be a nice topic to discuss at the workshop ;-)
[16:39:19] <kaduk@jabber.openafs.org/barnowl> :)
[16:43:07] <meffie> ok, good luck on the patches for stable wiesand.
[16:43:35] <meffie> let us know if there is something we can do to help.
[16:44:12] <meffie> maybe Cheyenne could share his branch on a github repo?
[16:47:48] <wiesand> one idea for "something radically different" is to do away with what I pulled up (or am planning to) and just ask Cheyenne to pull up what consttiutes his local branch
[16:48:39] <wiesand> that would require a lot of review, and swiftly or it's not going to help either
[16:49:20] <kaduk@jabber.openafs.org/barnowl> If there's a need for a specific focused effort I can try to schedule
some time.
[16:52:13] <wiesand> Cheyenne, if we'd go that route and thus just use your branch, would that be a 1.8.8.2 release or a 1.8.9 one?
[16:54:44] <meffie> seems it should be 1.8.9, given the number of patches?
[16:58:10] <kaduk@jabber.openafs.org/barnowl> (BTW I have a hard cutoff at the hour.  I don't think we had other
topics to cover, though.)
[16:59:09] <meffie> i have nothing else. thanks all!
[16:59:15] <wiesand> mike: yes, so it seems - and yes, that's one of our bigger problems
[16:59:44] <kaduk@jabber.openafs.org/barnowl> Having enough patches to merit a 1.8.9 is a problem?
[17:00:10] <meffie> oh?
[17:00:41] <wiesand> I don't know how to resolve that conflict between an urgent need for those Linux fixes and many "underlying" changes - so I hesitate, things are stuck and get worse all the time
[17:00:54] <kaduk@jabber.openafs.org/barnowl> Mike: Isn't that what Stephan said, as "that's one of our bigger problems"?
[17:01:07] <kaduk@jabber.openafs.org/barnowl> Ah, I think I see now.  Thanks Stephan!
[17:01:14] <kaduk@jabber.openafs.org/barnowl> Also, thanks all, and have a good week :)
[17:01:28] <mvitale> thanks
[17:01:41] <wiesand> let me try - if I fail, we must change something
[17:02:17] <wiesand> But let's adjourn now. Thanks a lot everybody!
[17:02:31] <meffie> thanks! take care all.
[17:02:59] meffie leaves the room
[17:04:20] <Cheyenne> Sorry.. had to step away for a moment.
[22:28:53] wiesand leaves the room
[22:54:02] Cheyenne leaves the room