#4663 BLOC Update.: Connect: doesn't get into a consistent state on joining
Zarro Boogs per Child
bugtracker at laptop.org
Tue Nov 6 06:17:26 EST 2007
#4663: Connect: doesn't get into a consistent state on joining
-------------------------------+--------------------------------------------
Reporter: smcv | Owner: morgs
Type: defect | Status: new
Priority: blocker | Milestone: Update.1
Component: connect-activity | Version:
Resolution: | Keywords: collaboration
Verified: 0 |
-------------------------------+--------------------------------------------
Changes (by smcv):
* cc: ApprovalForUpdate (added)
Comment:
(cc'ing ApprovalForUpdate as a proxy for "Jim, Kim and Walter" - hopefully
its email goes somewhere useful?)
What is Connect doing as an Update.1 candidate in the first place? It's a
demo of Tubes functionality, and is maintained as such. We don't have the
resources to maintain it as a user-friendly activity with features and UI
(its maintainer is "morgs whenever he isn't working on PS and Sugar") so
if you want it in a state where it can be shipped to children, I think
someone else from laptop.org will have to take on maintenance.
We should definitely fix this bug, because Connect is an example activity
whose correctness developers rely on, but I don't think Connect should be
shipped to the children, who will be frustrated and confused by bugs like:
http://dev.laptop.org/query?status=assigned&status=new&status=reopened&component
=connect-
activity&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component
In my view, the ideal situation would be that Connect remains on Joyride
images (because it makes a useful smoke-test for Tubes, with no external
dependencies) but never propagates to Update.1, or perhaps that it
propagates to Update.1 but is removed shortly before release.
--
Ticket URL: <http://dev.laptop.org/ticket/4663#comment:4>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system
More information about the Bugs
mailing list