TODO: fill out epic template
Corollary: Wikipedia iOS repo's main (master) branch is always in a deployable state.
Subtasks
- Implement packaging & deploying scripts in the iOS repo Done: using fastlane
- Configure CI job to be triggered after master is updated
- Setup build slave to be able to push changes to git remote
- Establish feedback loop between job results & developers
Acceptance criteria
Given I am working on the Wikipedia iOS repo
When I signal that a change should be merged
Then CI should run a job configured by iOS engineers
And the job should lint, test, package, and deploy the changes as a new version of the app
And when the job finishes, I should give the developers feedback on the results
Copy the description below when making Epics
(format was created from comments on this ether pad: https://etherpad.wikimedia.org/p/Q1_Epic_and_story_creation)
Definition Progress
The following is a checklist for completion of the definition of the Epic. Make sure to check these off as you complete each item.
- Summary
- Rationale
- Success Metrics
- External Dependencies
- Unknowns
- Product Plan
- Prototyping
- MVP
- User stories
- User Story Phab Tickets
- Metrics Implementation
- Metrics Phab Tickets
- Estimates
- Delivery Date
Summary
As a Wikipedia iOS project contributor, my changes are automatically deployed to testers after being merged.
Goal Visibility
Is this goal an internal Readership Goal or a WMF quarterly goal.
Rationale
Explain how this Epic came to be. User feedback, Metrics, Appstore reviews, Internal WMF goals/mission, Product or UX driven.
Success Metrics
Define the metrics criteria for success. Explain why they are a valid measure of success.
External Dependencies
List out any known dependencies on other teams / services / APIs.
Unknowns
List out anything you don't know that will need to be understood before the Epic can be completed.
Product Plan
Prototyping
Are prototypes needed? If so, what is the purpose - what do we need to understand before implementing? How do we validate/test the prototype? What is the audience size?
MVP
What needs to be accomplished for this task to be considered done and shipped to users? What is the minimum feature set needed to accomplish this.
User Stories
Write out the user stories needed to accomplish this goal. Each of these user stories should become a Phab ticket. Link to each Phab ticket here.
User Story | Ticket |
---|---|
A user should be able to use this feature | TXXXXXX |
A user should feel good after using this feature | TXXXXXX |
Metrics Implementation
Define any tasks needed to be completed to enable the success metrics to measured. Create a Phab task and link to it here.
Timeline Estimate
List estimates below. These do not have to be exact. These are just used to validate proposed timelines and ship dates.
Task | Estimate |
---|---|
Prototyping | 1 week |
User Testing | 2 weeks |
Mockups | 2 weeks |
Development | 2 weeks |
Beta Testing | 1 week |
Delivery Estimate
What is the estimated ship date to end users?