Hi Andreas,
On 14.09.2024 13:07, Andreas Mantke wrote:
Am 05.09.24 um 06:49 schrieb Áron Budea:
The reason would be impatience. Those patches were merged less than
two days ago, and porting patches can take a while depending on the
priorities (or forgetfulness) of the developer.
seemed like that. There are other developers which push their patches
first to the upstream project and afterwards to their distro branch.
Would it help if someone else would work on porting it to the master
branch, if the origin developer has other priorities or forget about it?
What could we do to improve the workflow here?
They will never be forgotten completely. At some stage, sooner or later,
they will arrive to the master.
On the other hand, porting between branches is not a trivial process.
Xisco does a great job of porting bugfix master patches to release
branches, which usually puts off that load from other developers who
made the master changes; but from time to time, it turns out to be
problematic.
I don't think that a change like "let's force merging patches to
branches other than the developers see best" would be an *improvement*
of the workflow (or of anything else). Of course, when someone sees that
there is an existing change in some branch, that is applicable to
another branch to fix some blocker, those people would themselves make
the needed backport (that happens a lot in product branches).
--
Best regards,
Mike Kaganski
