The ubuntu community's systematic approach to prevent unintended consequences is well conceived and implemented. But no one plan is flawless and every good plan should have a contingency. This thread documents a years worth of history showing a very important component getting hung up in a well-intentioned process; causing server security issues to persist, significant advances to not be implemented and a loss of marketshare to competitors. Please be open to discussing a contingency among the ubuntu core team.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/939300 Title: Update Apache to 2.4 To manage notifications about this bug go to: https://bugs.launchpad.net/raringautomatedsuggestions/+bug/939300/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
