danielv at netvision.net.il wrote:
> If think we are in violent agreement then. Lets review -
> 
> * Code is refactored to make a complete package that requires no other
> code changes to load/unload.
> * Refactoring is posted for feedback (on list or SM) as needed.
> * When it's acceptable the code is inserted into update stream, so that
> code becomes removable using "remove category" in the simple case or DVS
> if there are class extensions.
> Then (Some unspecified time after the package starts living in SM...)
> * Update is issued that performs the remove, asking the user if he wants
> to reload from SM, or leave his version loaded (in case he has
> modifications).
> 
> Comments?
> 
> If none and the it's ratified by the Guides, this will become our
> current policy for removing things from the image, and I'll put it on
> the swiki and expand on the details, and we'll do it to PWS first, and then
> to whatever we get good unload code for.

Sounds like a good plan to me. I can add category "Package type" with
subcats "Image removal" and "Image refactoring".

regards, Göran