{"issue":{"milestone":null,"user":{"login":"lloyd","id":39411,"url":"https://api.github.com/users/lloyd","avatar_url":"https://secure.gravatar.com/avatar/5810c72f30b0ab202823d8c26460c39d?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"5810c72f30b0ab202823d8c26460c39d"},"title":"repair .channel internal API in dev","created_at":"2011-12-17T01:55:52Z","labels":[],"updated_at":"2011-12-17T01:55:52Z","state":"open","id":2587056,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"html_url":"https://github.com/mozilla/browserid/issues/768","closed_at":null,"body":"lloyd br0k3 with issue #766\r\n\r\nben will clean up his mess.\r\n\r\nThe apps team says they are interested in moving to the new internal APIs, however they'd like at least till the 12th:\r\n\r\n    15:27 < anant> 1. is it possible to not remove the old BrowserID API on 1/5? pushing it out a week, say 1/12 would help get the apps add-on that uses the new API on time\r\n\r\nSo plan of record would seem to be to continue to support channel for now, while aggressively moving all native clients over to the internal api.  /cc @benadida /cc @anantn /cc @wfwalker /cc @shane-tomlinson ","number":768,"url":"https://api.github.com/repos/mozilla/browserid/issues/768","comments":0,"assignee":null},"action":"opened"}