Having just recently upgraded the site to Apache 2.2.x and mod_perl 2, it made me want to kick things, hard, when paulej72 noticed this little gem earlier this morning in mod_perl 2.0.9's changelog:
Add support for Apache httpd-2.4.x. [Torsten Foertsch, Jan Kaluza, Steve Hay, Gozer]
Awesome work, guys, but couldn't you have done this a month ago? You know, before NCommander and the rest of us put all that work into getting the site running on 2.2.x?
(Score: 2) by bootsy on Thursday June 25 2015, @08:34AM
This is too bleeding edge. Let others upgrade and iron out any bugs before you take a new verison of mod_perl. It's never good practice to jump straight to a new version of a library unless there is a critical bug fix or security patch. Take your time and let it bed in. The work to make the site run on 2.2 will have made the next move to 2.4 easier when you do it.
(Score: 2) by NCommander on Thursday June 25 2015, @11:39PM
I'm moving the dev site to 2.4 as we speak right now. If production will follow with the next upgrade cycle is unclear, but I'm a strong believer of upgrade often and frequently, and deal with the breakage as it comes, else you get stuck with loads of old crap, and an unmaintable install.
Still always moving
(Score: 2) by bootsy on Friday June 26 2015, @01:11PM
A fair point. You can certainly be too cautious and bit rot is pain to fix once it has set in. I suppose it depends on the the effect of an outage. If Soylent is out for a day I wouldn't have a problem with that but other systems I have worked on cannot have downtime of more than 5 minutes so it pays to be a bit more cautious in those situations.
Thanks for all your efforts