] On
Behalf
Of
Michal
Mocny
Sent: Tuesday, February 17, 2015 9:32 AM
To: dev
Subject: Re: Schedule for npm transition
FYI since its perhaps relevant to npm transition (from npm
weekly
notes):
We will also
...@google.com] On
Behalf
Of
Michal
Mocny
Sent: Tuesday, February 17, 2015 9:32 AM
To: dev
Subject: Re: Schedule for npm transition
FYI since its perhaps relevant to npm transition (from npm
weekly
notes
] On Behalf Of
Michal
Mocny
Sent: Tuesday, February 17, 2015 9:32 AM
To: dev
Subject: Re: Schedule for npm transition
FYI since its perhaps relevant to npm transition (from npm weekly
notes):
We will also be changing the behavior
...@google.com] On Behalf Of
Michal
Mocny
Sent: Tuesday, February 17, 2015 9:32 AM
To: dev
Subject: Re: Schedule for npm transition
FYI since its perhaps relevant to npm transition (from npm weekly
notes):
We will also be changing the behavior
?
-Chuck
-Original Message-
From: mmo...@google.com [mailto:mmo...@google.com] On Behalf Of Michal
Mocny
Sent: Tuesday, February 17, 2015 9:32 AM
To: dev
Subject: Re: Schedule for npm transition
FYI since its perhaps relevant to npm transition (from npm
plugins?
-Chuck
-Original Message-
From: mmo...@google.com [mailto:mmo...@google.com] On Behalf Of Michal
Mocny
Sent: Tuesday, February 17, 2015 9:32 AM
To: dev
Subject: Re: Schedule for npm transition
FYI since its perhaps relevant to npm
AM
To: dev
Subject: Re: Schedule for npm transition
FYI since its perhaps relevant to npm transition (from npm weekly
notes):
We will also be changing the behavior of peerDependencies in npm@3.
We
won't be automatically downloading the peer dependency
to upgrade to install any new
plugins?
-Chuck
-Original Message-
From: mmo...@google.com [mailto:mmo...@google.com] On Behalf
Of
Michal
Mocny
Sent: Tuesday, February 17, 2015 9:32 AM
To: dev
Subject: Re: Schedule
, February 17, 2015 9:32 AM
To: dev
Subject: Re: Schedule for npm transition
FYI since its perhaps relevant to npm transition (from npm
weekly
notes):
We will also be changing the behavior of peerDependencies in
npm@3.
We
?
-Chuck
-Original Message-
From: mmo...@google.com [mailto:mmo...@google.com] On Behalf
Of
Michal
Mocny
Sent: Tuesday, February 17, 2015 9:32 AM
To: dev
Subject: Re: Schedule for npm transition
FYI
:32 AM
To: dev
Subject: Re: Schedule for npm transition
FYI since its perhaps relevant to npm transition (from npm weekly notes):
We will also be changing the behavior of peerDependencies in npm@3. We
won’t be automatically downloading the peer dependency anymore. Instead,
we’ll warn you
FYI since its perhaps relevant to npm transition (from npm weekly notes):
We will also be changing the behavior of peerDependencies in npm@3. We
won’t be automatically downloading the peer dependency anymore. Instead,
we’ll warn you if the peer dependency isn’t already installed. This
requires
simply telling people
they have to upgrade to install any new plugins?
-Chuck
-Original Message-
From: mmo...@google.com [mailto:mmo...@google.com] On Behalf Of Michal Mocny
Sent: Tuesday, February 17, 2015 9:32 AM
To: dev
Subject: Re: Schedule for npm transition
FYI since its perhaps
Query, you say, if we use the mapper module - is there a chance that
may not happen, and in 3+ months, folks who do cordova plugin add
org.apache.cordova.something will get an error?
Sorry if that's a dumb question, not 100% sure what the mapper
module entails.
On Wed, Feb 11, 2015 at 1:39 PM,
]
Sent: Wednesday, February 11, 2015 3:48 PM
To: dev@cordova.apache.org
Subject: Re: Schedule for npm transition
I agree with Steve to move forward with this. The package name
rationale was already discussed during the hangout, and we all agreed.
On Wed, Feb 11, 2015 at 3:43 PM, Steven Gill
(or some other source of metadata) for a
'cloud' Cordova build system.
Thanks,
Leo
-Original Message-
From: Shazron [mailto:shaz...@gmail.com]
Sent: Wednesday, February 11, 2015 3:48 PM
To: dev@cordova.apache.org
Subject: Re: Schedule for npm transition
I agree with Steve to move
We don't have one yet but we should pick dates soon.
How about:
CPR Switch to read only: Monday, May 18th
NPM fetch becomes default: Monday, May 18th
CPR offline: Monday, August 17th
Based on the following proposal:
Steve, npm fetch default only affects plugins that use same name in both
places, right?
If we create cordova-plugin-device today, and tell users to start using
cordova plugin add cordova-plugin-device, then we will get much user
feedback on npm fetching far before May 18th, right?
On Wed, Feb
Correct! For the first 3 months, all requests will hit CPR first, if CPR
fails, we will try to fetch from npm.
If users run cordova plugin add cordova-plugin-device, it would hit CPR,
fail, go to npm, succeed.
If we use the mapper module, cordova plugin add
org.apache.cordova.device would be
Going to try and summarize my concerns with the proposal here:
On Wed, Feb 11, 2015 at 2:39 PM, Steven Gill stevengil...@gmail.com wrote:
Correct! For the first 3 months, all requests will hit CPR first, if CPR
fails, we will try to fetch from npm.
If users run cordova plugin add
that? Is the name change really
necessary - why can't we stick with the current names?
Thanks,
Leo
-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Wednesday, February 11, 2015 11:40 AM
To: dev@cordova.apache.org
Subject: Re: Schedule for npm transition
Correct
with the current names?
Thanks,
Leo
-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Wednesday, February 11, 2015 11:40 AM
To: dev@cordova.apache.org
Subject: Re: Schedule for npm transition
Correct! For the first 3 months, all requests will hit CPR first
, 2015 11:40 AM
To: dev@cordova.apache.org
Subject: Re: Schedule for npm transition
Correct! For the first 3 months, all requests will hit CPR first, if CPR
fails, we will try to fetch from npm.
If users run cordova plugin add cordova-plugin-device, it would hit CPR,
fail, go to npm, succeed
I would agree that we should change plugin ID as well as package name, but
I don't think that affects the results.
All 3 of those use cases you mentioned I think are addressed equivalently.
Whether the plugin is added as a dependency, with save/restore, or
explicitly from the command line,
On 11 Feb 2015, at 13:09, Steven Gill wrote:
We don't have one yet but we should pick dates soon.
How about:
CPR Switch to read only: Monday, May 18th
NPM fetch becomes default: Monday, May 18th
CPR offline: Monday, August 17th
I was hoping for a longer read-only period, 6 months would be
names?
Thanks,
Leo
-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Wednesday, February 11, 2015 11:40 AM
To: dev@cordova.apache.org
Subject: Re: Schedule for npm transition
Correct! For the first 3 months, all requests will hit CPR first, if CPR
fails, we
@cordova.apache.org
Subject: Re: Schedule for npm transition
Correct! For the first 3 months, all requests will hit CPR first, if
CPR
fails, we will try to fetch from npm.
If users run cordova plugin add cordova-plugin-device, it would hit
CPR,
fail, go to npm, succeed.
If we use the mapper
[mailto:stevengil...@gmail.com]
Sent: Wednesday, February 11, 2015 11:40 AM
To: dev@cordova.apache.org
Subject: Re: Schedule for npm transition
Correct! For the first 3 months, all requests will hit CPR first, if CPR
fails, we will try to fetch from npm.
If users run cordova plugin add cordova-plugin
28 matches
Mail list logo
