Mobile/Projects/Add-on definition: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 6: | Line 6: | ||
* Use our current distribution file mechanism | * Use our current distribution file mechanism | ||
* Add the ability to state which add-ons should be included / bundled for a particular distribution partner | * Add the ability to state which add-ons should be included / bundled for a particular distribution partner | ||
* Settings must be preserved with each software update | |||
== User stories == | == User stories == | ||
Latest revision as of 21:34, 13 June 2013
Overview/Goals
- Add the ability to define which add-ons are included for a particular partner within the distribution file
Specifications
- Use our current distribution file mechanism
- Add the ability to state which add-ons should be included / bundled for a particular distribution partner
- Settings must be preserved with each software update
User stories
- As a partner, I want to define which add-ons should be distributed for my particular audience, so I have the ability to create the perfect, custom package for my users.
Quality criteria
- User stories are satisfied
- Specifications are met
Implementation
- bug 872806 - Distribution support for add-ons