Fedora used ODCS for ELN composes. Honestly I'm not sure it was a great match, as it didn't really bring many benefits and introduced significant overhead and complexity.

There is practically no active development at the moment, but the project itself is not deprecated. Let's call it maintenance mode. Bugs generally get fixed.

We are still planning on continuing to use it at Red Hat for the time being. Konflux changes things though. ODCS doesn't fit into that, so eventually it will be phased out. I'd expect at that point we would archive/sunset the upstream project too, unless someone else steps up to take over.

Thanks for that information Lubomir. That helps me understand how much to invest here with my product (Ceph).

https://composes.stream.centos.org/ really looks like ODCS - Is the CentOS project still using it? @arrfab do you know?

@ktdreyer : it's still actually used for the CentOS Stream 9 and 10 composes, but with people mentioning Konflux here and there, I'm myself in doubt about the future.
@asamalik (CentOS Stream Team lead) would probably be able to help answering that but I confirm that odcs is still used today for centos stream composes

To clarify : we're still on odcs 0.2.50 : (https://cbs.centos.org/koji/packageinfo?packageID=8239)

Thanks @arrfab for mentioning me here!

We in CentOS Stream use ODCS for our composes. @ktdreyer got the URL right, that's where all the results land. (https://composes.stream.centos.org/)

We're aware of the maintenance issue, and might be looking into replacing it, but haven't started yet. We only call the ODCS API through Jenkins, so we don't provide users to make their own on-demand composes. Maybe we could be using Pungi directly. But as I said, we haven't really started looking into replacing it very heavily.

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/pungi/odcs/issues/675

Please continue any further discussion there.