Difference between revisions of "Development:Planning:Software Update"
Jump to navigation
Jump to search
(herewith some updates, and a table we can use to compare) |
(→Comparison Table: fix bug; fill in a few mozUpdate cells) |
||
| Line 29: | Line 29: | ||
==Comparison Table== | ==Comparison Table== | ||
| − | <table class="fullwidth-table"> | + | <table class="fullwidth-table" width="100%"> |
<tr> | <tr> | ||
<th style="width:100px">Requirement</th> | <th style="width:100px">Requirement</th> | ||
| Line 39: | Line 39: | ||
<tr> | <tr> | ||
<td>Can build as 10.3/10.4 Universal</td> | <td>Can build as 10.3/10.4 Universal</td> | ||
| − | <td></td> | + | <td {{GreenCell}}>Yes</td> |
<td></td> | <td></td> | ||
<td></td> | <td></td> | ||
| Line 46: | Line 46: | ||
<tr> | <tr> | ||
<td>License</td> | <td>License</td> | ||
| − | <td></td> | + | <td {{GreenCell}}>Tri-License</td> |
<td></td> | <td></td> | ||
<td></td> | <td></td> | ||
| Line 53: | Line 53: | ||
<tr> | <tr> | ||
<td>cvs Approval</td> | <td>cvs Approval</td> | ||
| − | <td></td> | + | <td {{GreenCell}}>In tree</td> |
<td></td> | <td></td> | ||
<td></td> | <td></td> | ||
| Line 60: | Line 60: | ||
<tr> | <tr> | ||
<td>Can land source code<br>(instead of binary drops)</td> | <td>Can land source code<br>(instead of binary drops)</td> | ||
| − | <td></td> | + | <td {{GreenCell}}>In tree</td> |
<td></td> | <td></td> | ||
<td></td> | <td></td> | ||
| Line 169: | Line 169: | ||
<tr> | <tr> | ||
<td colspan=4>Other concerns</td> | <td colspan=4>Other concerns</td> | ||
| + | </tr> | ||
| + | |||
| + | <tr> | ||
<td>Expanded QA requirements</td> | <td>Expanded QA requirements</td> | ||
<td></td> | <td></td> | ||
| Line 184: | Line 187: | ||
<tr> | <tr> | ||
<td>Complexity added to the app<br />''e.g.'' wrapping Gecko</td> | <td>Complexity added to the app<br />''e.g.'' wrapping Gecko</td> | ||
| − | |||
<td></td> | <td></td> | ||
<td></td> | <td></td> | ||
| Line 202: | Line 204: | ||
<tr> | <tr> | ||
| − | <td> | + | <td> </td> |
| − | <td | + | <td {{GreenCell}}>Present</td> |
| − | <td | + | <td {{YellowCell}}>Unknown</td> |
| − | <td | + | <td {{RedCell}}>Missing</td> |
<!--<td style="background: #88F;">Completed/waiting for files</td>--> | <!--<td style="background: #88F;">Completed/waiting for files</td>--> | ||
</tr> | </tr> | ||
</table> | </table> | ||
Revision as of 18:08, 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
- en-only and ML Camino
- what if your language drops from ML in a major update?
- Automated generation of update and update notification
Potential requirements
- Resuming lost connections
- Background/throttled downloads
- Remind me later
- Install update later
Concerns
- QA
- Documentation
- Gecko
- Well-maintained
Comparison Table
| Requirement | mozUpdate | Sparkle | Option 3 |
|---|---|---|---|
| Can build as 10.3/10.4 Universal | Yes | ||
| License | Tri-License | ||
| cvs Approval | In tree | ||
| Can land source code (instead of binary drops) |
In tree | ||
| Uses https for binary downloads | |||
| Uses https for "need to update" notice downloads | |||
| https server available | |||
| Supports fine-grained checking for version/OS pairs | |||
| Can disable update checking within Camino | |||
| Verifies user has permission to update first | |||
| Can enable updates/update checking only in official release builds | |||
| Can handle ML as well as en-only Camino | |||
| Release automation | |||
| Desirables | |||
| Support for resuming lost connections | |||
| Can download in background | |||
| Can download at low speed to not affect connection | |||
| Can remind to download later | |||
| Can install later once downloaded | |||
| Other concerns | |||
| Expanded QA requirements | |||
| Documentation | |||
| Complexity added to the app e.g. wrapping Gecko |
|||
| Actively maintained and supported | |||
| Color key | |||
| Present | Unknown | Missing | |
