point update.1 to a different jabber server address

[robot101]

19:46 < jg> Robot101: please add a trac bug, blocker, asking us to decide on a default jabber server name for Update.1.

[ixo]

Or at least, several jabber servers, and alternate which latop connects to which, and have services shared between them. (i.e. load balancing). (or DNS round-robin setup)

[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.

[marco]

It will be in next joyride: http://koji.fedoraproject.org/koji/taskinfo?taskID=512593

[erikos]

Tested as working in 1758. sugar-control-panel -g jabber is pointing to "update1.jabber.laptop.org"

[erikos]

Is working fine in Update.1(700)