Surly this is just a formality. If there have not been updates for two years they are pretty-much dead projects anyway. Conversely if you have been running on an old system for two years without problems then its likely to be pretty stable, so you can just stick with it on the understanding that there will be no fixes or enhancements.
And what does this mean exactly? Obviously, no new features for 1.3 and 2.0 - what about bugfixes? They say: "we'll be distributing security updates by other means" - what are these other means?
The main point is to reduce the overhead and burden of creating full releases. Releases take a large amount of community involvement and time, and are becoming impractical. The 1.3.x branch does not even build on many modern platforms - for example the configure script is incompatible with dash and there is a getline() function which conflicts with a glibc neologism.
The 1.3.x branch does not even build on many modern platforms - for example the configure script is incompatible with dash
You appear to have that ass-backwards, surely it is dash that is incompatible with the configure script?
and there is a getline() function which conflicts with a glibc neologism.
How did you manage to mispell "Posix 2008" as "a glibc neologism"? I've been running 1.3.42-dev since.41 was tagged, there were no build issues on my current systems 8? months ago and nothing here that'd take an
The difficult we do today; the impossible takes a little longer.
Surly this is just a formality (Score:3, Interesting)
Re: (Score:2)
Who you calling surly?
And what does this mean exactly? Obviously, no new features for 1.3 and 2.0 - what about bugfixes? They say: "we'll be distributing security updates by other means" - what are these other means?
Re:Surly this is just a formality (Score:5, Informative)
As per http://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x/README [apache.org] , the proposal (Full disclosure: I'm colm@apache.org - the proposer), was that we would start distributing security patches via;
http://www.apache.org/dist/httpd/patches/ [apache.org]
The main point is to reduce the overhead and burden of creating full releases. Releases take a large amount of community involvement and time, and are becoming impractical. The 1.3.x branch does not even build on many modern platforms - for example the configure script is incompatible with dash and there is a getline() function which conflicts with a glibc neologism.
Hope that helps.
Re: (Score:0)
You appear to have that ass-backwards, surely it is dash that is incompatible with the configure script?
How did you manage to mispell "Posix 2008" as "a glibc neologism"? I've been running 1.3.42-dev since .41 was tagged, there were no build issues on my current systems 8? months ago and nothing here that'd take an