+1

Aaron West

Loadbalancer.org Ltd.
www.loadbalancer.org <https://www.loadbalancer.org/?gclid=ES2017>

  <https://plus.google.com/+LoadbalancerOrg>
<https://twitter.com/loadbalancerorg>
<http://www.linkedin.com/company/3191352?trk=prof-exp-company-name>
<https://www.loadbalancer.org/?category=company&post-name=overview&?gclid=ES2017>
<https://www.loadbalancer.org/?gclid=ES2017>
+1 888 867 9504 / +44 (0)330 380 1064
aa...@loadbalancer.org

LEAVE A REVIEW
<http://collector.reviews.io/loadbalancer-org-inc-/new-review> | DEPLOYMENT
GUIDES
<https://www.loadbalancer.org/?category=resources&post-name=deployment-guides&?gclid=ES2017>
 | BLOG <https://www.loadbalancer.org/blog/?gclid=ES2017>

On 2 January 2018 at 15:34, Pavlos Parissis <pavlos.paris...@gmail.com>
wrote:

> On 02/01/2018 04:23 μμ, Jonathan Matthews wrote:
> > On 2 January 2018 at 15:12, Willy Tarreau <w...@1wt.eu> wrote:
> >> So please simply voice in. Just a few "please keep it alive" will be
> >> enough to convince me, otherwise I'll mark it unmaintained.
> >
> > I don't use 1.4, but I do have a small reason to say please *do* mark
> > it as unmaintained.
> >
> > The sustainability of haproxy is linked to the amount of work you (and
> > a /relatively/ small set of people) both have to do and want to do.
> > I would very much like it to continue happily, so I would vote to
> > reduce your mental load and to mark 1.4 as unmaintained.
> >
>
> +1
>
> BTW: I don't use/look at haproxy 1.5 version as well...
>
> Cheers,
> Pavlos
>
>

Reply via email to