atom feed14 messages in org.apache.incubator.callback-devRE: Decreasing the Deprecation Time
FromSent OnAttachments
Joe BowserMar 12, 2013 3:14 pm 
Anis KADRIMar 12, 2013 3:23 pm 
Brian LeRouxMar 12, 2013 3:59 pm 
Tommy-Carlos WilliamsMar 12, 2013 5:06 pm 
Braden ShepherdsonMar 13, 2013 7:44 am 
Lorin BeerMar 13, 2013 7:45 am 
Michal MocnyMar 13, 2013 8:32 am 
ShazronMar 13, 2013 11:28 am 
Simon MacDonaldMar 13, 2013 7:09 pm 
Michael BrooksMar 14, 2013 8:02 pm 
Tommy-Carlos WilliamsMar 14, 2013 8:31 pm 
Marcel KinardMar 15, 2013 6:24 am 
Ken WallisMar 15, 2013 7:25 am 
Anis KADRIMar 15, 2013 8:07 am 
Subject:RE: Decreasing the Deprecation Time
From:Ken Wallis (
Date:Mar 15, 2013 7:25:42 am

We will definitely care as well as we move directly on top of Cordova. Cordova
is being adopted more and more as a platform that others will build on. A
certain level of predictability and stability in a platform is certainly
appreciated at least. ;)

We will be heavily invested in the plug-in approach here at BlackBerry so that
is of special concern if it is unstable.


Ken Wallis

Product Manager – WebWorks



________________________________________ From: Marcel Kinard [] Sent: Friday, March 15, 2013 9:24 AM To: Subject: Re: Decreasing the Deprecation Time

On Mar 14, 2013, at 11:02 PM, Michael Brooks <> wrote:

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

I care. Or in other words, the users of my product (which embeds Cordova) care.
I get yelled at by my users when their app breaks when doing an in-place upgrade
from version n-3 to n of Cordova.

-- Marcel