OK... last email on this topic.
I feel like I'm getting replies like I'm from another planet for asking prudent questions. If others want to keep their heads in the sand and get a huge surprise someday when a Perl update or a new version of Apache they just installed breaks mod_perl or there's a vulnerability that requires a fix and there's no one to fix... go ahead and roll  your dice... it's your party.

If you care at all about your software environment you should want to have an understanding of when you need  to look for a replacement and when a product  hits EOL. No, I don't want to look  for a replacement, but I do want to have an understanding of when to recognize when that is going to be a necessity given a software package's managed lifecycle. Perhaps others here are still looking for devices to play their 1970s 8-track tapes?

For anyone who actually does care given Adam's direction to the attic description at https://attic.apache.org/. If mod_perl hits The Apache Attic, I consider that fair warning. I don't think that 100% indicates an absolute final nail, but reasonable fair warning. I appreciate the responses of those that have lead me to that information.

Jim

On 3/18/2021 2:14 PM, Michel Jansen wrote:
Hi there,

If it broken it doesnt have to be fixed. Our purchase system is running almost 
20 years on modperl and there is no reason for is to stop this. We are very 
happy with it. How about that?

Michel Jansen

Op 18 mrt. 2021 om 17:48 heeft adam.pr...@utoronto.ca het volgende geschreven:

If you go back to Sander's original email, he outlines what will happen if we 
can't staff the PMC sufficiently to meet Apache's guidelines. The project woudl 
go to the attic[1].  There are lots of projects in the Attic. Some of them have 
been forked and continue to have development done on them. At any rate, there 
will be some notice, though probably not years of notice, and the source code 
absolutely will not 'suddenly disappear'. I'd suggest following the link below 
and reading about what the attic is, and what it would mean to get more context 
if you're interested in more detail.

Adam

[1] http://attic.apache.org/




Quoting Jim Albert <j...@netrition.com>:

When mod_perl does come to an end what would an End of Life look like?
I'm told mod_perl is an Apache Software Foundation project. Do Apache
Software Foundation projects have a structured life cycle or do some
just suddenly disappear with no warning given various situations that
result in the need for EOL?

Jim





Reply via email to