That seems impractical as it will result in every commit creating a new issue since it isn’t possible to commit to both branches at once.
Ralph > On Jan 2, 2023, at 1:50 AM, Volkan Yazıcı <vol...@yazi.ci> wrote: > > Suggestion: Shall we harness GitHub Actions to create a GitHub Issue > telling commit X needs to be reflected on branch Y whenever a commit lands > on branch Z? > > If you all agree, I volunteer to set this up. > > On Fri, Dec 30, 2022 at 9:48 AM Piotr P. Karwasz <piotr.karw...@gmail.com> > wrote: > >> Hi all, >> >> As you know `master` is painfully lagging after `release-2.x`. The >> main problem is that it is still diverging (in the wrong direction). >> >> In the Tomcat repository you can observe 4 commits within minutes, >> addressing the same issue in all 4 supported branches. Can we do >> something similar in Log4j? What I mean is, whenever a commit occurs >> on the `master` or `release-2.x` branches we: >> >> * either receive 2 e-mails in a short timespan (5 minutes?), that >> basically mean that we need to prepare 2 commits locally before >> pushing it, >> * receive 1 e-mail, but the commit message (not necessarily the title) >> explains why the other branch has not been touched. >> >> I have been trying to follow this for a couple of months and it is not >> always easy: sometimes I can not push a commit/PR to `release-2.x`, >> because `master` requires cherry-picking 5 other commits that we >> forgot to cherry-pick before. And the commit is deferred by another >> day... >> >> "Next" weekend I'll try to write down the sync status of `master` on >> the Wiki. I'll break it down into modules and for `log4j-core` into >> packages. >> >> Piotr >>
