Dear all, Acting as release engineer for Tizen:Common, I recently received a submission to update the profile/common/meta package in the project.
This submission has been done on a commit that was *not* reviewed in proper conditions: https://review.tizen.org/gerrit/#/c/23955/ When I looked at the patch, it was already merged. So I had no other choice but rejecting the submission. I made the necessary comments but had no answer from the commiter or the merger. I ask everyone to *follow the rules* and give other reviewers at least 24 hours to check and review the patches. If really urgent, ping by direct email. And communicate with other maintainers of the package. *Doing things silently without any coordination is not a good idea*, especially on meta packages and OBS projects. The same misbehavior has been observed also today, as someone added a arm-x11 repo on Tizen:Common OBS project, without any notification. see: https://build.tizen.org/project/show?project=Tizen%3ACommon The result is that we switched from a "clean" OBS project (no error) to a main project with errors: this makes the prerelease builds messy and incurs more work from RE to triage errors. Who's responsible for that and what should I do with this repo ? Best regards, -- Stéphane Desneux Intel OTC - Vannes/FR gpg:1CA35726/DFA9B0232EF80493AF2891FA24E3A2841CA35726 _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
