[Sugar-devel] [DESIGN] optional automatic updates
quozl at laptop.org
Thu Aug 7 19:03:15 EDT 2014
Oh, that's a pity, I hope someone else understands my questions. ;-)
On Thu, Aug 07, 2014 at 06:34:03PM -0400, Martin Abente wrote:
> Hey James,
> You lost me there :) We definitely have many other improvements we should add
> to the updater, but with this particular feature, only two things happen when a
> activity is "marked" as optional (in the microformat file):
> a) the uptomatic updater (where there is no user interaction) skips that
> activity for upgrade or installation.
> b) the activity is not selected by default in CP updater UI list.
> This way, deployments won't force clients to download some activities (ie., if
> they are too big), but users can still get these updates or new activities if
> they select them in CP updater UI list.
> On Thu, Aug 7, 2014 at 5:58 PM, James Cameron <quozl at laptop.org> wrote:
> On Thu, Aug 07, 2014 at 08:40:26AM -0400, Martin Abente wrote:
> > Thanks for the feedback, please notice that we already support
> > automatic updates. This feature is simply to extend this microformat
> > to mark some activities in the list so they don't get automatically
> > updated or installed (ie., when they are too big for doing it
> > massively).
> The perceived size of a download depends on the actual size, and the
> bandwidth available.
> Does the updater handle stop and continue of download, and give any
> indication of the duration expected? Users will be more willing to
> try massive updates (e.g. new Wikipedia activity) if they can be more
> in control.
> Also, it would be nice if the updater provided updates to nearby
> users. ;-)
> James Cameron
>  mailto:quozl at laptop.org
>  http://quozl.linux.org.au/
More information about the Sugar-devel