Re: stable-bot: Bugfixes waiting for a release 2.1 (21), 2.0 (16)
On 31 Mar 17:14, Willy Tarreau wrote: > On Tue, Mar 24, 2020 at 04:46:43PM +0100, Tim Düsterhus wrote: > > > Could you please cut a release ? there are many fixes that just cherry > > > picking it in my fork would make sense. > > > > I second that. I was already thinking about asking after yesterday's > > 2.2-dev5. > > I'm aiming at Thursday. Still working on the backports. I know sometimes > we're lagging behind a lot, but when you consider that backports can take > up to 50% of the work time, and more importantly that many times it can > divert you by 3 hours for something that was expected to take 10 seconds, > it's easy to understand why they're often handled in batches :-/ > > Willy No worries. The goal is not to put pressure on the maintainers, also I did not insist after my first mail. Take your time, thanks! -- (o-Julien Pivotto //\Open-Source Consultant V_/_ Inuits - https://www.inuits.eu signature.asc Description: PGP signature
Re: stable-bot: Bugfixes waiting for a release 2.1 (21), 2.0 (16)
On Tue, Mar 24, 2020 at 04:46:43PM +0100, Tim Düsterhus wrote: > > Could you please cut a release ? there are many fixes that just cherry > > picking it in my fork would make sense. > > I second that. I was already thinking about asking after yesterday's > 2.2-dev5. I'm aiming at Thursday. Still working on the backports. I know sometimes we're lagging behind a lot, but when you consider that backports can take up to 50% of the work time, and more importantly that many times it can divert you by 3 hours for something that was expected to take 10 seconds, it's easy to understand why they're often handled in batches :-/ Willy
stable-bot: Bugfixes waiting for a release 2.1 (21), 2.0 (16)
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 to this mail must be sent to the mailing list. Last release 2.1.3 was issued on 2020-02-12. There are currently 21 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2020-02-21 - 6 MEDIUM, first one merged on 2020-02-21 - 13 MINOR, first one merged on 2020-02-21 Thus the computed ideal release date for 2.1.4 would be 2020-03-06, which was two weeks ago. Last release 2.0.13 was issued on 2020-02-13. There are currently 16 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020-02-21 - 6 MEDIUM, first one merged on 2020-02-21 - 9 MINOR, first one merged on 2020-02-21 Thus the computed ideal release date for 2.0.14 would be 2020-03-06, which was two weeks ago. The current list of patches in the queue is: - 2.0, 2.1 - MAJOR : http-ana: Always abort the request when a tarpit is triggered - 2.1 - MAJOR : list: fix invalid element address calculation - 2.0, 2.1 - MEDIUM : muxes: Use the right argument when calling the destroy method. - 2.0, 2.1 - MEDIUM : ssl: fix several bad pointer aliases in a few sample fetch functions - 2.0, 2.1 - MEDIUM : shctx: make sure to keep all blocks aligned - 2.0, 2.1 - MEDIUM : ebtree: don't set attribute packed without unaligned access support - 2.0, 2.1 - MEDIUM : random: implement a thread-safe and process-safe PRNG - 2.0, 2.1 - MEDIUM : random: initialize the random pool a bit better - 2.0, 2.1 - MINOR : dns: ignore trailing dot - 2.0, 2.1 - MINOR : namespace: avoid closing fd when socket failed in my_socketat - 2.0, 2.1 - MINOR : sample: fix the json converter's endian-sensitivity - 2.1 - MINOR : h2: reject again empty :path pseudo-headers - 2.0, 2.1 - MINOR : connection: make sure to correctly tag local PROXY connections - 2.1 - MINOR : http-htx: Don't return error if authority is updated without changes - 2.0, 2.1 - MINOR : http-ana: Matching on monitor-uri should be case-sensitive - 2.0, 2.1 - MINOR : checks/threads: use ha_random() and not rand() - 2.0, 2.1 - MINOR : filters: Count HTTP headers as filtered data but don't forward them - 2.1 - MINOR : mux-fcgi: Forbid special characters when matching PATH_INFO param - 2.1 - MINOR : http-htx: Do case-insensive comparisons on Host header name - 2.0, 2.1 - MINOR : sample: Make sure to return stable IDs in the unique-id fetch - 2.0, 2.1 - MINOR : http: http-request replace-path duplicates the query string -- The haproxy stable-bot is freely provided by HAProxy Technologies to help improve the quality of each HAProxy release. If you have any issue with these emails or if you want to suggest some improvements, please post them on the list so that the solutions suiting the most users can be found.
Re: stable-bot: Bugfixes waiting for a release 2.1 (21), 2.0 (16)
Julien, List, Am 24.03.20 um 16:41 schrieb Julien Pivotto: > Dear list, > > We are facing some of the bugs fixed in the 2.1 branch (in particular the > replace-path bug). There are more bugs that have not even been backported, yet. I believe some even have been "skipped" / the RNG changes have been picked out-of-order. > Could you please cut a release ? there are many fixes that just cherry > picking it in my fork would make sense. I second that. I was already thinking about asking after yesterday's 2.2-dev5. Best regards Tim Düsterhus
Re: stable-bot: Bugfixes waiting for a release 2.1 (21), 2.0 (16)
Dear list, We are facing some of the bugs fixed in the 2.1 branch (in particular the replace-path bug). Could you please cut a release ? there are many fixes that just cherry picking it in my fork would make sense. Thanks :) Note: the bot says that the ideal date was 2020-03-06 :) On 18 Mar 00:00, stable-...@haproxy.com wrote: > 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 to this mail > must be sent to the mailing list. > > > Last release 2.1.3 was issued on 2020-02-12. There are currently 21 patches > in the queue cut down this way: > - 2 MAJOR, first one merged on 2020-02-21 > - 6 MEDIUM, first one merged on 2020-02-21 > - 13 MINOR, first one merged on 2020-02-21 > > Thus the computed ideal release date for 2.1.4 would be 2020-03-06, which was > one week ago. > > Last release 2.0.13 was issued on 2020-02-13. There are currently 16 patches > in the queue cut down this way: > - 1 MAJOR, first one merged on 2020-02-21 > - 6 MEDIUM, first one merged on 2020-02-21 > - 9 MINOR, first one merged on 2020-02-21 > > Thus the computed ideal release date for 2.0.14 would be 2020-03-06, which > was one week ago. > > The current list of patches in the queue is: > - 2.1 - MAJOR : list: fix invalid element address > calculation > - 2.0, 2.1 - MAJOR : http-ana: Always abort the request > when a tarpit is triggered > - 2.0, 2.1 - MEDIUM : shctx: make sure to keep all blocks > aligned > - 2.0, 2.1 - MEDIUM : muxes: Use the right argument when > calling the destroy method. > - 2.0, 2.1 - MEDIUM : ebtree: don't set attribute packed > without unaligned access support > - 2.0, 2.1 - MEDIUM : random: implement a thread-safe and > process-safe PRNG > - 2.0, 2.1 - MEDIUM : random: initialize the random pool a > bit better > - 2.0, 2.1 - MEDIUM : ssl: fix several bad pointer aliases > in a few sample fetch functions > - 2.0, 2.1 - MINOR : connection: make sure to correctly > tag local PROXY connections > - 2.1 - MINOR : http-htx: Don't return error if > authority is updated without changes > - 2.0, 2.1 - MINOR : checks/threads: use ha_random() and > not rand() > - 2.0, 2.1 - MINOR : sample: Make sure to return stable > IDs in the unique-id fetch > - 2.1 - MINOR : mux-fcgi: Forbid special characters > when matching PATH_INFO param > - 2.0, 2.1 - MINOR : dns: ignore trailing dot > - 2.0, 2.1 - MINOR : filters: Count HTTP headers as > filtered data but don't forward them > - 2.0, 2.1 - MINOR : http-ana: Matching on monitor-uri > should be case-sensitive > - 2.1 - MINOR : http-htx: Do case-insensive > comparisons on Host header name > - 2.0, 2.1 - MINOR : namespace: avoid closing fd when > socket failed in my_socketat > - 2.1 - MINOR : h2: reject again empty :path > pseudo-headers > - 2.0, 2.1 - MINOR : sample: fix the json converter's > endian-sensitivity > - 2.0, 2.1 - MINOR : http: http-request replace-path > duplicates the query string > > -- > The haproxy stable-bot is freely provided by HAProxy Technologies to help > improve the quality of each HAProxy release. If you have any issue with > these emails or if you want to suggest some improvements, please post them on > the list so that the solutions suiting the most users can be found. > -- (o-Julien Pivotto //\Open-Source Consultant V_/_ Inuits - https://www.inuits.eu signature.asc Description: PGP signature
stable-bot: Bugfixes waiting for a release 2.1 (21), 2.0 (16)
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 to this mail must be sent to the mailing list. Last release 2.1.3 was issued on 2020-02-12. There are currently 21 patches in the queue cut down this way: - 2 MAJOR, first one merged on 2020-02-21 - 6 MEDIUM, first one merged on 2020-02-21 - 13 MINOR, first one merged on 2020-02-21 Thus the computed ideal release date for 2.1.4 would be 2020-03-06, which was one week ago. Last release 2.0.13 was issued on 2020-02-13. There are currently 16 patches in the queue cut down this way: - 1 MAJOR, first one merged on 2020-02-21 - 6 MEDIUM, first one merged on 2020-02-21 - 9 MINOR, first one merged on 2020-02-21 Thus the computed ideal release date for 2.0.14 would be 2020-03-06, which was one week ago. The current list of patches in the queue is: - 2.1 - MAJOR : list: fix invalid element address calculation - 2.0, 2.1 - MAJOR : http-ana: Always abort the request when a tarpit is triggered - 2.0, 2.1 - MEDIUM : shctx: make sure to keep all blocks aligned - 2.0, 2.1 - MEDIUM : muxes: Use the right argument when calling the destroy method. - 2.0, 2.1 - MEDIUM : ebtree: don't set attribute packed without unaligned access support - 2.0, 2.1 - MEDIUM : random: implement a thread-safe and process-safe PRNG - 2.0, 2.1 - MEDIUM : random: initialize the random pool a bit better - 2.0, 2.1 - MEDIUM : ssl: fix several bad pointer aliases in a few sample fetch functions - 2.0, 2.1 - MINOR : connection: make sure to correctly tag local PROXY connections - 2.1 - MINOR : http-htx: Don't return error if authority is updated without changes - 2.0, 2.1 - MINOR : checks/threads: use ha_random() and not rand() - 2.0, 2.1 - MINOR : sample: Make sure to return stable IDs in the unique-id fetch - 2.1 - MINOR : mux-fcgi: Forbid special characters when matching PATH_INFO param - 2.0, 2.1 - MINOR : dns: ignore trailing dot - 2.0, 2.1 - MINOR : filters: Count HTTP headers as filtered data but don't forward them - 2.0, 2.1 - MINOR : http-ana: Matching on monitor-uri should be case-sensitive - 2.1 - MINOR : http-htx: Do case-insensive comparisons on Host header name - 2.0, 2.1 - MINOR : namespace: avoid closing fd when socket failed in my_socketat - 2.1 - MINOR : h2: reject again empty :path pseudo-headers - 2.0, 2.1 - MINOR : sample: fix the json converter's endian-sensitivity - 2.0, 2.1 - MINOR : http: http-request replace-path duplicates the query string -- The haproxy stable-bot is freely provided by HAProxy Technologies to help improve the quality of each HAProxy release. If you have any issue with these emails or if you want to suggest some improvements, please post them on the list so that the solutions suiting the most users can be found.
