Iterating on our release strategy: Mule ESB, Mule Studio, CloudHub

motif

In the past, as now, Mule ESB follows a release schedule that introduces a new version of our industry-leading ESB software every 9 – 12 months, supplemented with maintenance releases approximately every 6 months. Though this cadence fit very tightly with the demands of our customers who deploy Mule on premises, we came to realize that our customers deploying Mule to were much more flexible in terms of updating versions of software, and were more eager to take advantage of new features and functionality.

Four months ago we introduced a revised release strategy for MuleSoft. We created this strategy because we wanted to accelerate the speed at which we’re able to deliver improvements to our customers. However, there is some lingering confusion from our community about how the strategy works. I would like to take this chance to more clearly explain our strategy.

1. Mule Studio will be released every 2 months and support several runtimes. Users can download Studio once, then add multiple Enterprise and Community runtimes to it. Our whole ecosystem – from community to on-premise and cloud customers – will benefit from these more frequent improvements and expanded set of features.

2. We have created a CloudHub Mule Runtime which is updated about every two months. With this shortened cycle, we are able to offer our CloudHub users access to new features and functionality without burdening our on-premises customers with the need to conduct frequent updates. Not only are we able to quickly innovate and deliver functionality with these rapid releases, we have tightened our user-feedback loop so as to better meet new demands in the industry. In addition to this, if users have applications that need to work in hybrid environments, they can continue to use the regular Mule ESB releases (e.g. Mule 3.4.1) on CloudHub as well.

We will provide full backward compatibility between the CloudHub Mule Runtime releases, with the exception of capabilities that are marked as preview. Because of this, we will only support the latest runtime at any given point, and customers will be auto-upgraded on CloudHub when a new release is available. These changes will also feed into the next on-premise release.

3. The Mule Studio and CloudHub Mule Runtime releases will be referred to by the date of the release where we need to mention a version (e.g. Oct 2013).

4.  Mule ESB releases will continue to released every 8-12 months and be available on CloudHub and on-premises. These releases will include both Mule Community Edition and Muel Enterprise Edition. It will continue to be versioned according to 3.4.x, 3.5.x, etc.

5. CloudHub and Anypoint Service Registry will continue to undergo continuous releases as features become available, and will align, for the most part, with the runtime improvements.

We hope this makes sense for you. If you’d like more details, check out the documentation on our release strategy. If you have any additional questions, please be sure to reach out to us in the comments section of this post.


We'd love to hear your opinion on this post