The nightmare scenario is when you try to support HTTP/3 when you can’t even support an HTML form parser.
Have an appropriate amount of fun. Popcorn is popping. Joe Schaefer, Ph.D. <https://sunstarsys.com/orion/features> Orion - The Enterprise Jamstack Wiki <https://sunstarsys.com/orion/features> <j...@sunstarsys.com> 954.253.3732 <//954.253.3732> On Thu, Feb 15, 2024 at 7:36 PM Joe Schaefer <j...@sunstarsys.com> wrote: > The reason the QA around httpd is so lousy lately is because none of you > actually dogfood the software professionally, because no Fortune 500 > employer would be caught dead running httpd over nginx in the cloud. > > That historically lackadaisical approach to CI has no business persisting > now that you are on GitHub. > > And yet it persists. > > It also is why you guinea pig your user base instead of respecting them, > because you aren’t a part of that community any more. > > And it shows with each new dud delivered to the apreq user base over the > past decade. > > So let’s end this fiasco ASAP. > > Joe Schaefer, Ph.D. > <https://sunstarsys.com/orion/features> > Orion - The Enterprise Jamstack Wiki > <https://sunstarsys.com/orion/features> > <j...@sunstarsys.com> > 954.253.3732 <//954.253.3732> > > > > > On Thu, Feb 15, 2024 at 7:08 PM Joe Schaefer <j...@sunstarsys.com> wrote: > >> Keep your tone policing off list wise guy. If you have something of >> substance to offer to your colleagues other than defensive posturing, let’s >> have it. >> >> Like all these vacuous bug reports missing from the issue tracker about >> apreq, that you rumor mongers like to scare people with. >> >> Joe Schaefer, Ph.D. >> <https://sunstarsys.com/orion/features> >> Orion - The Enterprise Jamstack Wiki >> <https://sunstarsys.com/orion/features> >> <j...@sunstarsys.com> >> 954.253.3732 <//954.253.3732> >> >> >> >> >> On Thu, Feb 15, 2024 at 7:03 PM Frank Gingras <thu...@apache.org> wrote: >> >>> >>> >>> On Thu, Feb 15, 2024 at 5:47 PM Joe Schaefer <j...@sunstarsys.com> wrote: >>> >>>> Nobody gives a flying f what you released from trunk. I personally will >>>> be dead and buried before you release httpd 3.0. So like you I don’t give >>>> a damned what you do with it. >>>> >>>> I just want the warfare against existing libapreq2 users to cease and >>>> desist. >>>> >>>> If there are known vulnerabilities in the existing codebase, you have a >>>> professional obligation to report them to the security team, who have >>>> assured me they will send them my way for proper handling by a competent >>>> engineer. >>>> >>>> None have been forthcoming, so that’s reason to release 2.18 as-is and >>>> mothball the subproject so we need not deal with each other again over it. >>>> >>>> Thanks >>>> >>>> Joe Schaefer, Ph.D. >>>> <https://sunstarsys.com/orion/features> >>>> Orion - The Enterprise Jamstack Wiki >>>> <https://sunstarsys.com/orion/features> >>>> <j...@sunstarsys.com> >>>> 954.253.3732 <//954.253.3732> >>>> >>>> >>>> >>>> >>>> On Thu, Feb 15, 2024 at 5:17 PM Eric Covener <cove...@gmail.com> wrote: >>>> >>>>> On Wed, Feb 14, 2024 at 11:57 PM Joe Schaefer <j...@sunstarsys.com> >>>>> wrote: >>>>> >>>>>> Twenty years in core, with one bug to fix. >>>>>> And you couldn’t even manage without three different botched releases. >>>>>> >>>>> >>>>> I think you are mixing up apreq and httpd releases here. >>>>> AIUI the apreq stuff in the core of httpd-trunk has only ever been in >>>>> one alpha release, and predates the regression. >>>>> >>>>> I'll keep any advice about an apreq release to myself, good luck and >>>>> please be mindful of the CoC >>>>> https://www.apache.org/foundation/policies/conduct >>>>> >>>>> >>> Respectfully, the tone of that response was unwarranted. There are >>> better ways to express your opinion that don't require attacks, and >>> cynicism. >>> >>
