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 <stevengil...@gmail.com> 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 <gorkem.er...@gmail.com> > 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-unsubscr...@cordova.apache.org > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > >
