Now that master is very active again, this will continue to be a problem There is really no good clean solution to the problem as our process is now:
If you expect pull request mergers to also merge branch to branch then they will be less apt to approve pull requests. (thought this is the good compromise in the mean time) If you expect pull request makers to do it, you won't get pull requests. We don't have enough developers with enough experience to do this - and it's a pain for those few that do. If we wait and do it time to time (as we do) it become a huge problem. Is there a way to do partial merges? so merge the work you are familiar with? Is there another process that is less painful for our devs to work with? Doing the same thing over and over is not going to fix the problem! Chris ________________________________ From: Hans Unzner <hansunz...@gmail.com> Sent: December 31, 2023 1:23 PM To: emc-developers@lists.sourceforge.net <emc-developers@lists.sourceforge.net> Subject: Re: [Emc-developers] Merge 2.9 to master Am 31.12.23 um 13:29 schrieb andy pugh: > On Sun, 31 Dec 2023 at 12:14, Hans Unzner <hansunz...@gmail.com> wrote: > >> You mean via Github by the author of the PR? Not sure if that will work. >> Better that the person who merges it keep track of it. > That assumes that the person who accepts the merge understands the > code as well as the one creating the code, which is rarely likely to > be the case? > I hope that the person who merges the PR have at least a rough idea what the change is about. Otherwise how could this person judge if this PR is good or bad? _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
