We know Ubuntu wants this behavior. We are less confident that other projects will.
Francis suggested feature flags as an initial cut for a distinguishing mechanism. I think we could do this by, for instance, looking for a feature flag that specifies a comma-separated whitelist of projects that want this behavior. After this is deployed and configured for Ubuntu, we can then decide if we should apply this policy to all projects, if we should make it opt-in or opt-out, and if we should make it configurable. A particularly nice thing about this approach is that we can deploy the change in a no-downtime deployment, as early as possible, for Ubuntu; and then other opt-in/opt-out choices that require a database change can be pushed out to a db change/downtime deployment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/777874 Title: If multiple reports on new bug, mark it confirmed To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/777874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs