You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by "Joshi, Pavankumar" <Jo...@fast.au.fujitsu.com> on 2014/09/29 06:48:19 UTC
3.6 cordova plugin versions
Hello devs,
Kindly clarify our doubt. It’s a blocker issue for us.
Regarding 3.6 release, which versions of plugins should we use?
In the News page of Apache Cordova 3.6 release, http://cordova.apache.org/announcements/2014/09/22/cordova-361.html, the versions of plugins, for example cordova-plugin-battery-status and cordova-plugin-vibration are 0.2.10 and 0.3.10 respectively.
But on 22 September versions of all plugins were incremented by 1.
Now in Apache Cordova plugin documentation, if I go to plugins and click on vibration plugin of 3.6.0 release, http://cordova.apache.org/docs/en/3.6.0/cordova_plugins_pluginapis.md.html#Plugin%20APIs I get the description as tagged in 0.3.11 and not as explained in 0.3.10.
Please let me know which versions of plugins should be considered as 3.6.0 Cordova release.
Thanks and Regards
Pavan Joshi
RE: 3.6 cordova plugin versions
Posted by "Joshi, Pavankumar" <Jo...@fast.au.fujitsu.com>.
Thank you very much for the information.
Regards
Pavan Joshi
-----Original Message-----
From: Shazron [mailto:shazron@gmail.com]
Sent: Monday, 29 September 2014 4:59 PM
To: dev@cordova.apache.org
Subject: Re: 3.6 cordova plugin versions
Plugins are independently released and not tied to a particular version.
That just shows it was tested with that version.
Just use the latest versions.
On Sun, Sep 28, 2014 at 11:41 PM, Joshi, Pavankumar < JoshiP@fast.au.fujitsu.com> wrote:
> Sorry, But then why the news section of plugins,
> http://cordova.apache.org/announcements/2014/09/22/cordova-361.html,
> still has an older version?
> In Cordova 3.6 release page it says
>
> Plugin versions tested with this release
>
> cordova-plugin-battery-status: 0.2.10
> cordova-plugin-camera: 0.3.1
> cordova-plugin-console: 0.2.10
> cordova-plugin-contacts: 0.2.12
> cordova-plugin-device: 0.2.11
> cordova-plugin-device-motion: 0.2.9
> cordova-plugin-device-orientation: 0.3.8
> cordova-plugin-dialogs: 0.2.9
> cordova-plugin-file: 1.3.0
> cordova-plugin-file-transfer: 0.4.5
> cordova-plugin-geolocation: 0.3.9
> cordova-plugin-globalization: 0.3.0
> cordova-plugin-inappbrowser: 0.5.1
> cordova-plugin-media: 0.2.12
> cordova-plugin-media-capture: 0.3.2
> cordova-plugin-network-information: 0.2.11
> cordova-plugin-splashscreen: 0.3.2
> cordova-plugin-statusbar: 0.1.7
> cordova-plugin-vibration: 0.3.10
>
> are plugins latest version for example cordova-plugin-battery-status:
> 0.2.11 is tested with 3.6?
>
> Regards
> Pavan Joshi
>
>
> -----Original Message-----
> From: Shazron [mailto:shazron@gmail.com]
> Sent: Monday, 29 September 2014 4:20 PM
> To: dev@cordova.apache.org
> Subject: Re: 3.6 cordova plugin versions
>
> Always use the latest.
>
> On Sun, Sep 28, 2014 at 9:48 PM, Joshi, Pavankumar <
> JoshiP@fast.au.fujitsu.com> wrote:
>
> > Hello devs,
> >
> > Kindly clarify our doubt. It’s a blocker issue for us.
> >
> > Regarding 3.6 release, which versions of plugins should we use?
> > In the News page of Apache Cordova 3.6 release,
> > http://cordova.apache.org/announcements/2014/09/22/cordova-361.html,
> > the versions of plugins, for example cordova-plugin-battery-status
> > and cordova-plugin-vibration are 0.2.10 and 0.3.10 respectively.
> > But on 22 September versions of all plugins were incremented by 1.
> > Now in Apache Cordova plugin documentation, if I go to plugins and
> > click on vibration plugin of 3.6.0 release,
> > http://cordova.apache.org/docs/en/3.6.0/cordova_plugins_pluginapis.md.
> > html#Plugin%20APIs I get the description as tagged in 0.3.11 and not
> > as explained in 0.3.10.
> > Please let me know which versions of plugins should be considered as
> > 3.6.0 Cordova release.
> >
> > Thanks and Regards
> > Pavan Joshi
> >
> >
> >
>
Re: 3.6 cordova plugin versions
Posted by Michal Mocny <mm...@chromium.org>.
Just add a quick comment as well.
On Wed, Oct 1, 2014 at 10:40 AM, Ray Camden <ra...@adobe.com> wrote:
> oh - I didn’t see your comment Shaz. Thanks!
>
>
> On 10/1/14, 9:33 AM, "Ray Camden" <ra...@adobe.com> wrote:
>
> >No one complained, so I assume it is perfect. ;) Seriously though - feel
> >free to comment on the blog if you have suggestions.
> >
> >On 9/30/14, 4:35 PM, "Ray Camden" <ra...@adobe.com> wrote:
> >
> >>Any comments folks?
> >>
> >>https://gist.github.com/cfjedimaster/b689cbf528cddaa2391a
> >>
> >>
> >>On 9/30/14, 11:57 AM, "Michal Mocny" <mm...@chromium.org> wrote:
> >>
> >>>I'm not an expert on <engine> requirements, but I'm happy to review your
> >>>post.
> >>>
> >>>-Michal
> >>>
> >>>On Tue, Sep 30, 2014 at 12:41 PM, Ray Camden <ra...@adobe.com>
> wrote:
> >>>
> >>>> Ah, good point there.
> >>>>
> >>>> I¹m going to write up a blog post on this after I run some errands.
> >>>>I¹d
> >>>> love a quick review from you, or anyone, before I publish. I¹m also
> >>>>going
> >>>> to add something to the core docs.
> >>
> >
>
>
Re: 3.6 cordova plugin versions
Posted by Ray Camden <ra...@adobe.com>.
oh - I didn’t see your comment Shaz. Thanks!
On 10/1/14, 9:33 AM, "Ray Camden" <ra...@adobe.com> wrote:
>No one complained, so I assume it is perfect. ;) Seriously though - feel
>free to comment on the blog if you have suggestions.
>
>On 9/30/14, 4:35 PM, "Ray Camden" <ra...@adobe.com> wrote:
>
>>Any comments folks?
>>
>>https://gist.github.com/cfjedimaster/b689cbf528cddaa2391a
>>
>>
>>On 9/30/14, 11:57 AM, "Michal Mocny" <mm...@chromium.org> wrote:
>>
>>>I'm not an expert on <engine> requirements, but I'm happy to review your
>>>post.
>>>
>>>-Michal
>>>
>>>On Tue, Sep 30, 2014 at 12:41 PM, Ray Camden <ra...@adobe.com> wrote:
>>>
>>>> Ah, good point there.
>>>>
>>>> I¹m going to write up a blog post on this after I run some errands.
>>>>I¹d
>>>> love a quick review from you, or anyone, before I publish. I¹m also
>>>>going
>>>> to add something to the core docs.
>>
>
Re: 3.6 cordova plugin versions
Posted by Ray Camden <ra...@adobe.com>.
No one complained, so I assume it is perfect. ;) Seriously though - feel
free to comment on the blog if you have suggestions.
On 9/30/14, 4:35 PM, "Ray Camden" <ra...@adobe.com> wrote:
>Any comments folks?
>
>https://gist.github.com/cfjedimaster/b689cbf528cddaa2391a
>
>
>On 9/30/14, 11:57 AM, "Michal Mocny" <mm...@chromium.org> wrote:
>
>>I'm not an expert on <engine> requirements, but I'm happy to review your
>>post.
>>
>>-Michal
>>
>>On Tue, Sep 30, 2014 at 12:41 PM, Ray Camden <ra...@adobe.com> wrote:
>>
>>> Ah, good point there.
>>>
>>> I¹m going to write up a blog post on this after I run some errands. I¹d
>>> love a quick review from you, or anyone, before I publish. I¹m also
>>>going
>>> to add something to the core docs.
>
Re: 3.6 cordova plugin versions
Posted by Ray Camden <ra...@adobe.com>.
Any comments folks?
https://gist.github.com/cfjedimaster/b689cbf528cddaa2391a
On 9/30/14, 11:57 AM, "Michal Mocny" <mm...@chromium.org> wrote:
>I'm not an expert on <engine> requirements, but I'm happy to review your
>post.
>
>-Michal
>
>On Tue, Sep 30, 2014 at 12:41 PM, Ray Camden <ra...@adobe.com> wrote:
>
>> Ah, good point there.
>>
>> I¹m going to write up a blog post on this after I run some errands. I¹d
>> love a quick review from you, or anyone, before I publish. I¹m also
>>going
>> to add something to the core docs.
Re: 3.6 cordova plugin versions
Posted by Shazron <sh...@gmail.com>.
Thanks Ray! That would be great.
I concur with what Michal said. Unfortunately, testing with older releases
hasn't been our focus (resources and whatnot).
On Tue, Sep 30, 2014 at 9:57 AM, Michal Mocny <mm...@chromium.org> wrote:
> I'm not an expert on <engine> requirements, but I'm happy to review your
> post.
>
> -Michal
>
> On Tue, Sep 30, 2014 at 12:41 PM, Ray Camden <ra...@adobe.com> wrote:
>
> > Ah, good point there.
> >
> > I¹m going to write up a blog post on this after I run some errands. I¹d
> > love a quick review from you, or anyone, before I publish. I¹m also going
> > to add something to the core docs.
> >
> >
> > On 9/30/14, 11:18 AM, "Michal Mocny" <mm...@chromium.org> wrote:
> >
> > >That sounds reasonable.
> > >
> > >The <engine> tag is a bit weird though, in that the dependency is on cli
> > >and not platform version. Combined with CLI semver and platform release
> > >unbundling, its a bit hard to reason about. It kinda still works
> because
> > >we have default platform versions pinned to cli versions, but users can
> > >explicitly install non-default platform versions if they chose, and
> > >plugins
> > >may have support for only a subset of platforms..
> > >
> > >-Michal
> > >
> > >On Tue, Sep 30, 2014 at 12:11 PM, Ray Camden <ra...@adobe.com>
> wrote:
> > >
> > >> Ah - never mind. I picked a plugin that didn¹t have it specified. I
> > >>picked
> > >> another random one and it *was* shown.
> > >>
> > >> I¹d say that for plugins w/o engine support, the site should still say
> > >> something, even if
> > >>
> > >> Engine Number
> > >> Not Specified
> > >>
> >
> >
>
Re: 3.6 cordova plugin versions
Posted by Michal Mocny <mm...@chromium.org>.
I'm not an expert on <engine> requirements, but I'm happy to review your
post.
-Michal
On Tue, Sep 30, 2014 at 12:41 PM, Ray Camden <ra...@adobe.com> wrote:
> Ah, good point there.
>
> I¹m going to write up a blog post on this after I run some errands. I¹d
> love a quick review from you, or anyone, before I publish. I¹m also going
> to add something to the core docs.
>
>
> On 9/30/14, 11:18 AM, "Michal Mocny" <mm...@chromium.org> wrote:
>
> >That sounds reasonable.
> >
> >The <engine> tag is a bit weird though, in that the dependency is on cli
> >and not platform version. Combined with CLI semver and platform release
> >unbundling, its a bit hard to reason about. It kinda still works because
> >we have default platform versions pinned to cli versions, but users can
> >explicitly install non-default platform versions if they chose, and
> >plugins
> >may have support for only a subset of platforms..
> >
> >-Michal
> >
> >On Tue, Sep 30, 2014 at 12:11 PM, Ray Camden <ra...@adobe.com> wrote:
> >
> >> Ah - never mind. I picked a plugin that didn¹t have it specified. I
> >>picked
> >> another random one and it *was* shown.
> >>
> >> I¹d say that for plugins w/o engine support, the site should still say
> >> something, even if
> >>
> >> Engine Number
> >> Not Specified
> >>
>
>
Re: 3.6 cordova plugin versions
Posted by Ray Camden <ra...@adobe.com>.
Ah, good point there.
I¹m going to write up a blog post on this after I run some errands. I¹d
love a quick review from you, or anyone, before I publish. I¹m also going
to add something to the core docs.
On 9/30/14, 11:18 AM, "Michal Mocny" <mm...@chromium.org> wrote:
>That sounds reasonable.
>
>The <engine> tag is a bit weird though, in that the dependency is on cli
>and not platform version. Combined with CLI semver and platform release
>unbundling, its a bit hard to reason about. It kinda still works because
>we have default platform versions pinned to cli versions, but users can
>explicitly install non-default platform versions if they chose, and
>plugins
>may have support for only a subset of platforms..
>
>-Michal
>
>On Tue, Sep 30, 2014 at 12:11 PM, Ray Camden <ra...@adobe.com> wrote:
>
>> Ah - never mind. I picked a plugin that didn¹t have it specified. I
>>picked
>> another random one and it *was* shown.
>>
>> I¹d say that for plugins w/o engine support, the site should still say
>> something, even if
>>
>> Engine Number
>> Not Specified
>>
Re: 3.6 cordova plugin versions
Posted by Michal Mocny <mm...@chromium.org>.
That sounds reasonable.
The <engine> tag is a bit weird though, in that the dependency is on cli
and not platform version. Combined with CLI semver and platform release
unbundling, its a bit hard to reason about. It kinda still works because
we have default platform versions pinned to cli versions, but users can
explicitly install non-default platform versions if they chose, and plugins
may have support for only a subset of platforms..
-Michal
On Tue, Sep 30, 2014 at 12:11 PM, Ray Camden <ra...@adobe.com> wrote:
> Ah - never mind. I picked a plugin that didn’t have it specified. I picked
> another random one and it *was* shown.
>
> I’d say that for plugins w/o engine support, the site should still say
> something, even if
>
> Engine Number
> Not Specified
>
>
> On 9/30/14, 11:09 AM, "Ray Camden" <ra...@adobe.com> wrote:
>
> >Query - why isn¹t <engine> data shown on plugins.cordova.io? That seems
> >like crucial data that should be displayed, right?
> >
> >On 9/30/14, 10:59 AM, "Michal Mocny" <mm...@chromium.org> wrote:
> >>
> >>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 >= 3.0.0).
> >>
> >
>
>
Re: 3.6 cordova plugin versions
Posted by Ray Camden <ra...@adobe.com>.
Ah - never mind. I picked a plugin that didn’t have it specified. I picked
another random one and it *was* shown.
I’d say that for plugins w/o engine support, the site should still say
something, even if
Engine Number
Not Specified
On 9/30/14, 11:09 AM, "Ray Camden" <ra...@adobe.com> wrote:
>Query - why isn¹t <engine> data shown on plugins.cordova.io? That seems
>like crucial data that should be displayed, right?
>
>On 9/30/14, 10:59 AM, "Michal Mocny" <mm...@chromium.org> wrote:
>>
>>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 >= 3.0.0).
>>
>
Re: 3.6 cordova plugin versions
Posted by Ray Camden <ra...@adobe.com>.
Query - why isn¹t <engine> data shown on plugins.cordova.io? That seems
like crucial data that should be displayed, right?
On 9/30/14, 10:59 AM, "Michal Mocny" <mm...@chromium.org> wrote:
>
>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 >= 3.0.0).
>
Re: 3.6 cordova plugin versions
Posted by Michal Mocny <mm...@chromium.org>.
On Wed, Oct 1, 2014 at 4:13 PM, Fischer, Paul A <pa...@intel.com>
wrote:
> Hi Michal,
>
> Thanks for the clarification. What you describe is what I expected, and I
> totally understand the issues around trying to tightly specify what version
> works where, getting independent plugin developers to follow through with
> testing, etc. It's an impossible matrix to maintain. :(
>
> In essence, based on the process you outline, I am assuming something like
> the following badly formatted timeline of releases:
>
> -- cordova X.Y release --
> Core Cordova plugins tested against are listed by individual version
> (provided in release notes/blog)
> Core Cordova plugin A gets updated
> Core Cordova plugin B gets updated
> Core Cordova plugin C gets updated
> Core Cordova plugin A gets updated
> Core Cordova plugin D gets updated
> Core Cordova plugin A gets updated
> ...etc.
> -- cordova X.Z release --
> Core Cordova plugins tested against are listed (provided in release
> notes/blog)
> ...similar to above
> ...etc.
> -- cordova Y.A release --
>
> So one can generally "assume" that those core plugin versions listed in
> the release notes of a Cordova framework, up to those versions listed in
> the next Cordova framework release are "safe" to use with the immediately
> preceding release of the framework.
>
I think thats a good conservative conclusion to make. In practice, newer
plugin updates are quite compatible with older platform versions and often
contain valuable fixes -- but you probably don't want to assume that by
default.
>
> I ask only because our users are not all sophisticated Cordova users (I
> represent Intel and the XDK) and trying to come up with some general
> guidelines. They are limited to the Cordova CLI versions that we provide
> build support for, so they can't just update the CLI to meet the needs of a
> specific plugin.
>
Fair enough. We've also toyed with community supplied metadata -- where
you can flag a plugin as *not* working, and assume it works unless it is
flagged. This would shift the burden over to the community / testers,
instead of the plugin authors. But this was just brainstorming, there is
no work on this yet. (I bring it up in case this appeals to you as a
project).
>
> Thanks for the quick replies, sorry mine was so long in coming,
>
> Paul
>
> -----Original Message-----
> From: mmocny@google.com [mailto:mmocny@google.com] On Behalf Of Michal
> Mocny
> Sent: Tuesday, September 30, 2014 09:00
> To: dev
> Subject: Re: 3.6 cordova plugin versions
>
> 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 >= 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 <ra...@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" <sh...@gmail.com> wrote:
> >
> > >He didnt ask that question, but Ray: yes.
> > >
> > >On Tuesday, September 30, 2014, Ray Camden <ra...@adobe.com> wrote:
> > >
> > >> Does it make sense to clarify that statement though? Not *every*
> > >>plugin is tested like this, just the ³Core² 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:
> > >>
> > >> >
> >
> >
>
RE: 3.6 cordova plugin versions
Posted by "Fischer, Paul A" <pa...@intel.com>.
Hi Michal,
Thanks for the clarification. What you describe is what I expected, and I totally understand the issues around trying to tightly specify what version works where, getting independent plugin developers to follow through with testing, etc. It's an impossible matrix to maintain. :(
In essence, based on the process you outline, I am assuming something like the following badly formatted timeline of releases:
-- cordova X.Y release --
Core Cordova plugins tested against are listed by individual version (provided in release notes/blog)
Core Cordova plugin A gets updated
Core Cordova plugin B gets updated
Core Cordova plugin C gets updated
Core Cordova plugin A gets updated
Core Cordova plugin D gets updated
Core Cordova plugin A gets updated
...etc.
-- cordova X.Z release --
Core Cordova plugins tested against are listed (provided in release notes/blog)
...similar to above
...etc.
-- cordova Y.A release --
So one can generally "assume" that those core plugin versions listed in the release notes of a Cordova framework, up to those versions listed in the next Cordova framework release are "safe" to use with the immediately preceding release of the framework.
I ask only because our users are not all sophisticated Cordova users (I represent Intel and the XDK) and trying to come up with some general guidelines. They are limited to the Cordova CLI versions that we provide build support for, so they can't just update the CLI to meet the needs of a specific plugin.
Thanks for the quick replies, sorry mine was so long in coming,
Paul
-----Original Message-----
From: mmocny@google.com [mailto:mmocny@google.com] On Behalf Of Michal Mocny
Sent: Tuesday, September 30, 2014 09:00
To: dev
Subject: Re: 3.6 cordova plugin versions
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 >= 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 <ra...@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" <sh...@gmail.com> wrote:
>
> >He didnt ask that question, but Ray: yes.
> >
> >On Tuesday, September 30, 2014, Ray Camden <ra...@adobe.com> wrote:
> >
> >> Does it make sense to clarify that statement though? Not *every*
> >>plugin is tested like this, just the ³Core² 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:
> >>
> >> >
>
>
Re: 3.6 cordova plugin versions
Posted by Michal Mocny <mm...@chromium.org>.
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 >= 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 <ra...@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" <sh...@gmail.com> wrote:
>
> >He didnt ask that question, but Ray: yes.
> >
> >On Tuesday, September 30, 2014, Ray Camden <ra...@adobe.com> wrote:
> >
> >> Does it make sense to clarify that statement though? Not *every* plugin
> >>is
> >> tested like this, just the ³Core² 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:
> >>
> >> >
>
>
Re: 3.6 cordova plugin versions
Posted by Ray Camden <ra...@adobe.com>.
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" <sh...@gmail.com> wrote:
>He didnt ask that question, but Ray: yes.
>
>On Tuesday, September 30, 2014, Ray Camden <ra...@adobe.com> wrote:
>
>> Does it make sense to clarify that statement though? Not *every* plugin
>>is
>> tested like this, just the ³Core² 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:
>>
>> >
Re: 3.6 cordova plugin versions
Posted by Shazron <sh...@gmail.com>.
He didnt ask that question, but Ray: yes.
On Tuesday, September 30, 2014, Ray Camden <ra...@adobe.com> wrote:
> Does it make sense to clarify that statement though? Not *every* plugin is
> tested like this, just the ³Core² 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:
>
> >Yes
> >
> >On Monday, September 29, 2014, Joshi, Pavankumar
> ><JoshiP@fast.au.fujitsu.com <javascript:;>>
> >wrote:
> >
> >> Thanks for the mail. Kindly can you clarify this question,
> >>
> >> So every time a new version of plugin is released, is it tested with the
> >> already released latest Cordova version.
> >> Example: In Cordova 3.6 release it is stated that battery-status plugin
> >> version 0.2.10 is tested. Then on 22 September 0.2.11 version of
> >> battery-status plugin was released.
> >> So does it mean that 0.2.11 version was tested with 3.6.0 version of
> >> Cordova ? I am asking this because if I download and use Cordova 3.6.0
> >> release, then can I continuously upgrade the plugins to the latest
> >>released
> >> version?
> >>
> >>
> >> Thanks and Regards
> >> Pavan Joshi
> >>
> >>
> >> -----Original Message-----
> >> From: Shazron [mailto:shazron@gmail.com <javascript:;> <javascript:;>]
> >> Sent: Monday, 29 September 2014 4:59 PM
> >> To: dev@cordova.apache.org <javascript:;> <javascript:;>
> >> Subject: Re: 3.6 cordova plugin versions
> >>
> >> Plugins are independently released and not tied to a particular version.
> >> That just shows it was tested with that version.
> >> Just use the latest versions.
> >>
> >> On Sun, Sep 28, 2014 at 11:41 PM, Joshi, Pavankumar <
> >> JoshiP@fast.au.fujitsu.com <javascript:;> <javascript:;>> wrote:
> >>
> >> > Sorry, But then why the news section of plugins,
> >> > http://cordova.apache.org/announcements/2014/09/22/cordova-361.html,
> >> > still has an older version?
> >> > In Cordova 3.6 release page it says
> >> >
> >> > Plugin versions tested with this release
> >> >
> >> > cordova-plugin-battery-status: 0.2.10
> >> > cordova-plugin-camera: 0.3.1
> >> > cordova-plugin-console: 0.2.10
> >> > cordova-plugin-contacts: 0.2.12
> >> > cordova-plugin-device: 0.2.11
> >> > cordova-plugin-device-motion: 0.2.9
> >> > cordova-plugin-device-orientation: 0.3.8
> >> > cordova-plugin-dialogs: 0.2.9
> >> > cordova-plugin-file: 1.3.0
> >> > cordova-plugin-file-transfer: 0.4.5
> >> > cordova-plugin-geolocation: 0.3.9
> >> > cordova-plugin-globalization: 0.3.0
> >> > cordova-plugin-inappbrowser: 0.5.1
> >> > cordova-plugin-media: 0.2.12
> >> > cordova-plugin-media-capture: 0.3.2
> >> > cordova-plugin-network-information: 0.2.11
> >> > cordova-plugin-splashscreen: 0.3.2
> >> > cordova-plugin-statusbar: 0.1.7
> >> > cordova-plugin-vibration: 0.3.10
>
>
Re: 3.6 cordova plugin versions
Posted by Ray Camden <ra...@adobe.com>.
Does it make sense to clarify that statement though? Not *every* plugin is
tested like this, just the ³Core² 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" <sh...@gmail.com> wrote:
>Yes
>
>On Monday, September 29, 2014, Joshi, Pavankumar
><Jo...@fast.au.fujitsu.com>
>wrote:
>
>> Thanks for the mail. Kindly can you clarify this question,
>>
>> So every time a new version of plugin is released, is it tested with the
>> already released latest Cordova version.
>> Example: In Cordova 3.6 release it is stated that battery-status plugin
>> version 0.2.10 is tested. Then on 22 September 0.2.11 version of
>> battery-status plugin was released.
>> So does it mean that 0.2.11 version was tested with 3.6.0 version of
>> Cordova ? I am asking this because if I download and use Cordova 3.6.0
>> release, then can I continuously upgrade the plugins to the latest
>>released
>> version?
>>
>>
>> Thanks and Regards
>> Pavan Joshi
>>
>>
>> -----Original Message-----
>> From: Shazron [mailto:shazron@gmail.com <javascript:;>]
>> Sent: Monday, 29 September 2014 4:59 PM
>> To: dev@cordova.apache.org <javascript:;>
>> Subject: Re: 3.6 cordova plugin versions
>>
>> Plugins are independently released and not tied to a particular version.
>> That just shows it was tested with that version.
>> Just use the latest versions.
>>
>> On Sun, Sep 28, 2014 at 11:41 PM, Joshi, Pavankumar <
>> JoshiP@fast.au.fujitsu.com <javascript:;>> wrote:
>>
>> > Sorry, But then why the news section of plugins,
>> > http://cordova.apache.org/announcements/2014/09/22/cordova-361.html,
>> > still has an older version?
>> > In Cordova 3.6 release page it says
>> >
>> > Plugin versions tested with this release
>> >
>> > cordova-plugin-battery-status: 0.2.10
>> > cordova-plugin-camera: 0.3.1
>> > cordova-plugin-console: 0.2.10
>> > cordova-plugin-contacts: 0.2.12
>> > cordova-plugin-device: 0.2.11
>> > cordova-plugin-device-motion: 0.2.9
>> > cordova-plugin-device-orientation: 0.3.8
>> > cordova-plugin-dialogs: 0.2.9
>> > cordova-plugin-file: 1.3.0
>> > cordova-plugin-file-transfer: 0.4.5
>> > cordova-plugin-geolocation: 0.3.9
>> > cordova-plugin-globalization: 0.3.0
>> > cordova-plugin-inappbrowser: 0.5.1
>> > cordova-plugin-media: 0.2.12
>> > cordova-plugin-media-capture: 0.3.2
>> > cordova-plugin-network-information: 0.2.11
>> > cordova-plugin-splashscreen: 0.3.2
>> > cordova-plugin-statusbar: 0.1.7
>> > cordova-plugin-vibration: 0.3.10
Re: 3.6 cordova plugin versions
Posted by Ray Camden <ra...@adobe.com>.
I don¹t have an answer, but I definitely see merit in documenting this
here:
http://cordova.apache.org/docs/en/3.6.0/cordova_plugins_pluginapis.md.html#
Plugin%20APIs
(replace 3.6.0 with ³most current² of course)
We should clarify expectations for when/how the core plugins are tested in
regards to the main Cordova release.
I¹ll happily write something up.
On 9/30/14, 10:16 AM, "Fischer, Paul A" <pa...@intel.com> wrote:
>But it is not wise to assume that the latest version of a core plugin is
>also tested against an older version of Cordova CLI? Is that true or
>false? In other words, when you test the latest version of a core plugin,
>you only test it against the latest released version of the Cordova CLI.
>Using the latest version of a core plugin is not guaranteed to work with
>a prior version of Cordova CLI.
>
>Are my assumptions correct or incorrect?
>
>-----Original Message-----
>From: Shazron [mailto:shazron@gmail.com]
>Sent: Tuesday, September 30, 2014 07:05
>To: dev@cordova.apache.org
>Subject: Re: 3.6 cordova plugin versions
>
>Yes
>
>On Monday, September 29, 2014, Joshi, Pavankumar
><Jo...@fast.au.fujitsu.com>
>wrote:
>
>> Thanks for the mail. Kindly can you clarify this question,
>>
>> So every time a new version of plugin is released, is it tested with
>> the already released latest Cordova version.
>> Example: In Cordova 3.6 release it is stated that battery-status
>> plugin version 0.2.10 is tested. Then on 22 September 0.2.11 version
>> of battery-status plugin was released.
>> So does it mean that 0.2.11 version was tested with 3.6.0 version of
>> Cordova ? I am asking this because if I download and use Cordova 3.6.0
>> release, then can I continuously upgrade the plugins to the latest
>> released version?
>>
>>
>> Thanks and Regards
>> Pavan Joshi
>>
RE: 3.6 cordova plugin versions
Posted by "Fischer, Paul A" <pa...@intel.com>.
But it is not wise to assume that the latest version of a core plugin is also tested against an older version of Cordova CLI? Is that true or false? In other words, when you test the latest version of a core plugin, you only test it against the latest released version of the Cordova CLI. Using the latest version of a core plugin is not guaranteed to work with a prior version of Cordova CLI.
Are my assumptions correct or incorrect?
-----Original Message-----
From: Shazron [mailto:shazron@gmail.com]
Sent: Tuesday, September 30, 2014 07:05
To: dev@cordova.apache.org
Subject: Re: 3.6 cordova plugin versions
Yes
On Monday, September 29, 2014, Joshi, Pavankumar <Jo...@fast.au.fujitsu.com>
wrote:
> Thanks for the mail. Kindly can you clarify this question,
>
> So every time a new version of plugin is released, is it tested with
> the already released latest Cordova version.
> Example: In Cordova 3.6 release it is stated that battery-status
> plugin version 0.2.10 is tested. Then on 22 September 0.2.11 version
> of battery-status plugin was released.
> So does it mean that 0.2.11 version was tested with 3.6.0 version of
> Cordova ? I am asking this because if I download and use Cordova 3.6.0
> release, then can I continuously upgrade the plugins to the latest
> released version?
>
>
> Thanks and Regards
> Pavan Joshi
>
>
> -----Original Message-----
> From: Shazron [mailto:shazron@gmail.com <javascript:;>]
> Sent: Monday, 29 September 2014 4:59 PM
> To: dev@cordova.apache.org <javascript:;>
> Subject: Re: 3.6 cordova plugin versions
>
> Plugins are independently released and not tied to a particular version.
> That just shows it was tested with that version.
> Just use the latest versions.
>
> On Sun, Sep 28, 2014 at 11:41 PM, Joshi, Pavankumar <
> JoshiP@fast.au.fujitsu.com <javascript:;>> wrote:
>
> > Sorry, But then why the news section of plugins,
> > http://cordova.apache.org/announcements/2014/09/22/cordova-361.html,
> > still has an older version?
> > In Cordova 3.6 release page it says
> >
> > Plugin versions tested with this release
> >
> > cordova-plugin-battery-status: 0.2.10
> > cordova-plugin-camera: 0.3.1
> > cordova-plugin-console: 0.2.10
> > cordova-plugin-contacts: 0.2.12
> > cordova-plugin-device: 0.2.11
> > cordova-plugin-device-motion: 0.2.9
> > cordova-plugin-device-orientation: 0.3.8
> > cordova-plugin-dialogs: 0.2.9
> > cordova-plugin-file: 1.3.0
> > cordova-plugin-file-transfer: 0.4.5
> > cordova-plugin-geolocation: 0.3.9
> > cordova-plugin-globalization: 0.3.0
> > cordova-plugin-inappbrowser: 0.5.1
> > cordova-plugin-media: 0.2.12
> > cordova-plugin-media-capture: 0.3.2
> > cordova-plugin-network-information: 0.2.11
> > cordova-plugin-splashscreen: 0.3.2
> > cordova-plugin-statusbar: 0.1.7
> > cordova-plugin-vibration: 0.3.10
> >
> > are plugins latest version for example cordova-plugin-battery-status:
> > 0.2.11 is tested with 3.6?
> >
> > Regards
> > Pavan Joshi
> >
> >
> > -----Original Message-----
> > From: Shazron [mailto:shazron@gmail.com <javascript:;>]
> > Sent: Monday, 29 September 2014 4:20 PM
> > To: dev@cordova.apache.org <javascript:;>
> > Subject: Re: 3.6 cordova plugin versions
> >
> > Always use the latest.
> >
> > On Sun, Sep 28, 2014 at 9:48 PM, Joshi, Pavankumar <
> > JoshiP@fast.au.fujitsu.com <javascript:;>> wrote:
> >
> > > Hello devs,
> > >
> > > Kindly clarify our doubt. It’s a blocker issue for us.
> > >
> > > Regarding 3.6 release, which versions of plugins should we use?
> > > In the News page of Apache Cordova 3.6 release,
> > > http://cordova.apache.org/announcements/2014/09/22/cordova-361.htm
> > > l, the versions of plugins, for example
> > > cordova-plugin-battery-status and cordova-plugin-vibration are
> > > 0.2.10 and 0.3.10 respectively.
> > > But on 22 September versions of all plugins were incremented by 1.
> > > Now in Apache Cordova plugin documentation, if I go to plugins and
> > > click on vibration plugin of 3.6.0 release,
> > > http://cordova.apache.org/docs/en/3.6.0/cordova_plugins_pluginapis.md.
> > > html#Plugin%20APIs I get the description as tagged in 0.3.11 and
> > > not as explained in 0.3.10.
> > > Please let me know which versions of plugins should be considered
> > > as
> > > 3.6.0 Cordova release.
> > >
> > > Thanks and Regards
> > > Pavan Joshi
> > >
> > >
> > >
> >
>
Re: 3.6 cordova plugin versions
Posted by Shazron <sh...@gmail.com>.
Yes
On Monday, September 29, 2014, Joshi, Pavankumar <Jo...@fast.au.fujitsu.com>
wrote:
> Thanks for the mail. Kindly can you clarify this question,
>
> So every time a new version of plugin is released, is it tested with the
> already released latest Cordova version.
> Example: In Cordova 3.6 release it is stated that battery-status plugin
> version 0.2.10 is tested. Then on 22 September 0.2.11 version of
> battery-status plugin was released.
> So does it mean that 0.2.11 version was tested with 3.6.0 version of
> Cordova ? I am asking this because if I download and use Cordova 3.6.0
> release, then can I continuously upgrade the plugins to the latest released
> version?
>
>
> Thanks and Regards
> Pavan Joshi
>
>
> -----Original Message-----
> From: Shazron [mailto:shazron@gmail.com <javascript:;>]
> Sent: Monday, 29 September 2014 4:59 PM
> To: dev@cordova.apache.org <javascript:;>
> Subject: Re: 3.6 cordova plugin versions
>
> Plugins are independently released and not tied to a particular version.
> That just shows it was tested with that version.
> Just use the latest versions.
>
> On Sun, Sep 28, 2014 at 11:41 PM, Joshi, Pavankumar <
> JoshiP@fast.au.fujitsu.com <javascript:;>> wrote:
>
> > Sorry, But then why the news section of plugins,
> > http://cordova.apache.org/announcements/2014/09/22/cordova-361.html,
> > still has an older version?
> > In Cordova 3.6 release page it says
> >
> > Plugin versions tested with this release
> >
> > cordova-plugin-battery-status: 0.2.10
> > cordova-plugin-camera: 0.3.1
> > cordova-plugin-console: 0.2.10
> > cordova-plugin-contacts: 0.2.12
> > cordova-plugin-device: 0.2.11
> > cordova-plugin-device-motion: 0.2.9
> > cordova-plugin-device-orientation: 0.3.8
> > cordova-plugin-dialogs: 0.2.9
> > cordova-plugin-file: 1.3.0
> > cordova-plugin-file-transfer: 0.4.5
> > cordova-plugin-geolocation: 0.3.9
> > cordova-plugin-globalization: 0.3.0
> > cordova-plugin-inappbrowser: 0.5.1
> > cordova-plugin-media: 0.2.12
> > cordova-plugin-media-capture: 0.3.2
> > cordova-plugin-network-information: 0.2.11
> > cordova-plugin-splashscreen: 0.3.2
> > cordova-plugin-statusbar: 0.1.7
> > cordova-plugin-vibration: 0.3.10
> >
> > are plugins latest version for example cordova-plugin-battery-status:
> > 0.2.11 is tested with 3.6?
> >
> > Regards
> > Pavan Joshi
> >
> >
> > -----Original Message-----
> > From: Shazron [mailto:shazron@gmail.com <javascript:;>]
> > Sent: Monday, 29 September 2014 4:20 PM
> > To: dev@cordova.apache.org <javascript:;>
> > Subject: Re: 3.6 cordova plugin versions
> >
> > Always use the latest.
> >
> > On Sun, Sep 28, 2014 at 9:48 PM, Joshi, Pavankumar <
> > JoshiP@fast.au.fujitsu.com <javascript:;>> wrote:
> >
> > > Hello devs,
> > >
> > > Kindly clarify our doubt. It’s a blocker issue for us.
> > >
> > > Regarding 3.6 release, which versions of plugins should we use?
> > > In the News page of Apache Cordova 3.6 release,
> > > http://cordova.apache.org/announcements/2014/09/22/cordova-361.html,
> > > the versions of plugins, for example cordova-plugin-battery-status
> > > and cordova-plugin-vibration are 0.2.10 and 0.3.10 respectively.
> > > But on 22 September versions of all plugins were incremented by 1.
> > > Now in Apache Cordova plugin documentation, if I go to plugins and
> > > click on vibration plugin of 3.6.0 release,
> > > http://cordova.apache.org/docs/en/3.6.0/cordova_plugins_pluginapis.md.
> > > html#Plugin%20APIs I get the description as tagged in 0.3.11 and not
> > > as explained in 0.3.10.
> > > Please let me know which versions of plugins should be considered as
> > > 3.6.0 Cordova release.
> > >
> > > Thanks and Regards
> > > Pavan Joshi
> > >
> > >
> > >
> >
>
RE: 3.6 cordova plugin versions
Posted by "Joshi, Pavankumar" <Jo...@fast.au.fujitsu.com>.
Thanks for the mail. Kindly can you clarify this question,
So every time a new version of plugin is released, is it tested with the already released latest Cordova version.
Example: In Cordova 3.6 release it is stated that battery-status plugin version 0.2.10 is tested. Then on 22 September 0.2.11 version of battery-status plugin was released.
So does it mean that 0.2.11 version was tested with 3.6.0 version of Cordova ? I am asking this because if I download and use Cordova 3.6.0 release, then can I continuously upgrade the plugins to the latest released version?
Thanks and Regards
Pavan Joshi
-----Original Message-----
From: Shazron [mailto:shazron@gmail.com]
Sent: Monday, 29 September 2014 4:59 PM
To: dev@cordova.apache.org
Subject: Re: 3.6 cordova plugin versions
Plugins are independently released and not tied to a particular version.
That just shows it was tested with that version.
Just use the latest versions.
On Sun, Sep 28, 2014 at 11:41 PM, Joshi, Pavankumar < JoshiP@fast.au.fujitsu.com> wrote:
> Sorry, But then why the news section of plugins,
> http://cordova.apache.org/announcements/2014/09/22/cordova-361.html,
> still has an older version?
> In Cordova 3.6 release page it says
>
> Plugin versions tested with this release
>
> cordova-plugin-battery-status: 0.2.10
> cordova-plugin-camera: 0.3.1
> cordova-plugin-console: 0.2.10
> cordova-plugin-contacts: 0.2.12
> cordova-plugin-device: 0.2.11
> cordova-plugin-device-motion: 0.2.9
> cordova-plugin-device-orientation: 0.3.8
> cordova-plugin-dialogs: 0.2.9
> cordova-plugin-file: 1.3.0
> cordova-plugin-file-transfer: 0.4.5
> cordova-plugin-geolocation: 0.3.9
> cordova-plugin-globalization: 0.3.0
> cordova-plugin-inappbrowser: 0.5.1
> cordova-plugin-media: 0.2.12
> cordova-plugin-media-capture: 0.3.2
> cordova-plugin-network-information: 0.2.11
> cordova-plugin-splashscreen: 0.3.2
> cordova-plugin-statusbar: 0.1.7
> cordova-plugin-vibration: 0.3.10
>
> are plugins latest version for example cordova-plugin-battery-status:
> 0.2.11 is tested with 3.6?
>
> Regards
> Pavan Joshi
>
>
> -----Original Message-----
> From: Shazron [mailto:shazron@gmail.com]
> Sent: Monday, 29 September 2014 4:20 PM
> To: dev@cordova.apache.org
> Subject: Re: 3.6 cordova plugin versions
>
> Always use the latest.
>
> On Sun, Sep 28, 2014 at 9:48 PM, Joshi, Pavankumar <
> JoshiP@fast.au.fujitsu.com> wrote:
>
> > Hello devs,
> >
> > Kindly clarify our doubt. It’s a blocker issue for us.
> >
> > Regarding 3.6 release, which versions of plugins should we use?
> > In the News page of Apache Cordova 3.6 release,
> > http://cordova.apache.org/announcements/2014/09/22/cordova-361.html,
> > the versions of plugins, for example cordova-plugin-battery-status
> > and cordova-plugin-vibration are 0.2.10 and 0.3.10 respectively.
> > But on 22 September versions of all plugins were incremented by 1.
> > Now in Apache Cordova plugin documentation, if I go to plugins and
> > click on vibration plugin of 3.6.0 release,
> > http://cordova.apache.org/docs/en/3.6.0/cordova_plugins_pluginapis.md.
> > html#Plugin%20APIs I get the description as tagged in 0.3.11 and not
> > as explained in 0.3.10.
> > Please let me know which versions of plugins should be considered as
> > 3.6.0 Cordova release.
> >
> > Thanks and Regards
> > Pavan Joshi
> >
> >
> >
>
Re: 3.6 cordova plugin versions
Posted by Shazron <sh...@gmail.com>.
Plugins are independently released and not tied to a particular version.
That just shows it was tested with that version.
Just use the latest versions.
On Sun, Sep 28, 2014 at 11:41 PM, Joshi, Pavankumar <
JoshiP@fast.au.fujitsu.com> wrote:
> Sorry, But then why the news section of plugins,
> http://cordova.apache.org/announcements/2014/09/22/cordova-361.html,
> still has an older version?
> In Cordova 3.6 release page it says
>
> Plugin versions tested with this release
>
> cordova-plugin-battery-status: 0.2.10
> cordova-plugin-camera: 0.3.1
> cordova-plugin-console: 0.2.10
> cordova-plugin-contacts: 0.2.12
> cordova-plugin-device: 0.2.11
> cordova-plugin-device-motion: 0.2.9
> cordova-plugin-device-orientation: 0.3.8
> cordova-plugin-dialogs: 0.2.9
> cordova-plugin-file: 1.3.0
> cordova-plugin-file-transfer: 0.4.5
> cordova-plugin-geolocation: 0.3.9
> cordova-plugin-globalization: 0.3.0
> cordova-plugin-inappbrowser: 0.5.1
> cordova-plugin-media: 0.2.12
> cordova-plugin-media-capture: 0.3.2
> cordova-plugin-network-information: 0.2.11
> cordova-plugin-splashscreen: 0.3.2
> cordova-plugin-statusbar: 0.1.7
> cordova-plugin-vibration: 0.3.10
>
> are plugins latest version for example cordova-plugin-battery-status:
> 0.2.11 is tested with 3.6?
>
> Regards
> Pavan Joshi
>
>
> -----Original Message-----
> From: Shazron [mailto:shazron@gmail.com]
> Sent: Monday, 29 September 2014 4:20 PM
> To: dev@cordova.apache.org
> Subject: Re: 3.6 cordova plugin versions
>
> Always use the latest.
>
> On Sun, Sep 28, 2014 at 9:48 PM, Joshi, Pavankumar <
> JoshiP@fast.au.fujitsu.com> wrote:
>
> > Hello devs,
> >
> > Kindly clarify our doubt. It’s a blocker issue for us.
> >
> > Regarding 3.6 release, which versions of plugins should we use?
> > In the News page of Apache Cordova 3.6 release,
> > http://cordova.apache.org/announcements/2014/09/22/cordova-361.html,
> > the versions of plugins, for example cordova-plugin-battery-status and
> > cordova-plugin-vibration are 0.2.10 and 0.3.10 respectively.
> > But on 22 September versions of all plugins were incremented by 1.
> > Now in Apache Cordova plugin documentation, if I go to plugins and
> > click on vibration plugin of 3.6.0 release,
> > http://cordova.apache.org/docs/en/3.6.0/cordova_plugins_pluginapis.md.
> > html#Plugin%20APIs I get the description as tagged in 0.3.11 and not
> > as explained in 0.3.10.
> > Please let me know which versions of plugins should be considered as
> > 3.6.0 Cordova release.
> >
> > Thanks and Regards
> > Pavan Joshi
> >
> >
> >
>
RE: 3.6 cordova plugin versions
Posted by "Joshi, Pavankumar" <Jo...@fast.au.fujitsu.com>.
Sorry, But then why the news section of plugins, http://cordova.apache.org/announcements/2014/09/22/cordova-361.html, still has an older version?
In Cordova 3.6 release page it says
Plugin versions tested with this release
cordova-plugin-battery-status: 0.2.10
cordova-plugin-camera: 0.3.1
cordova-plugin-console: 0.2.10
cordova-plugin-contacts: 0.2.12
cordova-plugin-device: 0.2.11
cordova-plugin-device-motion: 0.2.9
cordova-plugin-device-orientation: 0.3.8
cordova-plugin-dialogs: 0.2.9
cordova-plugin-file: 1.3.0
cordova-plugin-file-transfer: 0.4.5
cordova-plugin-geolocation: 0.3.9
cordova-plugin-globalization: 0.3.0
cordova-plugin-inappbrowser: 0.5.1
cordova-plugin-media: 0.2.12
cordova-plugin-media-capture: 0.3.2
cordova-plugin-network-information: 0.2.11
cordova-plugin-splashscreen: 0.3.2
cordova-plugin-statusbar: 0.1.7
cordova-plugin-vibration: 0.3.10
are plugins latest version for example cordova-plugin-battery-status: 0.2.11 is tested with 3.6?
Regards
Pavan Joshi
-----Original Message-----
From: Shazron [mailto:shazron@gmail.com]
Sent: Monday, 29 September 2014 4:20 PM
To: dev@cordova.apache.org
Subject: Re: 3.6 cordova plugin versions
Always use the latest.
On Sun, Sep 28, 2014 at 9:48 PM, Joshi, Pavankumar < JoshiP@fast.au.fujitsu.com> wrote:
> Hello devs,
>
> Kindly clarify our doubt. It’s a blocker issue for us.
>
> Regarding 3.6 release, which versions of plugins should we use?
> In the News page of Apache Cordova 3.6 release,
> http://cordova.apache.org/announcements/2014/09/22/cordova-361.html,
> the versions of plugins, for example cordova-plugin-battery-status and
> cordova-plugin-vibration are 0.2.10 and 0.3.10 respectively.
> But on 22 September versions of all plugins were incremented by 1.
> Now in Apache Cordova plugin documentation, if I go to plugins and
> click on vibration plugin of 3.6.0 release,
> http://cordova.apache.org/docs/en/3.6.0/cordova_plugins_pluginapis.md.
> html#Plugin%20APIs I get the description as tagged in 0.3.11 and not
> as explained in 0.3.10.
> Please let me know which versions of plugins should be considered as
> 3.6.0 Cordova release.
>
> Thanks and Regards
> Pavan Joshi
>
>
>
Re: 3.6 cordova plugin versions
Posted by Shazron <sh...@gmail.com>.
Always use the latest.
On Sun, Sep 28, 2014 at 9:48 PM, Joshi, Pavankumar <
JoshiP@fast.au.fujitsu.com> wrote:
> Hello devs,
>
> Kindly clarify our doubt. It’s a blocker issue for us.
>
> Regarding 3.6 release, which versions of plugins should we use?
> In the News page of Apache Cordova 3.6 release,
> http://cordova.apache.org/announcements/2014/09/22/cordova-361.html, the
> versions of plugins, for example cordova-plugin-battery-status and
> cordova-plugin-vibration are 0.2.10 and 0.3.10 respectively.
> But on 22 September versions of all plugins were incremented by 1.
> Now in Apache Cordova plugin documentation, if I go to plugins and click
> on vibration plugin of 3.6.0 release,
> http://cordova.apache.org/docs/en/3.6.0/cordova_plugins_pluginapis.md.html#Plugin%20APIs
> I get the description as tagged in 0.3.11 and not as explained in 0.3.10.
> Please let me know which versions of plugins should be considered as 3.6.0
> Cordova release.
>
> Thanks and Regards
> Pavan Joshi
>
>
>