Sprint 60 is mostly focused on the stabilization of upcoming Fine release, with close to half of the total 570 pull requests (a new high) going towards bug fixes. This sprint marks the first time that the Classic UI repo has outpaced the core ManageIQ repo in PRs, 158 to 148. From Sprint 52 to 60, the number of ManageIQ repositories went from 103 to 114 (11 new repos over 8 sprints), and more are being planned. We have a new “Repository Health Report” which includes number of files, Code Climate GPA scores and issues, as well as test coverages across different repos.

Welcome to Sprint 57 recap. In this sprint we merged a total of 565 pull request combined, almost 10% more than last sprint’s 518, and well ahead of what we used to achieve with 3-week sprints in 2016! The 180 PRs in the main repo is distributed in thirds between enhancements, bugs, and everything else. We are also growing in number of repos, from 103 repos 5 sprints ago, to 108 now. The new repos introduced this sprint are amazon_ssa_support and manageiq-ui-scaffold. More info on them will come as they get populated.

Greetings from FOSSASIA 2017 in Singapore! It’s exciting to see the growth of the open source movement in Asia and I hope to share more about ManageIQ with everyone I meet here. However, since I’m bustling about at this activity-filled event, I’ll have to make this post shorter than usual.

Welcome once again to a sprint review recap. This time we are looking at Sprint 55, which produced a total of 495 pull requests across all the ManageIQ repos. We used to see similar numbers in 3-week sprints last year! Even though we haven’t done an official comparison, PR counts seem to be drifting up in many repos, including the main repo (with 144 PRs this sprint) which has been split into many parts. With 2 more new repos (font-fabulous and manageiq-api-mock) this sprint, it seems that while the repo-splits caused some initial disruption, the outcome allowed for more velocity per repository.

Welcome to the Sprint 54 review recap! For this sprint, we had 126 pull requests in the main ManageIQ repo, with a good mix of enhancements, bugs, cleanup and more. The Classic UI repo contributed 80 more PRs, with Integration tests following closely at 77 PRs. Grand total across all repos is 462. As we keep splitting out repos from the monolith (which is looking less like one every sprint), the majority of the work will be going outside of the main repo.

As we move on to our second 2-week Sprint, we find 146 pull requests merged in the main ManageIQ repo, with enhancements and bugs taking up 2/3 of the pie. Further breakdown shows 39 PRs in the providers category, 21 in API, 20 in core and 12 in UI, and we expect the number of remaining UI PRs to go down to zero with the recent repo split. Across all the repos, which includes 77 repos under the ManageIQ umbrella, and 14 manageiq-* ones, there were 432 pull requests in total.

This sprint review marked the end of the first 2-week Sprint, which we are trying out and will adjust as needed. As mentioned previously, we are splitting repos as we chip away at the ManageIQ monolith and progress it into a platform. Keep up to date with the details in the Developers category of Talk forum.

Welcome to the first sprint review of 2017! It was a relatively succinct meeting, so I’ll try to keep this short and sweet. First, a couple of news items in case you missed them:

Happy New Year! We’re starting off 2017 with a notable change in the ManageIQ process. In an effort to become more agile, and allow more flexibility in planning and scheduling, we will be switching from 3-week Sprints to 2-week Sprints.

Hello and welcome to the final sprint review of 2016! During this sprint, we released RC2 for Euwe as well as Darga-5. We are on track for Euwe GA in the upcoming week, after which we’ll look forward to fleshing out the Fine release in 2017.

Welcome to the Sprint 49 review recap. The Euwe release candidate has been running its course, waiting for the next release to take over soon. Stay tuned!

Welcome to the Sprint 48 review recap! This was the sprint for the Euwe Beta release, with the just announced Euwe release candidate hot on its heels.

There is a ManageIQ Sprint review every 3 weeks, and everyone in the community is welcome to participate. To join our Sprint review meeting, please use this Bluejeans link.

There is a ManageIQ Sprint review every 3 weeks, and everyone in the community is welcome to participate. To join our Sprint review meeting, please use this Bluejeans link.

There is a ManageIQ Sprint review every 3 weeks, and everyone in the community is welcome to participate. To join our Sprint review meeting, please use this Bluejeans link.

There is a ManageIQ Sprint review every 3 weeks, and everyone in the community is welcome to participate. To join our Sprint review meeting, please use this Bluejeans link.

There is a ManageIQ Sprint review every 3 weeks, and everyone in the community is welcome to participate. To join our Sprint review meeting, please use this Bluejeans link.

Every three weeks, we discuss our sprint reports, and you can participate in this process.

Every three weeks, we discuss our sprint reports, and you can participate in this process, as well as take a look at our handiwork with a compiled image from this sprint.

If you’ve been participating in our sprint reports, you’ve no doubt found them to be an excellent way to stay apprised of feature progress in ManageIQ. I’m happy to announce that our community activities are now part of the 3-week sprints and included in the sprint reports.

Every three weeks, we discuss our sprint reports, and you can participate in this process, as well as take a look at our handiwork with a compiled image from this sprint.

The sprint 20 report is today at 7:30 PDT/10:30 EDT/14:30 GMT at the usual bluejeans.com location. Today’s topics include updates on the following:

Date & time: Wed February 18, 10:30am Eastern US/15:30 UTC

Time: 15:30 UTC/GMT, 10:30 EST

This is recording of the Sprint 16 report from Wednesday, Dec 3. To see the newest features from this sprint, download the latest bleeding edge Botvinnik image.

It’s that time again - today at 10:30am EST is the latest sprint report. If you’re interested in hearing what’s on the roadmap, you’ll want to join us on a web conference.

Earlier this week, we mentioned moving to ruby 2 on our github repository and in travis-ci for testing. Ruby 2 nightly build appliances based on sprint 15 are available here.

We just finished up the Sprint 12 demo, ended September 9.