Confirmed users
746
edits
Marketplace/PackagedApps: Difference between revisions
Jump to navigation
Jump to search
added preamble
(formatting to help my aging eyes) |
(added preamble) |
||
| Line 1: | Line 1: | ||
=== Non-engineering implications of a packaged app === | |||
* What is our release schedule? | |||
** ...for Gaia | |||
** ...for the website (in case some iframed packaged apps persist) | |||
* How/How hard should we push people to update their marketplace app? | |||
** How do we push critical bugfixes? | |||
The release schedule is a big deal, because currently we accommodate a lot of last-minute requests and under-planned features. The idea currently is that we can just patch it; "just patch it" with a package becomes a lot dicier unless we can more reliably get people to update. | |||
So, if our production schedule is longer (or has code freeze dates, etc), the impacts could be: | |||
* What happens with a third-party partner change? | |||
* How do we handle feature requests during our production cycle? Is there a cutoff point? | |||
* By when does L10n need to get something? | |||
* By when does QA need to get something? | |||
* How far in advance do features need to be defined? Designed? | |||
=== Packaged app or not === | === Packaged app or not === | ||