Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of mmocny@google.com designates
 209.85.223.172 as permitted sender)
MIME-Version: 1.0
Sender: mmocny@google.com
In-Reply-To: <D0503AEA.13F7B%raycamde@adobe.com>
References: <A8E4AD2B355CD049BD344F31968121DE27630F52@SYD1214>
 <CAE6O_-YNYYBhz-B90BT+1g0mqK+NA60CXZ5qYgs1JAsOTspO4A@mail.gmail.com>
 <A8E4AD2B355CD049BD344F31968121DE27630FAC@SYD1214>
 <CAE6O_-bSADuT5ASFRM+JSpjeHO6X-UsFxQQxeh4SEhnrXHucmg@mail.gmail.com>
 <A8E4AD2B355CD049BD344F31968121DE27631A50@SYD1214>
 <CAE6O_-YdCsNn2J6UbksgSTF3aQyQd8kzoBBuz-XnncgYguX72A@mail.gmail.com>
 <D050251F.13F6D%raycamde@adobe.com>
 <CAE6O_-auxYmBOaxkG9fkPZEEYK3YYHHkud2DkkDY7E50gZ9nSQ@mail.gmail.com>
 <D0503AEA.13F7B%raycamde@adobe.com>
From: Michal Mocny <mmocny@chromium.org>
Date: Tue, 30 Sep 2014 11:59:44 -0400
Message-ID: 
 <CAEeF2TddepfOvWjbf_z9C-xGQLLc7nWZ7YpFo3ZiaN0mUVtmdQ@mail.gmail.com>
Subject: Re: 3.6 cordova plugin versions
To: dev <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=047d7bd76d10fb04e905044a79c0

--047d7bd76d10fb04e905044a79c0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Paul:

You are right.  When we do a platform release, we test with the latest
plugins to make sure the platform isn't breaking things.  When we do a
plugins release, we test with the latest platforms to make sure the plugins
are breaking things.

In theory, we should know when plugins depend on a certain minimum platform
version, and even have a plugin.xml tag to specify this (<engine>), though
its a bit indirect and in practice I'm not sure that the requirements are
well specified (many plugins just say >=3D 3.0.0).


I think whether you consider this a problem depends a bit on your workflow
and cordova development philosophy.  Namely, do you make any native
platform changes directly in platforms/?  If so, upgrading to the latest of
everything all the time is a burden, and you may want well specified
compatibility.  On the other hand, if your platforms/ are treated as build
artefacts, and all your work is in hooks/ plugins/ and www/, its quite
trivial to upgrade platforms, sample different plugin versions, and
experiment.

In theory, we want to support both flows.  In practice, its quite tedious
and relies on plugin authors to put in the legwork, which doesn't usually
happen.  If you were interested in testing plugins on older cordova
platform versions, or perhaps you already maintain a list, that would be
useful to share with us.  However long term, I'd personally prefer to see
people less hesitant to just upgrade often, and that has certainly been the
trend.

-Michal

On Tue, Sep 30, 2014 at 11:48 AM, Ray Camden <raycamde@adobe.com> wrote:

> Just being annoying. ;) I can see this type of question though being
> something users will bring up.
>
> On 9/30/14, 9:46 AM, "Shazron" <shazron@gmail.com> wrote:
>
> >He didnt ask that question, but Ray: yes.
> >
> >On Tuesday, September 30, 2014, Ray Camden <raycamde@adobe.com> wrote:
> >
> >> Does it make sense to clarify that statement though? Not *every* plugi=
n
> >>is
> >> tested like this, just the =C2=B3Core=C2=B2 set of Cordova plugins. If=
 someone
> >>has a
> >> random plugin for Cowbell, there is no guarantee that it will work on
> >> _any_ release, right? (I know we were talking about core plugins, but =
I
> >> just wanted to be sure.)
> >>
> >>
> >> On 9/30/14, 9:04 AM, "Shazron" <shazron@gmail.com <javascript:;>>
> wrote:
> >>
> >> >
>
>

--047d7bd76d10fb04e905044a79c0--