On 7/20/23 07:59, Dirk Müller wrote:
Hi Eyad,
Am Do., 20. Juli 2023 um 13:49 Uhr schrieb <eyadlorenzo@gmail.com>:
Maybe I've not understood everything, but what about using the current workflow but with git branches?
It means that you have two PR/MRs that are unrelated and it doesn't fix the current problem that devel project maintainer accepts something that then gets rejected in the factory review (bots or humans). the improvement comes from having all the reviews happening in one PR that starts with the change and ends with the change ending in factory.
But who does the review? Today only factory reviewers have the permissions to accept into Factory. This, today makes the assumption that somewhere in the devel project there was a review by a person that is an "expert" for a given package. Now granted we have many packages that do not require special attention. But we also have many packages that do require special attention. So how do we get those packages that do require special attention reviewed by the people that have the most insight into those packages. For example we should always have a botocore, boto3 and aws-cli submission pretty much at the same time and not a random botocore update. How do we prevent the "drive by" botocore update if that request does not get reviewed by the people that know that the packages should always go together? Thanks, Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Distinguished Engineer LINUX rjschwei@suse.com IRC: robjo