> Given this behavior is described in published documentation, is there any reason to keep the bug private?
I think some of this behaviour, eg: A non-admin user can modify public images and inject locations pointing to dangerous images.
Is not publically documented. I'd hold off on marking public until we get a chance to digest the various possible behaviours.
> 1) Whenever an image is left without locations, it should be moved to 'deleted'
What about forbidding removal of the last location? It may be a bit surprising if your image disappears without doing an explicit image delete.
(If your image has only one location and you want to remove that location then delete the image.)
> Given this behavior is described in published documentation, is there any reason to keep the bug private?
I think some of this behaviour, eg:
A non-admin user can modify public images and inject locations pointing to dangerous images.
Is not publically documented. I'd hold off on marking public until we get a chance to digest the various possible behaviours.
> 1) Whenever an image is left without locations, it should be moved to 'deleted'
What about forbidding removal of the last location? It may be a bit surprising if your image disappears without doing an explicit image delete.
(If your image has only one location and you want to remove that location then delete the image.)