"Push to stable" on an obsolete update submits to testing; should not be submitted at all #848
On an obsolete update, there is still a "Push to stable" option. If I do a push to stable, the update is submitted to testing instead. This leads to two different updates (the new update and the obsolete update) for the same package pending for testing.
How to reproduce:
Some error message, e.g. "This update is obsolete and cannot be submitted to stable".
Update 1 will be submitted to testing instead. Both updates are now pending for testing.
There can be two possible solutions.
@lmacken Which one should we go for?