Frequency of updates is a good indication of the on-going viability of a data warehouse automation platform.
From what we see and hear, too many competitors are good at getting their products released, but not so good at error correction and enhancement.
This came to mind while I was packaging our latest update – huge changes in incremental deployment – and looked at the following:
That’s the releases we’ve made during just the past four months.
- Every update is cumulative, you don’t have to apply them all
- Every update contains one or more new features, usually driven directly by customer requests
- Most updates contain performance enhancements
- Many updates contain code enhancements and corrections to errors reported by users
Here’s what a couple of weeks looks like in Mercurial:
All our release planning is done through a Trello board. At present it has a backlog of around 18 months for the current development team. New target platforms. New data sources. New transformations. New BI interfaces. New methodology support. New features we’re not yet ready to discuss. We’re going to continue, or even accelerate the rate of new feature deployment over the next year.
The one thing that won’t change is our licence policy. We’ll continue to be a site-licensed product, with no lock-ins, including the guarantee that your data warehouse will continue to function even if you don’t renew your Ajilius licence, and we’ll never increase your annual renewal for as long as you use Ajilius.
Ajilius. USD 15k / site. The best value in data warehouse automation.