Re: Defining the future of the packager workflow in Fedora

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

 



On Thu, 2019-09-26 at 14:49 +0000, Jeremy Cline wrote:
> > ○ Every commit to dist-git (ie: PR merged) is automatically built
> > in koji
> > ○ Every build in koji results automatically in an update in bodhi
> 
> The combination of these two makes no sense to me. I do plenty of
> work
> where I don't want to build it (specfile cleanup, patches,
> configuration
> changes, etc.). I want a build that goes to users be explicit.

This is also a problem for multi-package updates. I frequently do chain
builds for changes that must go out together. It would be bad if one
went out and another didn't. Also, the tests won't pass on some of
them, which will guarantee that some will go out without the others.

Sending builds to users should be explicit.

Also, I don't see value in making builds that don't go to users, and
doing that consumes resources.

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
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

[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