Re: Open bugs report, May 1 2026
> On May 1, 2026, at 10:55 AM, Rich Bowen wrote: > > > >> On May 1, 2026, at 10:29 AM, Mads Toftum wrote: >> >> On Fri, May 01, 2026 at 10:05:15AM -0400, Rich Bowen wrote: >>> >>> On May 1, 2026, at 9:33 AM, Mads Toftum wrote: Would be tempting to close out old reports to get rid of some of the noise. If not by date, then at least close anything on unsupported versions. >>> >>> Yes, that would be fantastic. I’m never a big fan of bulk-closing tickets >>> based on age, but there’s *definitely* a lot of stuff in here against >>> modules that are long-retired, features that no longer exist, and a lot of >>> other ancient history. >>> >> I was thinking more along the lines of 1.3, 2.0 and 2.2 if there's any >> left from those versions. Hmm. I was mistaken.There are: 61 2.2.x bugs 25 2.0.x bugs I’ll run another report here, and see what we can do about bulk closing those with a polite message. — Rich Bowen [email protected]
Re: Open bugs report, May 1 2026
> On May 1, 2026, at 10:29 AM, Mads Toftum wrote: > > On Fri, May 01, 2026 at 10:05:15AM -0400, Rich Bowen wrote: >> >> >>> On May 1, 2026, at 9:33 AM, Mads Toftum wrote: >>> Would be tempting to close out old reports to get rid of some of the >>> noise. If not by date, then at least close anything on unsupported >>> versions. >> >> Yes, that would be fantastic. I’m never a big fan of bulk-closing tickets >> based on age, but there’s *definitely* a lot of stuff in here against >> modules that are long-retired, features that no longer exist, and a lot of >> other ancient history. >> > I was thinking more along the lines of 1.3, 2.0 and 2.2 if there's any > left from those versions. Oh, yeah, those are all gone. >> >> Yeah, there’s a lot of user support stuff in here that isn’t actually a bug >> report. There’s also a lot of tickets where someone did the work, fixed a >> problem, and asked the reporter for their +1 to close, and then it just sat >> and rotted. This kind of stuff is what the AI tools are actually good at, >> and I’m going to do some more digging. >> > Perhaps an approach could be to have AI make suggested responses and > then put a human in the loop before sending? That is my planned approach. I am very reluctant to give any AI agent direct access to the bz API or anything like that, but am trying to see how much I can at least get recommendations on to close stuff. — Rich Bowen [email protected]
Re: Open bugs report, May 1 2026
On Fri, May 01, 2026 at 10:05:15AM -0400, Rich Bowen wrote: > > > > On May 1, 2026, at 9:33 AM, Mads Toftum wrote: > > Would be tempting to close out old reports to get rid of some of the > > noise. If not by date, then at least close anything on unsupported > > versions. > > Yes, that would be fantastic. I’m never a big fan of bulk-closing tickets > based on age, but there’s *definitely* a lot of stuff in here against modules > that are long-retired, features that no longer exist, and a lot of other > ancient history. > I was thinking more along the lines of 1.3, 2.0 and 2.2 if there's any left from those versions. > > Yeah, there’s a lot of user support stuff in here that isn’t actually a bug > report. There’s also a lot of tickets where someone did the work, fixed a > problem, and asked the reporter for their +1 to close, and then it just sat > and rotted. This kind of stuff is what the AI tools are actually good at, and > I’m going to do some more digging. > Perhaps an approach could be to have AI make suggested responses and then put a human in the loop before sending? vh Mads Toftum -- http://flickr.com/photos/q42/
Re: Open bugs report, May 1 2026
> On May 1, 2026, at 10:04 AM, Thomas Meyer wrote: > > Hi, > > "world's most popular web server" - I don't think this is true anymore, > somebody should also update readme which also still claims this. Heh. Yeah, that was put in there by the over-enthusiastic AI agent, and it amused me, so I left it in. I actually made a note to do some digging for places in the docs and website where we make claims based on 2010 Netcraft surveys, and I’ve already fixed a couple of these. — Rich Bowen [email protected]
Re: Open bugs report, May 1 2026
> On May 1, 2026, at 9:33 AM, Mads Toftum wrote: > > On Fri, May 01, 2026 at 08:36:42AM -0400, Rich Bowen wrote: >> I was thinking last night it might be interesting to dig through and figure >> out what would be a good place for a beginner to get started, or whether >> there’s some opportunity for cleanup. >> >> TL:DR - we have almost 1500 open bugs, most of which are ancient history. >> >> Pretty graphs! - http://httpd.rcbowen.com/httpd-open-bugs.html >> > Nice work. > Would be tempting to close out old reports to get rid of some of the > noise. If not by date, then at least close anything on unsupported > versions. Yes, that would be fantastic. I’m never a big fan of bulk-closing tickets based on age, but there’s *definitely* a lot of stuff in here against modules that are long-retired, features that no longer exist, and a lot of other ancient history. > >> I suspect that a *bunch* of them are no longer valid. (There are, for >> example, 3 open bugs against the Win32 MSI Installer) >> > I had a quick look at "Critical & Blocker Bugs" - there's a lot of NEW > reports and perhaps some things that had better gone to users@httpd. Yeah, there’s a lot of user support stuff in here that isn’t actually a bug report. There’s also a lot of tickets where someone did the work, fixed a problem, and asked the reporter for their +1 to close, and then it just sat and rotted. This kind of stuff is what the AI tools are actually good at, and I’m going to do some more digging. — Rich Bowen [email protected]
Re: Open bugs report, May 1 2026
Hi, "world's most popular web server" - I don't think this is true anymore, somebody should also update readme which also still claims this. Mfg Thomas Am 1. Mai 2026 14:36:42 MESZ schrieb Rich Bowen : >I was thinking last night it might be interesting to dig through and figure >out what would be a good place for a beginner to get started, or whether >there’s some opportunity for cleanup. > >TL:DR - we have almost 1500 open bugs, most of which are ancient history. > >Pretty graphs! - http://httpd.rcbowen.com/httpd-open-bugs.html > >I suspect that a *bunch* of them are no longer valid. (There are, for example, >3 open bugs against the Win32 MSI Installer) > >(We also have 92 open PRs on https://github.com/apache/httpd/pulls which is a >whole *other* can of worms.) > >— >Rich Bowen >[email protected] > > > >
Re: Open bugs report, May 1 2026
On Fri, May 01, 2026 at 08:36:42AM -0400, Rich Bowen wrote: > I was thinking last night it might be interesting to dig through and figure > out what would be a good place for a beginner to get started, or whether > there’s some opportunity for cleanup. > > TL:DR - we have almost 1500 open bugs, most of which are ancient history. > > Pretty graphs! - http://httpd.rcbowen.com/httpd-open-bugs.html > Nice work. Would be tempting to close out old reports to get rid of some of the noise. If not by date, then at least close anything on unsupported versions. > I suspect that a *bunch* of them are no longer valid. (There are, for > example, 3 open bugs against the Win32 MSI Installer) > I had a quick look at "Critical & Blocker Bugs" - there's a lot of NEW reports and perhaps some things that had better gone to users@httpd. vh Mads Toftum -- http://flickr.com/photos/q42/
Open bugs report, May 1 2026
I was thinking last night it might be interesting to dig through and figure out what would be a good place for a beginner to get started, or whether there’s some opportunity for cleanup. TL:DR - we have almost 1500 open bugs, most of which are ancient history. Pretty graphs! - http://httpd.rcbowen.com/httpd-open-bugs.html I suspect that a *bunch* of them are no longer valid. (There are, for example, 3 open bugs against the Win32 MSI Installer) (We also have 92 open PRs on https://github.com/apache/httpd/pulls which is a whole *other* can of worms.) — Rich Bowen [email protected]
