Daniel, I already told you in IRC, but as I now have an email to reply to: This new email format is much better than the old one.
I have a few more small suggestions inline below: Am 26.02.20 um 01:00 schrieb [email protected]: > 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 7 patches > in the queue cut down this way: > - 1 MAJOR, first one merged on 2020-02-21 > - 1 MEDIUM, first one merged on 2020-02-21 > - 5 MINOR, first one merged on 2020-02-21 Consider aligning the "first one ..." part to avoid that jagged formatting, due to MEDIUM (and CRITICAL, though I assume we'll never see that) being longer the the other severities. Make sure to test two-digit patch numbers. > Thus the computed ideal release date for 2.1.4 would be 2020-03-06, which is > in two weeks or less. > > Last release 2.0.13 was issued on 2020-02-13. There are currently 5 patches > in the queue cut down this way: > - 1 MAJOR, first one merged on 2020-02-21 > - 1 MEDIUM, first one merged on 2020-02-21 > - 3 MINOR, first one merged on 2020-02-21 > > Thus the computed ideal release date for 2.0.14 would be 2020-03-06, which is > in two weeks or less. > > 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.0, 2.1 - MEDIUM : muxes: Use the right argument when > calling the destroy method. > - 2.0, 2.1 - MINOR : filters: Count HTTP headers as > filtered data but don't forward them > - 2.0, 2.1 - MINOR : namespace: avoid closing fd when > socket failed in my_socketat > - 2.0, 2.1 - MINOR : http-ana: Matching on monitor-uri > should be case-sensitive > - 2.1 - MINOR : http-htx: Don't return error if > authority is updated without changes > - 2.1 - MINOR : mux-fcgi: Forbid special characters > when matching PATH_INFO param > > --- Consider replacing "---" with "-- " (including the space after the hyphens). It will then be treated as an email signature (RFC 3676#4.3). My email client automatically tones down the color of signatures and strips them when replying. And de facto this last paragraph is a signature. > 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. > Best regards Tim Düsterhus
