Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D9BA317D11 for ; Sat, 14 Feb 2015 21:05:50 +0000 (UTC) Received: (qmail 41470 invoked by uid 500); 14 Feb 2015 21:05:50 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 41399 invoked by uid 500); 14 Feb 2015 21:05:50 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 41385 invoked by uid 99); 14 Feb 2015 21:05:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Feb 2015 21:05:50 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of raymondcamden@gmail.com designates 209.85.192.45 as permitted sender) Received: from [209.85.192.45] (HELO mail-qg0-f45.google.com) (209.85.192.45) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 14 Feb 2015 21:05:45 +0000 Received: by mail-qg0-f45.google.com with SMTP id h3so18358182qgf.4 for ; Sat, 14 Feb 2015 13:03:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=qAR9h6Y/amcGqOayJHIv/1xlV5ln00r68JOXsV91L2U=; b=PoLlBf2xiJtfG9FBBcrvD8h/Y8Ny7rApjf5VcgxBHUIhL2I/uv163oDZMRIV9G3m4o UzX/7DFYjn/P6SGpPOmwStXnJxusCMPhuuX5qfz3K3GwCINZB0FagxnqgLz2/mHXPI5M efQC7c+e1kLregr5mSkALQ9Kw2Ei6mKt/ZTnuCfbnSHCZiUo4M21RfL+JQNbRNJJZlhS bWRIWWksLafOmwWNhxTPf29Js8/dVPSTDmk4mZv/2mrJ0W+c1sl16JLXhZVDlwX6mgQi lymt9Hlxtlnek0fwsabb+GceUYO0BWEQlRBiBHZHJ2WlMYsyth7DkNhn8oI55/AoZcxC ajeQ== MIME-Version: 1.0 X-Received: by 10.141.18.10 with SMTP id u10mr10837720qhd.9.1423947835240; Sat, 14 Feb 2015 13:03:55 -0800 (PST) Received: by 10.96.10.39 with HTTP; Sat, 14 Feb 2015 13:03:55 -0800 (PST) In-Reply-To: References: <2F4839DC-CD04-419B-A050-1EF61AA831A2@gmail.com> Date: Sat, 14 Feb 2015 15:03:55 -0600 Message-ID: Subject: Re: Schedule for npm transition From: Raymond Camden To: dev@cordova.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org 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, Steven Gill 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 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 converted to cordova-plugin-device, hit > CPR, fail, go to npm, succeed. > > After 3 months, "cordova plugin add cordova-plugin-device" would hit npm > first and succeed. > > We want to use these 3 months to get our developers to update their tools > and use the new names for plugins to install. > > On Wed, Feb 11, 2015 at 10:36 AM, Michal Mocny wrote: > >> 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 11, 2015 at 1:09 PM, 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 >> > >> > Based on the following proposal: >> > >> > >> https://docs.google.com/document/d/12WAXJa6jfY3BnNHGieK9QOqvZ6cl3OXmP-9DpYkcmfs/edit?usp=sharing >> > >> > - Need to start educating plugin developers to publish to npm as well as >> > CPR for next three months. (blog post) >> > - Need to educate users to install plugins via new names (if >> package-name >> > is different than id). Our core plugins are being renamed from >> > org.apache.cordova.device to cordova-plugin-device >> > - Inform devs who are working with registry directly to pull plugins from >> > npm instead of CPR. After 3 months, CPR plugins will start to become out >> of >> > date compared to npm versions. >> > >> > Our next plugins release (after the one currently ongoing) will be >> > published to npm as well as cpr. >> > >> > >> > >> > On Wed, Feb 11, 2015 at 9:10 AM, Gorkem Ercan >> > wrote: >> > >> > > >> > > Is there a determined calendar for the npm move of the plugins? >> > > I think the scheduling of the transition is crucial for those who are >> > > using the plugin registry directly. >> > > -- >> > > Gorkem >> > > >> > > --------------------------------------------------------------------- >> > > To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org >> > > For additional commands, e-mail: dev-help@cordova.apache.org >> > > >> > > >> > >> -- =========================================================================== Raymond Camden, Developer Advocate for MobileFirst at IBM Email : raymondcamden@gmail.com Blog : www.raymondcamden.com Twitter: raymondcamden --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org For additional commands, e-mail: dev-help@cordova.apache.org