#5933 BLOC Update.: point update.1 to a different jabber server address

[Zarro Boogs per Child]

#5933: point update.1 to a different jabber server address
-----------------------+----------------------------------------------------
  Reporter:  robot101  |       Owner:  jg      
      Type:  defect    |      Status:  new     
  Priority:  blocker   |   Milestone:  Update.1
 Component:  distro    |     Version:          
Resolution:            |    Keywords:          
  Verified:  0         |    Blocking:          
 Blockedby:            |  
-----------------------+----------------------------------------------------

Comment(by morgs):

 ixo, we do not yet have a scalable server solution that will handle
 arbitrary numbers of G1G1 users, nor do we have multiple servers working.
 As for Ship.2, we will most likely point the default jabber server at an
 as-yet non-working DNS name, which we could activate in the future when we
 have addressed the server issues. It will be important which version of
 the Sugar distro is running when we do so, since we anticipate client-side
 changes which would probably not work with Ship.2 builds (G1G1 to date),
 so we shouldn't reuse the ship2.jabber.laptop.org address.

 Unless serendipitous events occur in the time remaining before release,
 the outcome of this ticket will be to point the default jabber server at
 "update1.jabber.laptop.org" or something similar.

-- 
Ticket URL: <http://dev.laptop.org/ticket/5933#comment:3>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system