I just want to quickly note that this email notes the team's initial
thoughts about what we are planning to do next sprint. It is not yet a
commitment to do said work; that happens after our estimation meetings.
That will happen next week.
Dan
On 6 March 2015 at 12:07, Dan Garry <dgarry(a)wikimedia.org> wrote:
Hi everyone,
This is the summary of the work the Android team is planning on tackling
in sprint 53. You can see the full workboard in Phabricator
<https://phabricator.wikimedia.org/tag/mobile-app-sprint-53-ios/>.
We're currently on track to get a production release by the end of the
quarter which contains lead images, image gallery, and read more. To ensure
that we remain on track, our primary priority in sprint 53 will be to fix
bugs reported by our release to TestFlight, to keep our production release
on track.
Our significant feature backlog compared to Android has meant we've pushed
really hard on features with little regard for technical debt. While
putting our users needs above our own has made us all feel warm and fuzzy,
we need to spend a little time tackling the technical debt that we've
accumulated over the quarter. We'll be spending sprint 53 setting up a
build server so that people have easier access to our alpha testing builds,
and we'll be hooking up a dashboard that lets us see our unit tests running
in real time. We'll also be auditing our API usage in preparation for our
final release that supports iOS 6.
We have two stretch goals for the sprint too: getting Jenkins to run our
unit tests when a patch is submitted (which is more complicated than for
other teams for a variety of technical reasons) and having our build server
actually submit beta TestFlight builds to Apple automatically. We're unsure
if we'll get to these tasks, so that's why their stretch goals.
If you have any questions, feel free to let me know!
Thanks,
Dan
--
Dan Garry
Associate Product Manager, Mobile Apps
Wikimedia Foundation
--
Dan Garry
Associate Product Manager, Mobile Apps
Wikimedia Foundation