Hi list, I own the rhcontainerbot account. Apologies it took so long to respond to this thread. A number of legitimate concerns have been raised about the bot, so let me address those below on behalf of the Containers team.
1. We have disabled all autobuilds for now. 2. The podman RC build landing in updates a month ago was a one-off and it has been discussed at: https://lists.podman.io/archives/list/pod...@lists.podman.io/thread/WYNTH224D5MVBC2RFOG6RPIC52JZFKAB/ 3. The fuse-overlayfs downgrade occurred unintendedly during the upstream branch rename from master to main. That has been fixed at: https://koji.fedoraproject.org/koji/buildinfo?buildID=1775442 Disabling autobuilds during the branch rename phase would’ve evidently avoided this issue. 1. Going forward: 1. We will only manually build upstream release tags for Fedora releases. We would prefer to send RC tags to Fedora rawhide as that will trigger gating tests and allow us to test podman with FCOS and toolbox CIs, so please let us know if that would be a deal-breaker. 2. We may look at re-enabling the bot only for koji builds of upstream releases, while bodhi updates will still be manual. We’ll make sure to check for breakages / version downgrades before re-enablement. The bot has so far compared upstream tags, rpm installability, version number sanity, but evidently it has missed a lot of cases including git branch changes. 3. If we re-enable the bot, we will mention the human’s name and email for every changelog entry in every relevant package as well as regularly monitor the bot’s email. Please let us know if there are any concerns with this approach. 4. We will use openSUSE’s OBS for builds of the latest upstream commits for our users who need the latest packages. We would need this to check if the latest commits in podman work well with new kernel features and selinux. 1. Team members will not add karma to containers’ packages, with the exception of our QE Engineer who owns our gating tests and is in charge of final testing of our builds. Currently Ed Santiago (FAS: @santiago) owns that responsibility. 1. We will also notify the containers’ communities that rawhide will no longer contain the latest builds as some of them are accustomed to using. Please let us know if there are any concerns that were left unaddressed or if you have any further recommendations or feedback. -- Lokesh On Fri, Jun 25, 2021 at 12:13 AM Dan Čermák <dan.cer...@cgc-instruments.de> wrote: > > > On June 22, 2021 1:26:30 PM UTC, "Miroslav Suchý" <msu...@redhat.com> > wrote: > >Dne 20. 06. 21 v 10:42 Miro Hrončok napsal(a): > >> Rather than "no bots allowed" policy, we might need a "bots that > >violate our policies and guidelines or have a > >> tendency to break things will be disabled until fixed" policy. > > > >Every bot has been written by somebody. 1) it should be always clear > >who is responsible for the bot 2) The owner should > >take conseq^H^H^H responsibility for it. > > I'd prefer this policy over an outright ban. > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure >
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
