Closed Bug 1000012 Opened 11 years ago Closed 10 years ago

Separate out MozLoop code from MozSocial

Categories

(Hello (Loop) :: Client, defect, P1)

Product:
Hello (Loop)
Component:
Client
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1000007
Milestone:
mozilla32
Blocking Flags:
backlog Fx32+

People

(Reporter: standard8, Assigned: markh)

References

Details

(Whiteboard: [p=3, est:3d, 1.5:p2, ft:webrtc][s=mlpnightly1])

User Story

* Separate out a new MozLoop object from MozSocial, and build a panel, and chat windows based around the new object.
* Review content-space unit test console errors, as some of these represent buggy tests (eg the CORS error probably means that we're not stubbing out something we should be).
* Ensure it is all working
We're currently investigating separating out the Loop code from the Social code. Bug 976109 comment 30 has the current details of the branch and work in-progress.
User Story: (updated)
Blocks: 995130
User Story: (updated)
Blocks: 974875
No longer blocks: 995130
backlog: --- → Fx32+
Priority: -- → P1
Whiteboard: [p=3, est:3d, 1.5:p2, ft:webrtc]
Target Milestone: --- → mozilla32
Depends on: 1002914
Whiteboard: [p=3, est:3d, 1.5:p2, ft:webrtc] → [p=3, est:3d, 1.5:p2, ft:webrtc][s=mlpnightly1]
Bug 1000007 has basically taken this over by integrating these two together.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
No longer depends on: 1002914
You need to log in before you can comment on or make changes to this bug.