On Wed, Sep 10, 2008 at 6:47 PM, Assaf Arkin <[EMAIL PROTECTED]> wrote: >>> 4. Maintain specs/tests for both new and deprecated behavior, until >>> deprecated behavior has been removed. >> >> To document this, I suggest we add expectations in our specs. >> >> E.g., >> >> it 'should do a deprecated behavior' do >> Buildr.VERSION.should < '1.5' >> ... >> end >> >> That way, when we reach version 1.5, we'll know automatically what >> needs to be removed. :-) > > +1 (we should add this to all the 1.2.x deprecated features if we can > remember what they are)
I added my first deprecation test at revision 703850 on trunk. If I get positive feed back on this, I'll keep adding this kind of tests. Lacton
