On Thu, 22 Oct 2020 at 16:18, wrote:
>
> Hi,
>
> Last release 1.8.26 was issued on 2020-08-03. There are currently 20
> patches in the queue cut down this way:
> - 10 MEDIUM, first one merged on 2020-08-05
> - 10 MINOR, first one merged on 2020-08-03
>
> Thus the computed ideal relea
On Thu, Oct 22, 2020 at 08:41:35PM +0200, William Lallemand wrote:
> On Thu, Oct 22, 2020 at 10:20:12PM +0500, Илья Шипицин wrote:
> > can we backport
> > http://git.haproxy.org/?p=haproxy.git;a=commit;h=b3201a3e077198b3f75ebe8661aa45589b811552
> > to 2.1 as well ? it was not scheduled, but it is r
On Thu, Oct 22, 2020 at 10:20:12PM +0500, Илья Шипицин wrote:
> can we backport
> http://git.haproxy.org/?p=haproxy.git;a=commit;h=b3201a3e077198b3f75ebe8661aa45589b811552
> to 2.1 as well ? it was not scheduled, but it is required to fix BoringSSL
> builds
>
BoringSSL does not have any maintenanc
can we backport
http://git.haproxy.org/?p=haproxy.git;a=commit;h=b3201a3e077198b3f75ebe8661aa45589b811552
to 2.1 as well ? it was not scheduled, but it is required to fix BoringSSL
builds
чт, 22 окт. 2020 г. в 20:19, :
> Hi,
>
> This is a friendly bot that watches fixes pending for the next
> hap
Hi,
This is a friendly bot that watches fixes pending for the next haproxy-stable
release! One such e-mail is sent periodically once patches are waiting in the
last maintenance branch, and an ideal release date is computed based on the
severity of these fixes and their merge date. Responses t
5 matches
Mail list logo