How to get Supervisor bug in Ubuntu 16.04 LTS fixed?

[Peter Odding]

Dear Ubuntu developers,

The output of $(dpkg-query --show --showformat='${Maintainer}' 
supervisor) brought me to this list. According to 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss this list 
serves the purpose of a "point of contact for Ubuntu users to reach 
Ubuntu developers" and I am writing to you from this perspective.

In Ubuntu 10.04, 12.04 and 14.04 after running `apt-get install 
supervisor' the Supervisor daemon would automatically be enabled (to 
start on boot) and started (so that Supervisor was running by the time 
apt-get returned).

Shortly after trying out Ubuntu 16.04 I found out that the Supervisor 
daemon is no longer automatically enabled nor is it started during 
installation. This breaks compatibility with previous and expected 
behavior. In June '16 I reported this issue as a bug against the 
supervisor package on Launchpad.net: https://bugs.launchpad.net/bugs/1594740

Apart from people confirming that the problem affected them it was quiet 
in that bug report for a while, but a few hours ago the Debian package 
maintainer replied that the bug was recently fixed in Debian unstable! 
This leaves me wondering if there is a remote chance of getting this bug 
fix into Ubuntu 16.04 (given that 16.04 is the latest Ubuntu LTS release 
and it will be for quite a while)...

The supervisor release in Debian unstable that fixes this issue combines 
several unrelated changes (as far as I can judge) including a new 
upstream release of the supervisor package, so I don't suppose anyone 
will be amused by the idea of simply copying the Debian unstable package 
to Ubuntu 16.04 LTS which was released quite a few months ago :-).

Is there another way to get this bug fix into Ubuntu 16.04? I'm willing 
to back port the minimal changes required to have correct maintainer 
scripts generated :-) but I wouldn't know how to actually get the 
changes into a released version of Ubuntu...

Long story short: Who do I contact to either 1) prod them to fix the bug 
or 2) guide me in getting the bug fixed?

Thanks for reading,

Peter Odding