Hey everyone!
I’m looking to get a clearer understanding of how OpenMandriva manages its release pipeline, specifically how packages move from Cooker over to Rome and how Rome is maintained as a rolling distribution.
Is there any kind of automatism in the creation of packages on Cooker, for QA and for the port to Rome?
If anyone can share how the build farm (ABF) workflows and repo syncs are configured for this—or point me to relevant docs—I’d really appreciate it!
Thanks!
Hi Davide,
A good starting point would be the Cooker documentation, followed by the packaging and QA workflow pages:
Cooker:
Packaging and ABF:
QA workflow:
The documented package flow is Cooker → Rolling → Stable.
Developers and package maintainers initiate builds in Cooker and move packages to Rolling/testing, after which QA takes over.
I’m still learning the workflow myself, but it seems designed to keep collaboration between developers and QA pretty straightforward.
As far as I’m concerned, it’s all simple as it should be a great collaborative open source project.
Sorry for my absence, but these have been some unusual days. So, if I understand correctly, there aren’t automated processes or whatsoever for creating and maintaining the packages.
There is no automation for new packages. Package version updates can be somewhat automated if the package maintainer has written a script to automatically update versions and trigger new builds, but as far as I know there is no official method for automatic updating.
I understand, would you consider implementing some sort of automation in managing ISO image packages, repositories, and releases?
I ask because there are distributions that want packages to be managed only by trusted packagers and don’t look favorably on automated management.
Instead, there are distros like opensuse and openmamba that rely heavily on automation with very positive results.