RFC #2 - Immediate Concerns #8
Replies: 5 comments 20 replies
-
I agree this version should be an in place replacement to original fork to allow people who are using this version to migrate without any breaking changes in terms of API. |
Beta Was this translation helpful? Give feedback.
-
I'm going to attempt to get the submodules merged into the main repository this coming week, and then I think we should get a version published to NPM. |
Beta Was this translation helpful? Give feedback.
-
@HarelM I think we're ready for another RC? Shall I kick this one off? - would be good for me to know how to do it, as I haven't done one yet! I'll test this one this eve on iOS and Android. |
Beta Was this translation helpful? Give feedback.
-
Is there anything else we would like to do before releasing version 1.0.0 (except maybe testing it more)? |
Beta Was this translation helpful? Give feedback.
-
We need to see how to get the tests up and running... or at least understand if we want to run them... |
Beta Was this translation helpful? Give feedback.
-
Proposal
It is proposed to create a release as soon as possible, with the most pressing concerns and issues resolved in order to secure the name on NPM and provide the community with a working plugin for background geolocation.
A milestone should be created on GitHub to organise this release and the issues that should be resolved in it.
The version number will be 1.0.0, as this is the first release of this plugin on NPM.
Beta Was this translation helpful? Give feedback.
All reactions