I should have been more clear. Ganesha V4.1 will be a tag applied to this week's or a following week's merge on next. At that point, I will create a v4-stable branch at that tag for future stable branch patches and the next merge on next would be tagged V5-dev.1. This is the process we have been following for the past several releases where we tag a stable release, and then accept patches to it in next until we tag the first stable update. THEN we open the new release for contributions, forking a stable branch to receive backports of additional fixes and subsequent stable update tags. So this request is which patches that have not been merged yet should be merged into next before tagging V4.1. Frank From: Frank Filz [mailto:ffilzlnx@mindspring.com] Sent: Tuesday, June 7, 2022 10:45 AM To: devel(a)lists.nfs-ganesha.org Subject: [NFS-Ganesha-Devel] Trying to wrap up Ganresha V4.1 this week I would like to do a final merge for Ganesha V4.1 this week. We have quite a number of patches ready to merge or real close. Please peruse this list: https://review.gerrithub.io/q/status:open+project:%255E.*nfs-ganesha.*+branc h:next+repo:ffilz/nfs-ganesha Any patches that have not been updated as of June 2nd or later are not under consideration. Any other patches that don't have a +2 vote (and especially those with unresolved comments or -1 votes) should be addressed so they can be resolved and be ready for merge by Friday. Thanks Frank Filz