> -----Original Message----- > From: Development <development-boun...@qt-project.org> On Behalf Of Volker > Hilsheimer via Development > Sent: maanantai 17. maaliskuuta 2025 9.59 > To: Marc Mutz <marc.m...@qt.io>; development@qt-project.org > Subject: Re: [Development] On Pick-to: and QUIP-16 > > > Marc, > > QUIP-16 documents what kinds of changes are permitted in each branch. There is > no requirement that those changes must get picked back. That decision is > absolutely within the authority of the author of the change, the reviewers, > and > ultimately the maintainer of the respective submodule. > > And it's also perfectly fine to originally aim for a certain branch, but - > upon > noticing the amount of work or changes requires to resolve conflicts - abandon > the cherry-picking from that branch on. >
Yeah, and before approval reviewers should also review, if change is really 'Picked to' correct branches. To every needed, but also if there is unnecessary branches included. In the release branches, we got lots of 'nice-to-have's' picked in, which doesn't belong to the release branch at all. Of course unclear cases belongs to release manager responsibility, but there is lots of clearly incorrect ones as well. And how much this kind of 'mistakes' is going in stable, strict and very strict branches without noticing those... br, Jani -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
