Ticket #6747 (closed defect: fixed)

Opened 7 years ago

Last modified 6 years ago

Messaging preparation for releasing Update.1

Reported by: mstone Owned by: mstone
Priority: blocker Milestone: Update.1
Component: distro Version:
Keywords: release? Cc: hhardy, holt, kimquirk, sj
Action Needed: never set Verified: no
Deployments affected: Blocked By:


hhardy and I inquired about how an inexperienced user updating from 656 machine to an U.1 release candidate might respond to the "disappearance" of their activities. The results indicate that there is much preparation to be done.

Change History

Changed 7 years ago by mstone

Some media that particularly need some love include "messages that the user reads before updating", Google, the Support FAQ, the wiki Front Page, release notes pages, olpc-update page, update paths page, the forums, and mailing lists.

Changed 7 years ago by mstone

We also might want to include a warning in the Journal resume failure path that warns people whose activities have disappeared that they need to procure an activity to use to resume their frozen instances.

Changed 7 years ago by bert

Couldn't an intermediate update be released that moves activities from /usr/share/activities to /home/olpc/Activities? It's asking for much trouble to expect coping with the missing activities for non-developers.

Changed 7 years ago by holt

MStone is thinking about how to do the hard work of preparing the general public (EG. 80,000+ Give1Get1 donors and others) helping them decide whether to upgrade or not, and understanding all the consequences -- starting in places like:


which is the same as,


Please contact him and I personally if you can help!

Changed 6 years ago by cscott

  • next_action set to never set
  • blockedby 7495 added

Dup of #7495 now?

Changed 6 years ago by mstone

  • blockedby 7495 removed

(In #7495) #6747 is just a zombie ticket left over from U.1.

Changed 6 years ago by mstone

  • status changed from new to closed
  • resolution set to fixed
  • milestone changed from 8.2.0 (was Update.2) to Update.1

I think it's just a zombie ticket that wasn't closed when U.1 was released.

Note: See TracTickets for help on using tickets.