For the record, I updated org.apache.cordova.statusbar from 0.1.4 to 0.1.5 for release (it was unclear to me whether 0.1.4 had actually been released), and changed master to 0.1.6-dev.
And as Steve said, there were problems with the newly released version, so we unpublished 0.1.5 on the registry shortly afterwards. On Thu, May 1, 2014 at 4:43 PM, Steven Gill <stevengil...@gmail.com> wrote: > You can file bugs for plugins.cordova.io on jira using the > cordova-registry-web component. > > The statusbar plugin needs another vote + release. The last one got > reverted to it failing on android. Platforms + repo will be updated the > next time it gets published. Plugman publish will handle that. > > > On Thu, May 1, 2014 at 1:35 PM, Jesse <purplecabb...@gmail.com> wrote: > > > This commit increments the plugin.xml version from 1.3.0->1.4.0 and > > happened almost 2 months ago. > > The current version is 1.6.0-dev [2] > > The latest version on plugins.cordova.io is 1.3.0 and was updated 6 days > > ago. [3] > > > > Can this be someone's responsibility? This "anyone can so no one does" > > thing is annoying. > > > > Also, installing a plugin on an unsupported platform does not produce an > > error message of any kind. > > plugman will happily add the js interface and do nothing else. ( CB-6585 > ) > > > > And where are we filing bugs to http://plugins.cordova.io/ ? > > - plugin-details : no listing of what platforms are supported by a plugin > > - plugin-details : no link to the repo > > > > > > > > > > > > [1] > > > > > https://github.com/apache/cordova-plugin-statusbar/commit/3055b675a84e877476f58470deba6a0798973086 > > [2] > > > https://github.com/apache/cordova-plugin-statusbar/blob/master/plugin.xml > > [3] http://plugins.cordova.io/#/package/org.apache.cordova.statusbar > > > > > > @purplecabbage > > risingj.com > > >
