Petr Sumbera wrote:
> Garrett D'Amore wrote:
>>>> Indeed, this begs a question: wouldn't it simply be easier to
>>>> remove mod_jserv with the removal of Apache 1.3.x. I'm assuming
>>>> that if we've not already EOF'd Apache 1.3 in favor of 2.0, that we
>>>> will do so at some point in the future?
>>>
>>> Simple removal of JServ seemed to be easier, faster and less
>>> controversial. So that question of EOF Apache 1.3 is beyond this
>>> case. But yes there are from time to time some discussions which
>>> might lead to it.
>>
>> I'm not sure that its much less controversial for Solaris
>> Nevada/Next. It seems like EOF of 1.3 is something that ought to
>> occur at about this time, and that the time is ripe for it. (Apache
>> has both Apache 2.0 and Apache 2.2 as release trains available at
>> this time -- so 1.3 is actually two releases behind schedule --
>> continuing to ship it makes about as much sense as continuing to ship
>> Gnome 1.x -- actually less since ISV software generally doesn't
>> dynamically link against the Apache server.)
>>
>> I think personally, I'd rather go through just a single EOF process
>> than go through two of them.
>
> There used to be some vendor specific Apache 1.3 modules (e.g. from
> Oracle, IBM). I'm not sure whether all these have their equivalent for
> Apache 2.2 now. So with all respect to Gnome I wouldn't compare it here.
>
> This case is here so we can remove Apache JServ as soon as possible
> since there is clear migration path. While Apache 1.3 removal would
> require usual time off.
Gosh, I'd hope that vendors would have made version 2.x modules
available. Apache 2.0 was released quite some time ago... back in
2002. This is no longer cutting edge technology.
(Apache 1.3 was released back in 1998.)
That said, I'm happy to +1 this case if an EOF of Apache 1.3 is not
deemed practical at this time. I do think the project team should at
least undertake the effort to Obsolete Apache 1.3 as soon as possible
though, so we can start the timer for its actual removal.
(Actually, getting a notification in the the next S10 update would allow
removal in the next full release, assuming you get buy in from the
various committees that would have to approve it. It seems like that
approval would be fairly straight-forward to get, unless there are known
consumers that we have to support and which can't migrate to Apache 2.0
or Apache 2.2.)
- Garrett
