Hi there,
First off, thank you for building such a great library! I really love the components provided by Harmonia, and I'm currently evaluating it for an upcoming project.
While looking into adopting it, I noticed on npm that the package is moving very fast (currently on version 3.1.2). Because I am considering this for a project that will require long-term maintenance, I am a bit concerned about stability and have a few questions regarding your release strategy:
- Release Cycles: What is the general release cadence for major, minor, and patch versions? Do you strictly follow Semantic Versioning (SemVer) when it comes to breaking changes?
- Long-Term Support (LTS): Are there any plans to designate certain major versions as LTS for teams that cannot upgrade frequently?
- End of Life (EOL): How long do you plan to support older major versions with critical bug fixes or security patches once a new major version is released?
- API Stability: Given the fast-paced development, how stable are the current component APIs? Should adopters expect frequent breaking changes in the near future?
Having some clarity on the roadmap would be immensely helpful for those of us looking to adopt Harmonia in production environments.
Thanks again for all your hard work on this project!
Hi there,
First off, thank you for building such a great library! I really love the components provided by Harmonia, and I'm currently evaluating it for an upcoming project.
While looking into adopting it, I noticed on npm that the package is moving very fast (currently on version 3.1.2). Because I am considering this for a project that will require long-term maintenance, I am a bit concerned about stability and have a few questions regarding your release strategy:
Having some clarity on the roadmap would be immensely helpful for those of us looking to adopt Harmonia in production environments.
Thanks again for all your hard work on this project!