The votes are in, and “Botvinnik” is the winner! In planning for Botvinnik (which we’ll sometimes shorten to “bot”) we’re now accepting blueprints for proposed features. Just submit your blueprint and make sure to categorize it properly. Next, you’ll need to propose an abstract for the ManageIQ Design Summit. Make sure to put your proposal in the Abstracts category.

As we wind down the Anand release cycle, the next one is winding up: a vote to determine the next release name, a call for feature blueprints, and a call for participation for the very first ManageIQ Design Summit.

Now that the Anand release is almost out the door, it’s the right time to turn our attention to the next release. Since we’re going alphabetically by chess world champions, we have a few choices:

Things have been rolling along here at the ManageIQ community, and we’re proud to announce that the first release candidate is now ready. The first release for ManageIQ is called “Anand”, named after world champion chess player Viswanathan Anand.

To download a release candidate build of Anand, proceed to the download page. To get the source for Anand, see the tagged GitHub repo.

To get an idea of what is included in Anand, see the results of the previous sprint. To see what is coming next, take a look at the roadmap.

Enjoy! Remember, if you find any issues, please report them.

-JM

When we originally open-sourced ManageIQ, the ManageIQ GitHub Repo was integrated with Code Climate. Integrating with Code Climate allowed the developer community to find code with too much complexity and/or duplication and refactor it.

This week, we integrated the ManageIQ GitHub Repo with Travis CI, the continuous integration service. This service runs on each GitHub pull request to ensure that no new code is breaking existing tests (i.e. no regression). If the pull request does cause a regression, the core maintainers of the ManageIQ project will not merge it until this is resolved.

So, keep creating pull requests to make ManageIQ better, but make sure that they do not break any tests!

Thanks, chessbyte

Here’s a great introduction written by Bryan Che, a Red Hat cloud strategy guy, on why we released ManageIQ as an open source project, as well as a look at the cloud management landscape. Cloud management is currently a nice car with four flat tires, and all four of them with different sizes, colors, and recommended pressure.

The wait is over—ManageIQ is now open source!

As I mentioned in the previous blog post, it’s a great day to be in the cloud. Yesterday marked our announcement at the OpenStack Summit, and the reaction was pretty swift and positive. There is pent-up demand for software that lets others take control of their clouds and virtualization environments.

We are gearing up for an open source release in the coming weeks, and you’re probably curious what all the fuss is about. What you’ll find here is some introductory information and ways to sign up for news and, eventually, pre-release code as we get closer to the project launch. Read Red Hat’s press release – it will give you the background information you need.

This is pretty simple but very useful. I have done a little research and whilst inspect is a way of seeing inside of an object its also hard to read and not very re-usable. Being somewhat old now (crazy thought) XML used to be the way we described things. Yes I know yaml, json etc have come to replace XML in languages such as Ruby, but I cannot get away from XML is far easier to read and self describing than the aforementioned.