On Wed, Feb 28, 2018 at 7:46 AM, Kevin Kofler <kevin.kofler@xxxxxxxxx> wrote:
The requirement to announce soname bumps to begin with is unreasonable
bureaucracy in the first place. If your package shows up in the broken
dependency report, you rebuild it and move on, where is the problem?
I'm going to respectfully disagree here. Strong and resilient communities learn to communicate well, and this communication helps to avoid problems, conflicts, and resentment. Even if we didn't have this rule, it would be common courtesy to announce any change that causes others to have to do work, even if it's only for a few users.
I'll paraphrase a mantra that I learned from Greg DeKoenigsberg, which says that "In communities, it's okay to be disappointed, but it's not okay to be surprised." I personally feel that we'd be a stronger community if we all focused a bit more on the principle of "least surprise".
--
I'll paraphrase a mantra that I learned from Greg DeKoenigsberg, which says that "In communities, it's okay to be disappointed, but it's not okay to be surprised." I personally feel that we'd be a stronger community if we all focused a bit more on the principle of "least surprise".
--
Jared Smith
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
