On Thu, Nov 24, 2022 at 9:12 AM Petr Pisar <ppi...@redhat.com> wrote:
> V Thu, Nov 24, 2022 at 02:40:09PM +0100, Miroslav Suchý napsal(a): > > > > Does anyone else feel like the documentation should be updated, or > > > > am I making too much of this? > > > > +1 to update documentation. Or even better, document which packages has > the > > exception. And later ask QE to create tool which will warn if packages > > outside of this list bump up version. > > > Checking for a version bump does not make sense unless you want to force > maintainers to backport each fix. (Nonpaid maintainers won't do it.) > +1000... Also, I think keeping the version the same and adding a bunch of upstream commits that essentially makes it the new version is fundamentally dishonest. Plus if you do need to report a bug upstream, which version is it? There's not really an option for "Frankenstein". My packaging philosophy has largely been, try not to perform soname bumps in released versions unless absolutely necessary, and most people want the latest version of user facing apps. Also, most upstreams of my user facing app packages release incrementally and frequently. If I didn't update them, I could easily be 10 releases behind between Fedora releases. That doesn't make sense. Thanks, Richard
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
