Agree that we should do a blog post. I will start writing one up tomorrow. Added a new check that only allows npm 1.3.4 to publish plugins. Let me know if you guys find any other fires to put out with this thing :P
On Mon, Feb 16, 2015 at 2:08 PM, Parashuram N (MS OPEN TECH) < panar...@microsoft.com> wrote: > Should we put out a blog post, telling that plugin authors may need to > republish old version? Could also be a way to refer to our move to npm :) > > -----Original Message----- > From: Chuck Lantz [mailto:cla...@microsoft.com] > Sent: Monday, February 16, 2015 1:37 PM > To: dev@cordova.apache.org; Nick Martin > Subject: RE: Plugin history purged from registry? > > Thanks Steve - We verified all of the pinned plugins in VS are working > again! > > -Chuck > > -----Original Message----- > From: Steven Gill [mailto:stevengil...@gmail.com] > Sent: Monday, February 16, 2015 1:24 PM > To: Nick Martin > Cc: dev@cordova.apache.org > Subject: Re: Plugin history purged from registry? > > Okay they are all up again. > > I had to change the latest tag for all of them back to what it should be. > > Ownership is messed up right now. Only Andrew and myself are listed as > owners for the plugins. I will have to readd all of you who want the > ability to publish core plugins. Let me know if you do. > > I am going to look into blocking plugman 0.22.17 again. Don't want the bug > from January to pop back up. > > Plugin authors will have to republish old versions of their plugins if > they have lost their history. > > > On Mon, Feb 16, 2015 at 1:11 PM, Nick Martin <n...@meteor.com> wrote: > > > Thank you, Steve! > > > > -- Nick > > > > On Mon, Feb 16, 2015 at 11:35 AM, Chuck Lantz <cla...@microsoft.com> > > wrote: > > > >> Awesome! Do let us know if you need help. Nikhil was digging in a > >> bit but we'll hold given this update. > >> > >> -Chuck > >> > >> From: Steven Gill [mailto:stevengil...@gmail.com] > >> Sent: Monday, February 16, 2015 11:29 AM > >> To: Chuck Lantz > >> Cc: dev@cordova.apache.org > >> Subject: Re: Plugin history purged from registry? > >> > >> It looks like the problem lies with the check I added to prevent > >> plugman > >> 0.22.17 from publishing. I have removed that check and updated the > >> DB. In the process of uploading old core plugins now. > >> I will figure out a better check after all of the plugins have been > >> uploaded again. > >> > >> On Sun, Feb 15, 2015 at 8:17 PM, Chuck Lantz <cla...@microsoft.com > >> <mailto:cla...@microsoft.com>> wrote: > >> Yeah Visual Studio is in a similar boat for projects where devs have > >> not used a plugin before. (We fortunately switched to storing the > >> plugins in the project in our latest update so existing projects > >> work.) We're directing people to use git URIs near term when acquiring > plugins. > >> > >> Steve, let us know if you need assistance. I can chat with folks > >> about pitching in if it would be helpful. (But know too many cooks > >> can be a problem too.) > >> > >> ________________________________________ > >> From: Nick Martin <n...@meteor.com<mailto:n...@meteor.com>> > >> Sent: Sunday, February 15, 2015 6:50 PM > >> To: Steven Gill > >> Cc: dev@cordova.apache.org<mailto:dev@cordova.apache.org> > >> Subject: Re: Plugin history purged from registry? > >> Hi Steven, > >> > >> Thank you for your work on this issue. I know it's the weekend, and I > >> appreciate you going above and beyond. > >> > >> Do you have any idea if and when old versions of plugins will be > >> restored to the site? This issue is biting our users pretty hard -- > >> we pin plugins to stable versions so users are not taken by surprise > >> when new versions come out. Old versions being missing means none of > >> our users can re-build or update their apps! > >> > >> Even a rough order of magnitude estimate would be helpful. We have to > >> decide if we need to push out an emergency patch release on Monday to > >> upgrade to the latest versions still in the registry. > >> > >> Thanks again, > >> -- Nick > >> > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
