Re: Copr Build System - review of 2019 and vote for features in 2020

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

 



On Mon, Feb 10, 2020 at 01:46:14AM -0700, John M. Harris Jr wrote:

> So long as people are willing to maintain it, why restrict peoples' ability to 
> work on something, especially while users are stuck on that version, or forced 
> to move elsewhere if they cannot get a fix and cannot upgrade?

A nummber of reasons: 

Resources: 
* storage space on fast storage instead of archives
* mirror space
* signing cycles
* build cycles
* compose cycles

False sense of security: Something might be updated because the maintainer wants
to keep it up to date there, but no one else does so 30 other things are
inscure/broken, making users thing things are up to date when they are
not. 

You would have to have some way to allow feedback/bug reports only to
those people who are wanting to keep it alive, while not bothering
people who don't wish to. 

kevin

Attachment: signature.asc
Description: PGP signature

_______________________________________________
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