- nothing to raise a concern with a minor version change.
From: Jesse purplecabb...@gmail.com
Sent: Tuesday, April 7, 2015 4:28 AM
To: dev@cordova.apache.org
Subject: Re: Question about plugin/platform --save: src vs version?
I'm okay with spec, the pr looks
...@microsoft.com
Sent: Tuesday, April 7, 2015 8:18 AM
To: dev@cordova.apache.org
Subject: Re: Question about plugin/platform --save: src vs version?
Thanks Jesse.
Well, according to semver standards, a bumped minor version means it
is 100% backwards compatible, and I'm hoping semver at least complies
with a minor version change.
From: Jesse purplecabb...@gmail.com
Sent: Tuesday, April 7, 2015 4:28 AM
To: dev@cordova.apache.org
Subject: Re: Question about plugin/platform --save: src vs version?
I'm okay with spec, the pr looks good.
Are there any side-effects
From: Jesse purplecabb...@gmail.com
Sent: Thursday, April 2, 2015 7:01 AM
To: dev@cordova.apache.org
Subject: Re: Question about plugin/platform --save: src vs version?
I'm ok with 'spec'
However; I had always thought we would jam the new single attribute
into 'src' which is much more generic than
From: Jesse [purplecabb...@gmail.com]
Sent: Tuesday, March 31, 2015 3:53 PM
To: dev@cordova.apache.org
Subject: Re: Question about plugin/platform --save: src vs version?
I agree with Andrew, fail loudly if we cannot find it.
And, jam all this into 1 attribute which may
3:53 PM
To: dev@cordova.apache.org
Subject: Re: Question about plugin/platform --save: src vs version?
I agree with Andrew, fail loudly if we cannot find it.
And, jam all this into 1 attribute which may or may not have a version ( or
a tag? )
Essentially just store whatever the parameter
...@gmail.com]
Sent: Tuesday, March 31, 2015 3:53 PM
To: dev@cordova.apache.org
Subject: Re: Question about plugin/platform --save: src vs version?
I agree with Andrew, fail loudly if we cannot find it.
And, jam all this into 1 attribute which may or may not have a version (
or
a tag
[purplecabb...@gmail.com]
Sent: Tuesday, March 31, 2015 3:53 PM
To: dev@cordova.apache.org
Subject: Re: Question about plugin/platform --save: src vs version?
I agree with Andrew, fail loudly if we cannot find it.
And, jam all this into 1 attribute which may or may not have a version
( or
a tag
.
If you want one name, how about 'origin'.
Leo
-Original Message-
From: Jesse [mailto:purplecabb...@gmail.com]
Sent: Tuesday, March 31, 2015 11:47 AM
To: dev@cordova.apache.org
Subject: Re: Question about plugin/platform --save: src vs version?
Yes, words are hard.
re:
Jesse - are you
On 29 Mar 2015, at 23:11, Tim Barham wrote:
Hi - I'm looking for input on this issue: For the plugin/platform
--save feature, there's currently an inconsistency between how we
store the information in config.xml for platforms vs plugins.
For platforms, we have a 'version'
To: dev [dev@cordova.apache.org] dev@cordova.apache.org
Date: 03/30/2015 10:45 AM
Subject:Re: Question about plugin/platform --save: src vs version?
On 29 Mar 2015, at 23:11, Tim Barham wrote:
Hi - I'm looking for input on this issue: For the plugin/platform
--save feature, there's
@cordova.apache.org
Date: 03/30/2015 10:45 AM
Subject: Re: Question about plugin/platform --save: src vs version?
--
On 29 Mar 2015, at 23:11, Tim Barham wrote:
Hi - I'm looking for input on this issue: For the plugin/platform
--save feature, there's currently
To: dev [dev@cordova.apache.org] dev@cordova.apache.org
Date: 03/30/2015 10:45 AM
Subject: Re: Question about plugin/platform --save: src vs version?
--
On 29 Mar 2015, at 23:11, Tim Barham wrote:
Hi - I'm looking for input on this issue
Hi - I'm looking for input on this issue: For the plugin/platform --save
feature, there's currently an inconsistency between how we store the
information in config.xml for platforms vs plugins.
For platforms, we have a 'version' attribute where we store either the source
location or the
14 matches
Mail list logo
