As an open-source project NativeScript keeps its source code and build infrastructure open. That is why we choose Travis CI for our nightly builds. Every commit in the master branch of all major NativeScript repos triggers a Travis CI build which publishes an npm package that can be used directly. Our goal is to help customers and partners address important issues for specific use cases without having to wait for the next major product update.
Seven-Day Bug Fixing
NativeScript Professional Support customers can get their Severity 1 issues prioritized and fixed within seven days. The NativeScript Team will attempt to resolve acknowledged Severity 1 product defects within seven days. These fixes will be included in the source code and available via npm.
Due to some limitations like regression potential and necessary refactoring, our service level objective (SLO) is to meet the seven-day target for 80% or more of Severity 1 product defects. Please note that the seven days bug fixing SLO is provided for information purposes only and is not a legally binding commitment or agreement.
We attempt to fix all reported issues on top of the latest product version and we highly recommend that customers regularly upgrade in order to benefit from the continuous improvements. However, business conditions sometimes prevent customers from upgrading and in such cases we will attempt to prepare a patch on top of an older version. We can attempt to produce patches for a limited number of versions back from the current one, as specified in your support plan. For example, if the support plan states you are eligible for receiving patches for up to three point versions back and the current version is 6.4, you can request patches for versions up to 6.1.
The produced patches are based on the official NativeScript version you are using. They’ve passed our fully automated test suite, which includes thousands of functional, integration, unit and performance tests. The actual bug fixes for which the patch is produced have also passed strict manual quality assurance and performance tests. These builds have not passed our full manual regression testing cycle that we do before each official release. The patch builds do not include breaking API changes, high-regression potential changes or fixes, and upgrading to them should be seamless. Upgrade from these builds to the consecutive official release is fully supported.
This service is available only to NativeScript Professional Support customers. Please note that due to code refactoring it’s not always possible to apply a patch to an older version. Nevertheless, we stand committed to meeting your business needs and if it isn’t possible to produce a patch we will advise you on the best path to address the issue.
Who should upgrade to latest version of the source code?
We recommend upgrading to “@next” in case you experience the particular issues that were fixed and resolved in the given build. The internal hotfixes are production-ready and can be upgraded to the consecutive release at a later point in time. Otherwise, you don’t have to worry about these builds since all those fixes will be included in the next major product release.
How to submit product feedback and see what’s in the works
We believe that an open source framework, like NativeScript, is best developed with help from the community. To influence our roadmap and be part of the discussions please visit our GitHub issues and use our voting system. Alternatively, you can submit a private inquiry by contacting Tech Support.