Learn more about these different git repos.
Other Git URLs
I have proposed a new repository called epel-next. This is described in detail on the epel-devel list.
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/thread/NYXQNQFAY44RNCJTP6WLYUGJSQX5XSIX/
Rather than dump all the work onto releng, I would like to perform as much of the work myself as possible (with releng guidance). This will also be beneficial for crossover work in my role on the CPE team. The planned out steps give a better picture of the work involved (and thus the permissions needed).
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/ZZ2NXNFEEO237XUO2ZYBCOCAKKUGA56P/
2020/10/27 (1 week after expected F33 release)
2022/05/31 (approximate CentOS Stream 8 EOL)
EPEL package incompatibility with CentOS Stream. Reduced adoption of CentOS Stream. Reduced community contributions for RHEL 8.
Metadata Update from @humaton: - Issue tagged with: high-gain, medium-trouble
Metadata Update from @humaton: - Issue tagged with: ops
We will be implementing this post f33 release.
I was granted permission to staging koji to prepare the steps that will eventually be used in prod. The next thing I need is permissions in staging bodhi so I can work out the steps needed there.
So everything is set in prod, is this ticket still needed?
I think we can close this out. Rather than gaining any additional permissions myself, @smooge and @mohanboddu took care of things for me.
Metadata Update from @carlwgeorge: - Issue close_status updated to: It's all good - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.