Discussion on the state of cloud computing and open source software that helps build, manage, and deliver everything-as-a-service.
2.2.10, 2.2.11, 2.2.12 - what do the versions number mean, how should I interpret - why do bug and feature targets keep moving.
If you've been following the CloudStack news of late you may know that there's a merged version that's already hit the 2.2.y and master branches of our git repos, and maybe you've even noticed the preview builds of that merged version. Those are versioned 2.2.11.some_prerelease_number, and those builds were generated from the 2.2.y branch. 2.2.10, already had a branch and was well into testing. and was still a split release.
2.2.11 was the targeted merge version and going to be built from the 2.2.y branch in git. However shortly after the 2.2.10 release, a customer came across a significant bug. After our developers looked at it, they realized that it could potentially affect other users, and decided to fix that bug and issue a new release with just those one or two fixes. (This level of responsiveness is one of the reasons that CloudStack support is widely valued among our customers). So in the next day or two 2.2.11 will likely emerge, and rather than being built on the 2.2.y branch, it's being built of the 2.2.11 branch, which was branched from 2.2.10 branch. (Confused about branches yet? :) )
So why does this merit a blogpost? Well for one reason, we want to be transparent and open, but more importantly, we want to make sure that you know that the work for the release that was formerly going to be known as 2.2.11 is still going on, making sure that the upgrade paths work; particularly from a database perspective, along with a few build issues are capturing a good chunk of time. We've found at least two bugs in this testing phase related to the merge, and those should be fixed shortly and forward progress is being made, even if the release won't be wearing the 2.2.11 badge because of other circumstances.
In the meantime, if you are so minded, the 2.2.y branch could certainly benefit from more people testing, and there are articles for setting up a development environment. A number of people are already stopping in IRC to talk about it, and contribute patches, which is always exciting.