+1 for switching the deprecation window from time to release. Michal summed it up perfectly.
It's worth reflecting on Tommy and Simon's input. The deprecation window is there to give users adequate warning that breakage is impending. However, it's just make-work for us, if our user's don't care or take action. On Wed, Mar 13, 2013 at 7:09 PM, Simon MacDonald <simon.macdon...@gmail.com>wrote: > On Tue, Mar 12, 2013 at 8:06 PM, Tommy-Carlos Williams > <to...@devgeeks.org> wrote: > > > > No one sees a deprecation warning and thinks "ooh… better not use > that…", they say "a warning is not an error" and move on with their project. > > What I find incredibly weird is no one cares about our deprecation > method but god forbid your Android Java code is using a deprecated > method or constant. I've been contacted by users days after a new > Android version drops asking to get rid of the deprecated methods. > > Simon Mac Donald > http://hi.im/simonmacdonald >
