Hey there, Chris; Fair question - and I don't think I have a handy link describing the flow of patch -> trunk -> STATUS backport proposal -> branch commit -> release
Generally speaking, the code goes into trunk and is proposed for backport into a stable branch via the STATUS file (at the root of the branch - ex http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/STATUS?view=markup). A lot of times, patches are proposed for discussion/refined and tweaked/etc before being committed in trunk, which seems to fit the conversation in your reference BZ item. From there, we need three committer +1s to backport. Once all three are in place, the proposer (or release manager) commits the change to the branch. So, for this one, I think we're not quite ready to incorporate. P.S. I hope all is well - long time no chat! -- Daniel Ruggeri On 7/23/2020 1:33 PM, Christopher Schultz wrote: > Daniel, > > On 7/22/20 19:32, Daniel Ruggeri wrote: > > Hi, all; It's been a while since we've rolled a release and gotten > > fixes/etc in our community's hands. Apologies for not suggesting > > this sooner. How about a T&R Friday? That will let vote run through > > the weekend. > > If I clean-up my patch for > https://bz.apache.org/bugzilla/show_bug.cgi?id=64338 is there a chance > it could make it into this release? > > I'm super-ignorant about the httpd release process so I apologize if > that's a ridiculous question. > > -chris
