https://issues.apache.org/jira/browse/CB-6634
On May 1, 2014, at 1:37 PM, Freak Show wrote:
>
> On May 1, 2014, at 10:21 AM, Andrew Grieve wrote:
>
>> Hi Freak,
>>
>> We're just talking about cordova core plugins (not all plugins). You can
>> find the plugin registry here: http://plugins.cor
Hi Freak
Are you referring about having a link on the website
http://cordova.apache.org ?
There is a link at the top "Plugins" it will take you to the plugins
registry http://plugins.cordova.io
On Thu, May 1, 2014 at 10:37 AM, Freak Show wrote:
>
> On May 1, 2014, at 10:21 AM, Andrew Grieve
On May 1, 2014, at 10:21 AM, Andrew Grieve wrote:
> Hi Freak,
>
> We're just talking about cordova core plugins (not all plugins). You can
> find the plugin registry here: http://plugins.cordova.io
>
I had no idea that was there. Seems to me a top level "Available Plugins" link
would be a us
;
> >>
> http://plugins.cordova.io/#/package/org.apache.cordova.camera;engine=3.4.0
> >>>>> "
> >>>>> and get the docs page for the best version of the camera plugin for
> >>>> *that*
> >>>>> cordova release.
> >>>>>
> >>>>> Thoughts?
> &
y
>>> wrote:
>>>>>
>>>>>> Thats will be easy to pretend (just kidding! ;). Yes, the plugin
>>>>> registry
>>>>>> shows the docs as they exist at the time of the plugin release, so
>>> next
>>>>>
On Thu, May 1, 2014 at 1:01 PM, Mike Billau wrote:
> So the plugin registry will go fetch the appropriate docs from github for
> whichever version of the plugin you are viewing by using the engine tag on
> the plugin page and comparing that to the git tags? And then the github
> page will still j
gistry
> > > > > shows the docs as they exist at the time of the plugin release, so
> > next
> > > > > release the docs will be up to date.
> > > > >
> > > > > The primary benefit here is that the plugin registry has a version
> > > > switcher
> > > > > on the side, a
So the plugin registry will go fetch the appropriate docs from github for
whichever version of the plugin you are viewing by using the engine tag on
the plugin page and comparing that to the git tags? And then the github
page will still just direct to the edge version of the docs?
That makes sense
Why?
I do my backend work in PHP generally and I really like composer. Except for
the need to go register my plugin at packagist which makes FORKING a repo and
just using my tweaked code rather than the official release extra difficult
because I now have to now go register my package as well.
hat
> > > > version.
> > > >
> > > > (for the future, we could consider adding "edge" versions for core
> > > plugins
> > > > on plugin registry. Not for installs, but just to list the latest
> > docs)
> > > >
> >
but just to list the latest
> docs)
> > >
> > >
> > > On Wed, Apr 30, 2014 at 9:54 AM, Ray Camden
> wrote:
> > >
> > > > So... pretend I'm dumb here. Do I need to do anything? Will it just
> be
> > > > updated in the next plu
; > on plugin registry. Not for installs, but just to list the latest docs)
> >
> >
> > On Wed, Apr 30, 2014 at 9:54 AM, Ray Camden wrote:
> >
> > > So... pretend I'm dumb here. Do I need to do anything? Will it just be
> > > updated in the next
> > From: mmo...@google.com on behalf of Michal Mocny <
> > mmo...@chromium.org>
> > Sent: Wednesday, April 30, 2014 8:50 AM
> > To: Michal Mocny
> > Cc: dev
> > Subject: Re: Docs for plugins
> >
> > Ray, Yeah seems file plugin @c1a
I'd suggest the latter.
On Apr 30, 2014, at 9:52 AM, Michal Mocny wrote:
> .. which I guess raises the question, how can we make docs fixes without
> formal releases? Do we want that, or should we just make formal releases
> easier and more frequent until the problem goes away?
o I need to do anything? Will it just be
> updated in the next plugin release?
>
>
> From: mmo...@google.com on behalf of Michal Mocny <
> mmo...@chromium.org>
> Sent: Wednesday, April 30, 2014 8:50 AM
> To: Michal Mocny
>
So... pretend I'm dumb here. Do I need to do anything? Will it just be updated
in the next plugin release?
From: mmo...@google.com on behalf of Michal Mocny
Sent: Wednesday, April 30, 2014 8:50 AM
To: Michal Mocny
Cc: dev
Subject: Re: Docs for pl
.. which I guess raises the question, how can we make docs fixes without
formal releases? Do we want that, or should we just make formal releases
easier and more frequent until the problem goes away?
On Wed, Apr 30, 2014 at 9:50 AM, Michal Mocny wrote:
> Ray, Yeah seems file plugin @c1a1052 wa
Ray, Yeah seems file plugin @c1a1052 was tagged for 1.1.0 release 13 days
ago, you patched docs after that tag @abcaf70 12 days ago, and plugin was
actually released with @e9efe65 7 days ago. You just missed the window
narrowly!
-Michal
On Wed, Apr 30, 2014 at 9:45 AM, Michal Mocny wrote:
> I
I believe the plugin docs reflect what was bundled with the latest plugin
release -- perhaps your recent changes were not released yet? Or has
something gotten lost in the recent shuffle with dev/master branches?
Its true, though, that for core plugins our registry links to the official
apache re
19 matches
Mail list logo
