On Mon, 23.02.15 08:52, Simo Sorce (simo@xxxxxxxxxx) wrote: > On Mon, 2015-02-23 at 14:40 +0100, drago01 wrote: > > On Mon, Feb 23, 2015 at 2:17 PM, David Cantrell <dcantrell@xxxxxxxxxx> wrote: > > > That is, and I am trying to > > > be specific here, changes that impact other components in the distribution > > > need to be coordinated in Fedora among the affected components. > > > > Almost every change might "affect other components" ... it might be > > obvious to a maintainer of an affected component but not necessarily > > for the maintainer / developer of the component that got changed. > > Which is why you should send a message to a general development list for > changes that change the semantics of a well established mechanism. > > If you are changing something internal to your software then the burden > of keeping up is with the downstream people that may decide to depend on > internal features (assuming private/public interfaces are clearly > defined). > > If you are changing something in the system public interfaces, instead a > bit more general and advance notice is necessary. The /etc/os-release to /usr/lib/os-release is hardly a change in the public interface, it keeps compat by leaving a symlink in /etc. And jeezuz, I didn't push this change into Fedora. Other people did, without talking to me. Really, this is neither much of a compat break, nor is this something I even knew about. Really, find something else to complain about. Lennart -- Lennart Poettering, Red Hat -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
