We have the packit even recommended in the-new-hotness documentation
(it's the application responsible for creating tickets in bugzilla when
release-monitoring.org finds new version).
https://the-new-hotness.readthedocs.io/en/stable/user-guide.html#opening-pull-requests-in-dist-git
Michal
On
> On Mon, Aug 28, 2023 at 5:29 AM Ryan Bach via devel
>
> 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
Hello,
as Fabio has pointed out, you can use Packit to get your releases to
Fedora via pull-requests. Packit supports both push and newly also
pull workflow. (So you don't need to have access to the upstream
repository because it gets the info about the new version from Release
Monitoring.)
On Mon, 2023-08-28 at 13:52 +0100, Sérgio Basto wrote:
> On Mon, 2023-08-28 at 03:28 +, Ryan Bach via devel wrote:
> > Faster updates are always as plus.
> >
> > Should this be under infrastructure list?
> >
> > Thoughts?
> >
>
> if you got a scratch build completed in a bugzilla for
On Mon, 2023-08-28 at 03:28 +, Ryan Bach via devel wrote:
> Faster updates are always as plus.
>
> Should this be under infrastructure list?
>
> Thoughts?
>
if you got a scratch build completed in a bugzilla for example :
https://bugzilla.redhat.com/show_bug.cgi?id=2231971
you may use
On Mon, Aug 28, 2023 at 5:29 AM Ryan Bach via devel
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
Faster updates are always as plus.
Should this be under infrastructure list?
Thoughts?
Thanks in advance for all the work done to make this distro great.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
