Third option: Tell users who are bothered by this misfeature to upgrade to Xenial. "I don't like these ports being in use" isn't a bug, per se, and our goal should not be to backport exact feature parity from Xenial to Trusty. We release new releases for a variety of reasons, and this is one of them.
I understand the compulsion to always make every LTS "look and behave the same", but there are points of diminishing returns, and this is one of them. To quote pitti (on another backporting topic), "if this is really what we want, why don't we just symlink trusty to xenial?"
If there was a bug to be fixed here, sure, let's fix it, but I don't see one worth fixing. Long-time trusty users have been at this for over 2.5 years, and I don't see a flood of people complaining about these random ports, while Xenial has been out for over half a year now, and the few people genuinely irritated can, well, use Xenial.
Third option: Tell users who are bothered by this misfeature to upgrade to Xenial. "I don't like these ports being in use" isn't a bug, per se, and our goal should not be to backport exact feature parity from Xenial to Trusty. We release new releases for a variety of reasons, and this is one of them.
I understand the compulsion to always make every LTS "look and behave the same", but there are points of diminishing returns, and this is one of them. To quote pitti (on another backporting topic), "if this is really what we want, why don't we just symlink trusty to xenial?"
If there was a bug to be fixed here, sure, let's fix it, but I don't see one worth fixing. Long-time trusty users have been at this for over 2.5 years, and I don't see a flood of people complaining about these random ports, while Xenial has been out for over half a year now, and the few people genuinely irritated can, well, use Xenial.