vosk-api
vosk-api copied to clipboard
alphacep
Kotlin Multiplatform Release Plan
- [x] Decide on version scheme. Currently, the version is set to 0.0.0. Should this be in sync with the releases, or should it be updated by itself?
- [x] Update documentation. Ensure documentation is compliant and well descriptive. Currently it just takes documentation straight from the C API which is not helpful at all.
- [x] Update license headers. While we all know it is apache2, I will add the headers to all files for it.
- [ ] Publish to maven central. Once prior steps are complete, Publish to the maven repository.
- [ ] Update dependents.
Numerous dependent applications should be updated to make use of the Kotlin API.
- [ ] demo: https://github.com/alphacep/vosk-android-demo/pull/198
- [ ] android-service: https://github.com/alphacep/vosk-android-service/pull/27
- [ ] Remove
androidandjavasub-projects They are duplicate code, and Android is default Kotlin nowadays anyways.
Continued from #1241
@nshmyrev This is the road map that should be followed to hopefully ensure a smooth release without any issues.
As far as I am concerned, it can be currently used via publication to maven local with the artifact id of vosk-api-kotlin.
Please let me know when ready to publish, I'll publish asap. As for version, I think it can be just in sync with the rest.
Btw, I've seen that in sherpa-ncnn fangjun used AssetManager in C++ on NDK side, it would be nice to get rid of copy of assets and just load models that way. I wanted to look on it when time permits but not much time yet.
Please let me know when ready to publish, I'll publish asap. As for version, I think it can be just in sync with the rest.
Alright, I shall sync it. It will now be 0.4.0-alpha0, matching up to the next release tag 0.4.0.
@nshmyrev The plan now is to remove the android and jvm targets, as they are duplicate code.
@nshmyrev I noticed that the kotlin library has not been published to maven central?