Changelogs – the essential but often underestimated narrative of software updates. Ever found yourself in the dilemma of "keep it short" versus "give me all the details" when documenting changes? You're not alone.

Join us for an engaging discussion where we'll collectively tackle the changelog chaos. Throughout the talk, we'll navigate the complexities, explore best practices, brainstorm areas for improvement, and share experiences.

Whether you're an upstream maintainer, a coding enthusiast, a downstream package maintainer, or simply intrigued by the challenges, your perspectives are more than welcome. Come, share your thoughts, and let's make sense of the changelogs together!

Ever wondered if our tools are worth the hype? Well, instead of us blowing our own trumpet, let's hear it straight from the horse's mouth – our satisfied users! Join us for a session where a handful of our users take the stage to showcase their setups, leaving you inspired and itching to join the world of Packit, Testing Farm and tmt.

Prepare to be impressed as they unveil the secrets behind seamlessly integrating your own tests into projects you rely on, automating your RPM pipeline, and using one test definition across various systems. Whether you're a seasoned quality engineer or just dipping your toes into the testing pool, you'll walk away with fresh ideas and a newfound enthusiasm for the endless possibilities our tools offer. So, come and get ready for a delightful journey through the world of testing made easy!

Here are the tools involved:

Packit is an open-source project aiming to ease the integration of your project with Fedora Linux, CentOS Stream and other distributions.

Testing Farm is a reliable and scalable Testing System as a Service. It is commonly used as a test execution back-end of other services or CI systems.

The tmt tool provides a user-friendly way to work with tests. You can comfortably create new tests, safely and easily run tests across different environments, review test results, debug test code and enable tests in the CI using a consistent and concise config.