Sprint 4 Planning
On this sprint 4, we want to try to do it a bit longer, so it’ll be 4 weeks instead of 2. This doesn’t mean that we aren’t going to release anything in 4 weeks, we’ll consider to do a release at the middle of the sprint if we consider it necessary.
We’re going to focus on finishing and merging everything that is currently in progress from previous sprints mentioned before, both the Pull Requests from the Frontity team and external ones.
Once that is done, we want to start the research of the e2e tests for WordPress and solve all the high priority bugs that are left:
- Frontity doesn’t work with Semantic UI [8pt]
- Research - E2E testing that requires WordPress instances [21pt]
After this, we can keep working on the next user stories and features:
- Create the Slot component [3pt]: Once this is done, the whole Slot and Fill feature will be finished.
- Add ENV variables for the build, dev and serve commands. [3pt]: Once this is done, the whole change publicPath feature would be finished.
- Version 1 of the Analytics library [6pt].
- Start working in the first part of Native WordPress comments package:
This is what is planned to be accomplished in the next 4 weeks. However, if we still have time, we’ll start working on the second part of the Native WordPress comments package:
Apart from that, we may ask Edu for some support to develop these features (or new ones.
Sprint 4 Review
For a more detailed view of the final status of the sprint you can check the GitHub board.
Note that, as we’re doing the release after the end of the sprint and we did a release at the middle of the sprint, some issues may differ in the announcement and in this review.
Frontity team review
Released - 50pt
We finished all the issues that were
in-progress in the previous sprint, although most of them were almost done:
- Research - WP Comments [20pt].
- Add publicPath option to CLI and pass it down to Webpack in both the build and dev commands [3pt].
- actions.source.fetch with “force: true” doesn’t work as expected [3pt].
- actions.source.fetch should populate link, route, page and query even if data exists [3pt].
- Create the useFills hook [5pt].
- Create ComScore beta package [5pt].
Between all the things we planned for the Sprint 4, we have finished:
- Frontity doesn’t work with Semantic UI [8pt].
- Add ENV variables for the build, dev and serve commands. [3pt]: With this one, the whole change publicPath feature is finished.
And apart from this, we have included a couple of critical bugs that needed to be solved:
- publicPath option not working with absolute urls.
- Pageviews not sent when navigating to a link with the same title.
babel-plugin-lodash not working in node: This wasn’t a
criticalbug, but it was solved after fixing Semantic UI.
In progress - 43pt
There are some features included in this sprint that, although we didn’t finish them, are almost done:
- Create the Slot component [3pt]: This one is supposed to be finished. It’s just pending the review. Once this is merged, the whole Slot and Fill feature will be finished.
- Version 1 of the Analytics[6pt]: It has already been reviewed, just some minor changes are needed. In the same Pull Request, we’re finally going to release also the version 1 of the Google Analytics package and the ComScore analytics package.
- Research - E2E testing that requires WordPress instances [21pt] : We underestimated this one and there are still some things to do, 13pt aprox.
- Add action to create new comments [13pt]: We still have to implement the error handling of this action. 5pt aprox left.
We estimated better this time and we were able to, at least, start all the features that were planned for this sprint.
in-progress features made by other Frontity users have been already finished. Some of them were released at the middle of the sprint.
- useConnect hook.
- Use a robots.txt file in the root.
- useInfiniteScroll hook: We released a beta version. Although it’s ready, we want to test it in real projects first until we release the v1.