Views Data Export: Sprint 4 Summary
Steven Jones
I've started working on maintaining Views Data Export again.
I've decided to document my work in 2 week 'sprints'. And so this article is about what I did in Sprint 4.
Sprint progress
At the start of the sprint in the Drupal.org issue queue there were:
- 45 open bugs
- 1 fixed issue.
- 63 other open issues
That's a total of 109 open issues.
By the end it looked like this:
- 40 open bugs
- 1 fixed issue.
- 59 other open issues
So that's a total of 100 open issues, an 8% reduction from before.
Key goals
In this sprint I wanted to:
- Go through the remaining bug reports
- Try to get Drush commands back in.
Bug reports
Didn't manage to get through these, but I did discover this fantastic website:
https://contribkanban.com/board/views_data_export
Where I can view all the tickets in a non-nasty way.
I got through some bug reports and committed one fix that closed out two tickets.
Drush commands
I couldn't bring myself to commit the code that was on the issue in this sprint, I've explained myself in the issue. It just seems like although the code works, it's not doing things in the 'right' way.
Part of the code in that issue is refactoring some code around so that it can be called from multiple places. This is making the MR look a lot more messy than it might first appear, so I might split those pieces off into their own MR and get those committed in before looping back and trying to address the Drush specific elements of the current MR in that issue.
I'm planning to tackle this next week, as part of the Sprint 5.
I'll likely do a release at the end of Sprint 5 too.
Future roadmap/goals
I'm not committing myself to doing these exactly, or any particular order, but this is my high-level list of hopes/dreams/desires, I'll copy and paste this to the next sprint summary article as I go and adjust as required.
- Update the documentation on Drupal.org
- Not have any duplicate issues on Drupal.org