We just finished up the Sprint 12 demo, ended September 9.
We’re happy to announce the preliminary agenda for the upcoming ManageIQ Design Summit, a 2-day event on October 7 & 8 in Montvale, NJ. Be sure to RSVP soon, as space is very limited. As mentioned in the title, it’s a small intimate gathering of cloud experts, those interested in pushing the limits of ManageIQ and setting the roadmap for development. If you’re a ManageIQ user who wants to learn how to make the most of its automation and orchestration capabilities, then there will be plenty for you, too:
We are thrilled to announce that Aaron Patterson (@tenderlove) has joined the ManageIQ team.
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.
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.
Enjoy! Remember, if you find any issues, please report them.
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!