Difference between revisions of "Development:Planning:Software Update"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
* can build in a 10.3/10.3.9 SDK/gcc3.3 and 10.4/10.4u/gcc4 Universal configuration | * can build in a 10.3/10.3.9 SDK/gcc3.3 and 10.4/10.4u/gcc4 Universal configuration | ||
* Compatible license | * Compatible license | ||
| − | * Approval to land in cvs (if not using mozUpdate) | + | * Approval to land in cvs (if not using mozUpdate) - mento prefers landing source code instead of binary drops |
* https capabilities | * https capabilities | ||
** Everything needs to be either https or signed (signing is an option for the Sparkle downloads, but there's a logistical issue that would come with that) | ** Everything needs to be either https or signed (signing is an option for the Sparkle downloads, but there's a logistical issue that would come with that) | ||
Revision as of 10:48, 22 August 2007
Requirements
- can build in a 10.3/10.3.9 SDK/gcc3.3 and 10.4/10.4u/gcc4 Universal configuration
- Compatible license
- Approval to land in cvs (if not using mozUpdate) - mento prefers landing source code instead of binary drops
- https capabilities
- Everything needs to be either https or signed (signing is an option for the Sparkle downloads, but there's a logistical issue that would come with that)
- Update checking (OS version, etc.)
- say, 1.6.x updates to 2.0.x at some point unless you're running 10.3, in which case you only get 1.6.x updates
- and if you move to 10.4, do you get re-offered 2.0.x
- provide a way to turn off update checking from inside the app (unlike adium - with apologies to cbarrett for the jab)
- one thing i don't like about sparkle is that it doesn't check to see if you have permission to update the app first
- We should only enable update checking in official release builds
Potential requirements
- Resuming lost connections
- Background/throttled downloads?
Concerns
- QA
- Generation
- Gecko
