https://bugzilla.redhat.com/show_bug.cgi?id=1211517 --- Comment #24 from Jan Chaloupka <jchaloup@xxxxxxxxxx> --- > We have processes decided by community, and just acting as if they do not > matter when we are using our @redhat.com email reflect very badly on the > community, cuase it send the message "we have rules for others, not for us". They do matter for me. And there is no excuse for breaking those rules. As you can see in many reviews of golang project, me and my colleagues are doing what we can to make golang packaging better. We have a lack of resource and there is still a lot of tasks to do to make automatic discovering of issues and updates of golang spec files. The effort to deal with dependencies is on. I could dick more into the deps and find what function or variable is broken, fix it and bult docker-swarm just from Fedora's deps. However, doing this for each update of docker is very frustrating. Once the tooling is done, it will be faster and easier to deal with it. Would be better to have an exception for every golang project until API breakage is resolved globally. It means functioning communication with upstream maintainers, tooling to automatically discover issues, automatic updates of spec files, etc. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review