Earlier in the week, Zoomdata proudly announced Zoomdata v2.6, a major milestone that includes improvements in analytic usability, connectivity, and architecture. In conjunction with the v2.6 rollout, Zoomdata initiated important changes to our software release, maintenance, and support processes. Principal among these changes, Zoomdata introduced a new model for feature and patch updates.
Our New Model Provides Options
Historically, Zoomdata’s release cadence has been feature driven. Our Product and Engineering Teams would develop great new capability and, when the product reached a critical mass for feature value, we would ship a new version. Over the past year we have increasingly received feedback from customers that would like faster, more incremental feature delivery. Many customers are eager to frequently accept new releases to gain access to the latest features. At the same time, we have many customers who value invariability and feature predictability more than the newest feature set. These customers want stability improvements without changes to application behavior through introduction of new functionality.
To service both needs, Zoomdata has adopted a release model that allows customers to choose between:
- A long-term support (LTS) version that receives stability fixes only through bi-weekly patch releases
- A rapid release version that adds stability fixes and new functionality every four weeks
The picture below illustrates the mechanics of this model.