policy on changes in or introduction of new dependencies

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

 



Dear Fedora developers,
there have been a number of examples where an update in a stable branch
brought in new dependencies and in significant numbers. The most recent
case was discussed on this list even today:
https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/BVUZWJYW2UVO53EZ2G2ALAQPU5PLDJZR/

I opened a ticket with FESCo to clarify the Updates Policy:
https://pagure.io/fesco/issue/1682

In particular, I propose:
* Mandating that all dependency changes in package updates must be
  mentioned in the package's %changelog and justified.

* Mandating that all dependency changes in package updates in a stable
  release MUST be mentioned in bodhi update release notes and justified.

* Adding this to https://fedoraproject.org/wiki/Updates_Policy#All_other_updates
  * Avoid updates that introduce any new dependencies

Thoughts?

Regards,
Dominik

-- 
Fedora http://fedoraproject.org/wiki/User:Rathann
RPMFusion http://rpmfusion.org
"Faith manages."
        -- Delenn to Lennier in Babylon 5:"Confessions and Lamentations"
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [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