Hello mufti, On Mon, Jul 29, 2019 at 9:56 PM J. Scheurich <mufti11@xxxxxx> wrote: > What can you do in a informal review more than sending comments with > found potential problems ? Helpful comments such as those you've made on Bugzilla are always welcome. You may have noticed some people using a template when reviewing packages, one that covers all possible aspects of a package. This template is produced by the fedora-review tool, but you can always do the same work manually, as long as you go over the same areas (fedora-review and the template really help the reviewer keep track of things). In December, Michael Schwendt gave you the link to the package review process: https://fedoraproject.org/wiki/Package_Review_Process This page explains how things should proceed, what each interested party needs to do and it contains a few relevant links. I noticed that you had issues when building some of the packages that you commented on. Given that new packages in fedora start their lives in rawhide, if you do not want to maintain a rawhide instance, Mock is a great tool to test builds in whichever fedora version you want, especially rawhide: https://github.com/rpm-software-management/mock/wiki https://fedoraproject.org/wiki/Using_Mock_to_test_package_builds Best regards, A. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
