[Pkg-haproxy-maintainers] Recommended strategy for running 1.5 in production

[Apollon Oikonomopoulos]

Hi Vincent,

On 12:05 Sat 19 Apr     , Vincent Bernat wrote:
>  ❦ 16 avril 2014 20:22 CEST, Apollon Oikonomopoulos <apoikos at debian.org> :
> 
> >> > An official Ubuntu dev repo will also make testing easier.
> >> > It's much easier to use a apt-get than building from source and figuring
> >> > out command line options.
> >
> > Actually Vincent Bernat maintains a PPA with rebuilds of our Debian 
> > packages from experimental, which should be handy for Ubuntu users:
> >
> >   https://launchpad.net/~vbernat/+archive/haproxy-1.5
> 
> If needed, I can move the maintainance of those backports in the team. I
> don't care being alone to do this, this doesn't take much time.
> 
> As for haproxy.debian.net, it is currenly hosted on one of my server. I
> have checked how mozilla.debian.net is done and they are hosted on
> static.debian.org. I think we can do the same thing, even if there is
> some Ubuntu stuff on it (but Ubuntu packages are hosted on Launchpad, so
> no bandwidth from Debian for that).
> 
> What do you think?

Moving the PPA to the team is relatively easy, because it already has 
its own signing key and infrastructure. We could do it if it will save 
you some time and trouble.

Moving haproxy.debian.net OTOH means that we have to either set up a 
separate signing infra (it's currently signed by your own key IIRC), or 
have people trust all team member keys. Since we will not be needing 
haproxy.debian.net anymore after 1.5 is officially released and uploaded 
to unstable (which will be probably soon), I don't think it's worth 
moving it.

Regards,
Apollon