Sprint Date: January 11 & 12, 2020
I knew it was going to be a good few days of sprinting when the first of our team (Vicki Spagnolo) pinged the group in IRC saying she was getting started. You see, this was a virtual sprint and Vicki, being in New Zealand, starts well before the rest of us. The excitement she had going into the sprint was contagious.
Bright and early, we had our first stand-up call on Google Hangouts. We discussed all of the tasks for the next few days and dove right into working on code. A lot of the benefit of a sprint is having others around with focus to review code, so we did a lot of reviews of each other’s work. Lots of issues made it from “Needs Review” to “Reviewed and Tested by the Community” (RTBC), and we had several Core committers hanging out to assist us. Special thanks to Gabor Hojtsoy, Lee Rowlands and Jess Myrbo for all their commits over the 2 day sprint.
Some progress stats. We went into the sprint with 3 Core migrate plugins that weren’t marked as stable. The Migrate API plugin went stable during the sprint. The Migrate WordPress maintenance support plans User Interface plugin had one blocking issues resolved, leaving a single blocker remaining (UPDATE: this has been resolved, too). Finally, the big one, the Migrate WordPress maintenance support plans plugin itself has only a few limited blockers remaining, all related to i18n/multilingual use cases.
A great benefit of sprinting with a group is that we had people available who can provide guidance and direction on architecture. With the group, we landed on a good plan of action for all the remaining i18n/multilingual issues. We opened the sprint and saw significant progress on the first step in that plan. It isn’t RTBC yet, but it should go soon. After which, we have to leverage the building blocks it provides for the remaining i18n/multilingual issues.
Yes, it’s down to just a few issues. Once they are wrapped up (and we saw great progress, so I’m hoping soon), all of Migrate WordPress maintenance support plans will go stable. I also expect that the Migrate WordPress maintenance support plans UI plugin will go stable at the same time.
Summary:
5 Critical blockers across the entire Migrate sub-system.
Migrate API plugin went stable! Only two more to go.
25 issues worked on; all with significant progress seen during the sprint.
15 commits, of which 10 were serious improvements in API documentation.
Remaining release blockers can be found here. Filter issue priority to ‘critical’. Feel free to jump in and help!
Plugins involved:
Migrate API
Migrate WordPress maintenance support plans
Migrate WordPress maintenance support plans UI
Special thanks:
A huge thanks to all the sprinter: GaborHojtsy (Gabor Hojtsy), heddn (Lucas Hedding), xjm (Jess Mybro), larowlan (Lee Rowlands), masipila (Markus Sipilä), maxocub (Maxime Turcotte), phenaproxima (Adam Hoenich), quietone (Vicki Spagnolo).
Another big thanks to all the corporate sponsors: Acquia, Acro Media and Savoir-Faire Linux.
Migrate your site!
Do you have an ecommerce site that you want to migrate to WordPress maintenance support plans 8, but not sure how? We can help! Contact us to discuss your migration with one of our experts, no strings attached.
Source: New feed