On 21/11/14 17:35, Niels Thykier wrote: > Control: tags -1 moreinfo > > On 2014-11-10 18:37, Daniel Pocock wrote: >> [...] >> >> I understand there are policies for the freeze >> > > Hi, > > I believe some of this was debated over IRC on the same day you sent > your mail. I will not comment on those parts. > >> [...] >> >> Furthermore, JSCommunicator 2.x has not changed from an API user >> perspective. The only dependent package is drupal7-mod-drucall and I >> have updated that so everything works together and gives Debian users >> the optimal experience. >> > > If JSCommunicator changes API in backwards incompatible manner, then you > should have done this before the transition freeze. That was two months > before the freeze itself. > > Is this upload of JSCommunicator breaking the API?
No, it does not break the API, it simply adds some extra API features (new options in config.js). The main API is async messaging through ArbiterJS and that hasn't changed at all. It is the browsers that have been tweaking the API and implementation details of WebRTC. JsSIP abstracts some of that and I built JSCommunicator on top of JsSIP with the aim of abstracting it even further so that web developers have something stable to work with. > >>> Would you prefer to have jscommunicator at its current version (1.1.1-1) >>> in Jessie or do you feel that we would be better off without it? >> >> >> [...] If Debian policy brings us to the point where people are >> actively talking about removing WebRTC capabilities from testing less >> than a week into the freeze then the policy is not working in the best >> interest of Debian's mission or openness in general. >> >> [...] > > My counter argument is: > > """ > It is not in the best interest of Debian's mission or openness in > general for the Debian release to drag on for months, because the freeze > policy is ignored. See "Squeeze Freeze" and "Wheezy Freeze". > """ > I agree and I remember the wheezy freeze well. I uploaded this as soon as reasonably possible after new dependencies entered the archive in October. If it wasn't for that I would have uploaded in August, the same time this code went live on rtc.debian.org -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/546f856a.5030...@pocock.pro
