FYI: I archived the github mod_h2 and mod_md repositories. - Stefan
> Am 05.06.2026 um 18:40 schrieb Stefan Eissing via dev <[email protected]>: > > > >> Am 05.06.2026 um 18:31 schrieb Joe Orton <[email protected]>: >> >> On Fri, Jun 05, 2026 at 02:48:14PM +0200, Stefan Eissing via dev wrote: >>> From 2.4.x STATUS: "I guess Stefan will take care." >>> >>> FYI: Stefan is totally under water and has been for months now, curl being >>> the first project to be hit by the LLM craziness. >>> >>> I have in the past silently synched changes between the repositories for >>> people who drop things into trunk and never proposing backports or >>> compatibility with 2.4.x. That service I can no longer do. If you change >>> anything in mod_http2 or mod_md, it's now your task to do this. >>> >>> For me "trunk" is a graveyard and an obstacle, a necessary evil for >>> maintaining 2.4.x. This might sound harsh to some, but the last decade has >>> only confirmed this as a reality (I expressed this in the past). I can only >>> regard the recent uptick in trunk changes as going in a direction I am no >>> longer able (as in having the mental strength and time) to follow. >>> >>> If there is something puzzling in the modules' code, please contact me >>> and I am happy to help. But I have to step back from the daily >>> security list madness and the tidy up work. At some point, it will >>> probably be best to set the github modules repository to archive mode. >> >> Thanks Stefan, and totally understand. >> >> We discussed in the PR and on slack a bit. If we move to r/w git, we >> could import mod_h2 via a git submodule which would force people to >> submit/propose changes there (or at least prevent change in svn trunk >> directly). That would avoid the overhead of maintaining the code in two >> places. > > I do not recommend this, as you can see from your PR #331 and the difficulty > of having code that works in trunk and 2.4.x. > > The problems are inherent in the way the project handles its branches. > > I am a bit foul-mouthed today (which gets the more attractive the more pieces > of LLM novellas one encounters), but "trunk" is and for the last decade has > been a kind of LALA-land, where on can commit well-intentioned changes > without ever having to maintain them in the real world. The maintainers of > 2.4.x have to carefully work around that, spending extra cycles to keep this > dreamland going. > > The branch policy made sense at then time when 2.4.x was exptected to be > short-lived and a 2.6 or whatever coming Real Soon Now. There is no evidence > that it will arrive. It is what it is. > >> In the meantime I got Claude to create >> https://svn.apache.org/repos/asf/httpd/dev-tools/trunk/github/mod_h2_sync_from_trunk.sh >> to help us create icing/mod_h2 MRs out of trunk changes> I encourage >> other httpd committers to use that or do it manualy, if you want to >> touch modules/http2. Will adapt for mod_md as well if I get a second >> next week. > > I do not want to put workload on the other people in the project. Atm, I > favour putting the github repositories into archive mode. Which is then also > clear to everyone visiting and avoids explaining this to people having issues > or PRs. > > Regards, > Stefan > >> >> Regards, Joe
