Hello everyone! About a year ago, we introduced our release syncing automation for Fedora. But that was just the start! The most important part was the feedback we got when we began getting people on board to start using this automation.

As we started with onboarding, we realized there was more to do than just getting new users. We have been collaborating with packagers, fixing bugs, adding missing elements, and polishing our documentation. And besides tweaking the automation for Fedora, we have been lately working on doing the same for CentOS Stream to bring the same simplification for the maintainers there. We've learned a lot, and the journey isn't over – with more users, we're still figuring out how to prioritize feature requests and bug fixes. But we enjoy every bit of it.

This talk will dive into our journey – the challenges, victories, and everything in between. We'll compare then-and-now in Fedora's release automation, showing the improved cool features and progress that has been made, allowing even more packagers to use our automation. And of course, it doesn’t stop here. We will also discuss our plans for future enhancements, including the work on release syncing to CentOS Stream, validation of new version updates, as well as our efforts to make the release process even easier for maintainers. If you're curious about our experience, join us!

Curious about Packit and Testing Farm? Wondering how they could benefit your project? Join us as we delve into their capabilities and explore how they can improve your project's health on Fedora through early integration testing.
Discover real-life examples showcasing both familiar and newly added features. Exciting updates await – including secrets support, multi-host testing, improved CLI and user interface support for bare-metal and dedicated GPU test machines. All Fedora contributors can now easily onboard to Testing Farm with Fedora SSO.
Need to fine-tune your test execution? Explore our latest features allowing granular test triggering based on pull request labels and job tagging. Plus, simplify complex setups with customizable test suites and job templates. And for features spreading across multiple repositories, you can test the changes together.

Struggling with the stability of your dependencies? Introduce your test suite into their development process and let them know they are breaking your work.

And if you by any chance need to have multiple packages in a single git project, Packit can help as well.

Don't miss out on unlocking the full potential of Packit and Testing Farm – join us as we uncover a wealth of possibilities for your project.