Re: Bug#839250 - gunicorn backport >= 19.6.0-6

[Chris Lamb <lamby@debian.org>]

> > Right, but that's for stretch where the sysadmin will be clearly be
> > more aware of and/or even looking for issues. I don't want to break
> > existing systems right now.
 
> So how are packages using gunicorn to handle support for both stretch
> and jessie-backports? Packages in jessie can't be changed, so changes
> need to take place in backports to prepare for stretch. 
 
> Adding packages from backports should be about preparing for the next
> stable release.

I completely understand that and strongly agree, but *weighed up against*
breaking existing stable-based systems I relaly feel it the worst of two
bad options to upload it to backports.

I mean, I know I have deployed systems that--if they were to blindly
upgrade from backports after such an upload--would have a broken system!


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org / chris-lamb.co.uk
       `-