On Thu, Apr 04, 2019 at 09:24:13AM -0400, Stephen Gallagher wrote: > > Without naming them, I see two different use cases: > > 1/ "for end users" — rolling stream meant for end users to consume, likely used in projects without traditional versioning scheme, or for the latest version that the Fedora's "cutting edge but not bleeding edge" > > Many golang packages do not do traditional releases, but instead > generally assume that the user will pull the latest git master branch > and use that. Since upstream intends that usage, I think it falls into > this category. Here's a wrinkle on this. When this is the case upstream, we almost certainly want to provide some stream following that, but we may also want to provide a more cautious stream. That could be either pinning to an older release or snapshot and backporting selected fixes, or it could simply mean a stream which updates to get those selected fixes but on a slower cadence and not automatically. One package I maintain has fairly frequent point releases, but those are generally extremely trivial bugfixes affecting very little real world use. It would be easy to have a "stable" stream which opts to not pick these up for cases where reduced churn is more important than the obscure fixes. -- Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
