Re: Defining the future of the packager workflow in Fedora

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

 



On 9/26/19 8:42 AM, Pierre-Yves Chibon wrote:
Again, I'd like to reinforce that the idea is not to enforce any part of this
workflow tomorrow, it'll be a smooth, slow and long transition. My question is
whether this is a place where we want to go or can we come up with a
different/better one?:)

The problem with this statement is that this is written as "come up with something different or else we're doing it my way anyway" and not "ok, we'll not do this."

I don't want a build for every commit. Sometimes I cache changes for future releases. A commit does *not* always equal an update. This proposed workflow model doesn't help me. It hurts. It makes me think of dropping my roles from Fedora.

With that said I believe there are some good parts to it, but the PR for everything and builds for every commit are show-stoppers.
_______________________________________________
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