Masterview devel - Oct 2006 - Well enough with my goofing around, I am going to go through and shore up the release notes for a release this weekend

> > I was thinking about renaming the directive_base_old.rb to
deprecated_directive_base.rb,  
>> this seems to be how they do it on the rails edge. Seem ok to you? 
>> It is clear about its status and then easy to find when we want to
remove
later. 
 
Yes.  I''d almost go further and put it completely on the side (e.g.
separate
deprecated subdir or something like that), with upgrade instructions on what
to require in legacy code.  This is fairly aggressive and not necesssarily a
technique I''d advocate at a more mature level of the life cycle, but
it''s
already that case that an existing impl would need to be touched to change
the superclass name, so asking them to do an explicit compat require
isn''t
that much more of a burden.
 
And  given the small size of the impacted clients and the huge improvement
of the new facility, I think it''s ok to be fairly agressive about
accepting
some breakage right now.
 
We should flag this very clearly in the release information, noting that it
deviates from desirable policy of not causing breakage, and ask for pushback
from users think we''ve gone too far at pushing burden onto them, but I
think
this will be acceptable.
 
~ Deb
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/masterview-devel/attachments/20061027/18cece46/attachment.html