First off I want to thank you for your work on this project. I noticed that the last release was over 4 months ago and since then it seems like many fixes have been introduced such as support for [email protected].
Is there a timeframe for the next release? It would be good if we could see more incremental releases along as well as a pathway to ensure backwards compatible changes can be more quickly incorporated while delaying breaking changes to expected intervals.
I would like to hear thoughts as well as help out where I can.
I see issues get created or commented on every day for fixes that are apparently in master, yet no new version has been released. Everyone trying out this library for the first time is getting a horrible experience because the version they are installing doesn't even work. It only takes a couple minutes to push a new patch release. What is the hold up?
would be cool to get a new release.. my app actually isnt buildable :(
@robertarnesson can you please add someone else to the list of maintainers so a new release can get published?
@soumak77 That's a great idea. Far too often I see cordova plugins abandoned which I really think hurts the ecosystem as a whole.
@adamduren agreed. If we don't get a resolution to this in the coming weeks, we may want to think about creating a fork which can be maintained by the community. It would be unfortunate to have to go down that route, but not having a release in 3 months is unacceptable.
any volunteer maintainers? a donation would also do \o/
the intermediate solution is to add the plugin from git (rather than npm) in your project
As mentioned in thread I'm interested in contributing. I'm fairly new to this particular project but have experience maintaining private npm projects as well as cordova plugins.
This is an aside but related to the donation. It would be nice if Firebase had official support for Cordova or were willing to sponsor projects to advance the platform.
@robertarnesson please add me as a maintainer
@robertarnesson Is there any objection to publishing a new major release (i.e. version 1.0) to follow proper semver rules? If not, I'll work on getting a prerelease created for testing sometime next week.
@soumak77 thats fine with me - its about time I guess :)
@robertarnesson if you haven't done so already, please add me as an owner to the npm package so that I can publish new releases
@robertarnesson I pushed a new version to github, but I still need publishing permissions for the npm package
I have the same problem, thanks
version 1.0 has been released
Most helpful comment
@robertarnesson please add me as a maintainer