Closed zachmullen closed 9 years ago
Once this gets added, should all extant plugins be version 1.0.1, some other value, or left without a version number until we modify the plugins for another reason?
We'll go through the ones in the repository and make them 1.0.0 if they're ready. If not I'm happy to leave them versionless. For metadata extractor and geospatial, I'll defer to @jamiesnape to decide versions for those.
Plugins now support version as of PR #270. We should go through the plugins and decide what version each one should be.
My suggestions:
Plugin | Version |
---|---|
jquery_widgets | 0.1.0 |
mongo_search | 0.1.0 |
oauth | 1.0.0 |
@jamiesnape Can you provide suggestions for geospatial and metadata_extractor? @cpatrick for google_analytics @ronichoudhury for vega
Thanks!
On Wed, Nov 5, 2014 at 3:04 PM, Zach Mullen notifications@github.com wrote:
@ronichoudhury https://github.com/ronichoudhury for vega
The plugin is basically a proxy to the version of Vega that's bundled with it. I'd say the version should be 1.0.0, and we bump it to 2.0.0 if and when we upgrade Vega to 2.x, and go to 1.0.1 for internal bugfixes etc. Does that work?
Sounds good.
Added version numbers in PR #470.
Plugins should be able to specify their own versions in plugin.json. It should be displayed on the plugins page next to the plugin name.