On Fri, Jul 12, 2013 at 09:57:04PM +0200, lee wrote: > The upgrade from 17 to 18 silently broke apache because the > configuration had changed. That is something that shouldn't happen, the > devs know when there are changes like that and make sure the users are > informed accordingly. > Where/how do you make suggestions like that? We try to. That's part of the change process. Fedora, as a fast moving distribution, doesn't make any promises that new versions will be backwards compatible like that, but of course we try to minimize the pain where possible and where it's reasonable given the upstream package. If there is an incompatible change, we do try to make users aware and put it in the release notes, or at least in the "common bugs" list after the fact. Software is complicated and configuration possibilities infinite, so it's not actually aways known when upgrades will have an impact. But we try. -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm@xxxxxxxxxxxxxxxxx> -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
