Comment 4 for bug 413174

The assertion message in this case is an instruction to the engineer that he has not read the documentation. It should be a statement like "You cannot create a release for a milestone that already has one." It is possible for a engineer to have decided to interpolate a private information and a reviewer approved it, but this can also be said about emails and notifications. AssertionErrors are not assumed to be about data, but contract violation.