Re: Decreasing the Deprecation Time

[Shazron <sh...@gmail.com>]

Since this has gone through the 48 month cooling off period (stole that
line from Jesse who brought this up when cleaning the Wiki), I think by
consensus, as originally proposed by Joe, the deprecation period is now 3
releases instead of 6 months. Finally, we can put this issue behind us!

On Fri, Mar 15, 2013 at 8:07 AM, Anis KADRI <an...@gmail.com> wrote:

> To Tommy-Carlos' point, I believe plugins (or the plugin interface) will
> unlikely break when we get closer to 3.0. Reason is: if the plugin
> interface breaks then everything will break :-D We certainly don't want
> that.
>
>
> On Fri, Mar 15, 2013 at 7:25 AM, Ken Wallis <kw...@blackberry.com>
> wrote:
>
> > 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
> >
> > BlackBerry
> >
> > 289-261-4369
> >
> > ________________________________________
> > From: Marcel Kinard [cmarcelk@gmail.com]
> > Sent: Friday, March 15, 2013 9:24 AM
> > To: dev@cordova.apache.org
> > Subject: Re: Decreasing the Deprecation Time
> >
> > On Mar 14, 2013, at 11:02 PM, Michael Brooks <mi...@michaelbrooks.ca>
> > wrote:
> >
> > > +1 for switching the deprecation window from time to release. Michal
> > summed
> > > it up perfectly.
> >
> > Agreed.
> >
> > >
> > > 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
> >
> > ---------------------------------------------------------------------
> > This transmission (including any attachments) may contain confidential
> > information, privileged material (including material protected by the
> > solicitor-client or other applicable privileges), or constitute
> non-public
> > information. Any use of this information by anyone other than the
> intended
> > recipient is prohibited. If you have received this transmission in error,
> > please immediately reply to the sender and delete this information from
> > your system. Use, dissemination, distribution, or reproduction of this
> > transmission by unintended recipients is not authorized and may be
> unlawful.
> >
>

Re: Decreasing the Deprecation Time

[Shazron <sh...@gmail.com>]

For those that don't have the original thread:
https://lists.apache.org/thread.html/f36ca4df2e8d4f1713e02daa2f9b91552779fd3dea1bea430019a8dc@1363226956@%3Cdev.cordova.apache.org%3E

On Mon, Mar 13, 2017 at 2:29 PM, Shazron <sh...@gmail.com> wrote:

> Since this has gone through the 48 month cooling off period (stole that
> line from Jesse who brought this up when cleaning the Wiki), I think by
> consensus, as originally proposed by Joe, the deprecation period is now 3
> releases instead of 6 months. Finally, we can put this issue behind us!
>
> On Fri, Mar 15, 2013 at 8:07 AM, Anis KADRI <an...@gmail.com> wrote:
>
>> To Tommy-Carlos' point, I believe plugins (or the plugin interface) will
>> unlikely break when we get closer to 3.0. Reason is: if the plugin
>> interface breaks then everything will break :-D We certainly don't want
>> that.
>>
>>
>> On Fri, Mar 15, 2013 at 7:25 AM, Ken Wallis <kw...@blackberry.com>
>> wrote:
>>
>> > 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
>> >
>> > BlackBerry
>> >
>> > 289-261-4369
>> >
>> > ________________________________________
>> > From: Marcel Kinard [cmarcelk@gmail.com]
>> > Sent: Friday, March 15, 2013 9:24 AM
>> > To: dev@cordova.apache.org
>> > Subject: Re: Decreasing the Deprecation Time
>> >
>> > On Mar 14, 2013, at 11:02 PM, Michael Brooks <mi...@michaelbrooks.ca>
>> > wrote:
>> >
>> > > +1 for switching the deprecation window from time to release. Michal
>> > summed
>> > > it up perfectly.
>> >
>> > Agreed.
>> >
>> > >
>> > > 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
>> >
>> > ---------------------------------------------------------------------
>> > This transmission (including any attachments) may contain confidential
>> > information, privileged material (including material protected by the
>> > solicitor-client or other applicable privileges), or constitute
>> non-public
>> > information. Any use of this information by anyone other than the
>> intended
>> > recipient is prohibited. If you have received this transmission in
>> error,
>> > please immediately reply to the sender and delete this information from
>> > your system. Use, dissemination, distribution, or reproduction of this
>> > transmission by unintended recipients is not authorized and may be
>> unlawful.
>> >
>>
>
>