serg according to the policy we discussed around bintars, this should not be a requirement. 16.04 is EoL, we should not even be building this system. Can you explain what is the basis for this request?

because it's a "main" builder and it fails? I don't want to see red in buildbot, if it should not even be building — remove it, it will solve the problem too. Or at least move to experimental

serg you agreed on "Transition from the old BB to the foundation BB - status and remaining steps"
e-mail to keep releasing 10.5 from buildbot.mariadb.net
so I will remove from buildbot.mariadb.org trusty and centos6 bintars

This task shouldn't be Critical if we agreed previously on "from where do we release 10.5".
But ok, I get your point on "main builder" being red.

As for the other bintars, please see my comments on (work is done, I just need your or Elena's OK to deploy them in Production):

• new-bintar: https://jira.mariadb.org/browse/MDBF-866
• centos7 bintar updates: https://jira.mariadb.org/browse/MDBF-883

assigned faust also for review (Ansible part):
https://github.com/MariaDB/buildbot/pull/692

old kvm bintars for 10.5 removed from buildbot.mariadb.org