How to submit refactorings (or: Removing PWS)

Julian Fitzell julian at beta4.com
Sat Nov 16 09:53:52 UTC 2002


Sure, sounds good.  It sounds like there is some disagreement regarding 
timeframe for removing it from the update stream... but I suspect that 
is irrelevant at this juncture :)  We can worry about that once we have 
a bunch of packages created.

Julian

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.
>
> Daniel



-- 
julian at beta4.com
Beta4 Productions (http://www.beta4.com)




More information about the Squeak-dev mailing list