We missed one step when designing / discussing package renames. We have
OBSOLETED_BY_ which creates stubs. This is good, but what about removing
stubs?

Turns out the stubs are best removed from build recipes immediately after
the first upload.

We don't have a check that prevents a useless stub from being uploaded. For
now, every time you work with a package and you see a stub / OBSOLETED_BY_
that has been previously uploaded, remove it from the recipe.

Maciej

Reply via email to