Return release milestones in predictable order
What does this MR do?
Fixes #259012 (closed) by adding an explicit order to the milestones returned through the release REST and GraphQL APIs. Also removes a number of testing workarounds that were caused by this bug.
Previously, the milestones were not sorted, so their order was non-deterministic (which made testing a challenge).
Now, the milestones are sorted like this:
- by
due_date
, earliest first (withNULL
values sorted last), then - by
start_date
, earliest first (withNULL
values sorted last), then - by
title
, alphabetically
Related to #259012 (closed)
Edited by Nathan Friend