Bug#768933: unblock: jscommunicator

[Niels Thykier <niels@thykier.net>]

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?

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

~Niels