Requesting permanent exception for python-damo

salimma commented

2025-04-08 16:15:50 +00:00

Owner

DAMO (Data Access Monitoring Operator) is a user space tool for the kernel's DAMON framework, used for monitoring data access patterns and making data-access-aware memory management optimizations.

It releases frequently - weekly on average, with some exceptions. The version numbers are not semantic (so think of x.y.z just like systemd's xyz) but does have a process for deprecating old features; they don't get immediately dropped

Ref: https://github.com/damonitor/damo/blob/next/README.md#will-the-features-of-damo-be-supported-forever

https://github.com/damonitor/damo/blob/next/FEATURES_DEPRECATION_PROCESS.md <-- non-experimental features get at least 3 months of grace period between deprecation and removal

https://github.com/damonitor/damo/blob/next/FEATURES_DEPRECATION_SCHEDULE.md

So effectively features can be deprecated, and are deprecated, on a rolling basis (weekly) and we can't rely on them being maintained for the lifecycle of a Fedora release (13 months). And upstream does not maintain old versions:

https://github.com/damonitor/damo/blob/next/CONTRIBUTING

Can we grant this package a permanent exception? If not it looks like we can only update it in Rawhide, and/or scrutinize every release to make sure nothing is dropped that is not already deprecated as of the first version shipped in that Fedora release (the latter is obviously a lot of work)

And if we ship a version that's too old people will just run it from a local checkout anyway, so that seems to defeat the purpose of packaging.

DAMO (Data Access Monitoring Operator) is a user space tool for the kernel's [DAMON](https://damonitor.github.io) framework, used for monitoring data access patterns and making data-access-aware memory management optimizations. It releases frequently - weekly on average, with some exceptions. The version numbers are not semantic (so think of x.y.z just like systemd's xyz) but does have a process for deprecating old features; they don't get immediately dropped Ref: https://github.com/damonitor/damo/blob/next/README.md#will-the-features-of-damo-be-supported-forever https://github.com/damonitor/damo/blob/next/FEATURES_DEPRECATION_PROCESS.md <-- non-experimental features get at least 3 months of grace period between deprecation and removal https://github.com/damonitor/damo/blob/next/FEATURES_DEPRECATION_SCHEDULE.md So effectively features can be deprecated, and are deprecated, on a rolling basis (weekly) and we can't rely on them being maintained for the lifecycle of a Fedora release (13 months). And upstream does not maintain old versions: https://github.com/damonitor/damo/blob/next/CONTRIBUTING Can we grant this package a permanent exception? If not it looks like we can only update it in Rawhide, and/or scrutinize every release to make sure nothing is dropped that is not already deprecated as of the first version shipped in that Fedora release (the latter is obviously a lot of work) And if we ship a version that's too old people will just run it from a local checkout anyway, so that seems to defeat the purpose of packaging.

salimma commented

2025-04-08 16:26:43 +00:00

Author

Owner

To add: this is a leaf node

decathorpe commented

2025-04-08 18:06:15 +00:00

Owner

I'm ok with granting this a permanent exception, though it would still be good to avoid pushing breaking changes to stable branches, when possible. Is it always obvious from the release notes that there were breaking changes?

salimma commented

2025-04-14 22:11:18 +00:00

Author

Owner

It's generally obvious: release note entries starting with 'remove' are the ones that remove functionalities (likewise searching for 'deprecate' will show functionality that gets deprecated)

https://github.com/damonitor/damo/blob/next/release_note

It's generally obvious: release note entries starting with 'remove' are the ones that remove functionalities (likewise searching for 'deprecate' will show functionality that gets deprecated) https://github.com/damonitor/damo/blob/next/release_note