Re: Add a push update mechanism for https://release-monitoring.org/

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Aug 28, 2023 at 5:29 AM Ryan Bach via devel
<devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> Faster updates are always as plus.

There's a problem with an approach like this: You need to check
*manually* that the new version builds and doesn't violate any of our
policies, for example, that it doesn't contain any prohibited items
(like new code or content that's under non-FOSS / non-commercial /
non-redistributable licenses).

For projects where the people who are responsible for the upstream
project are the same people who maintain the Fedora package, this is
mostly a non-issue - and for these cases, there's Packit [0] (which I
think does what you are looking for).

Fabio

[0]: https://packit.dev
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux