Re: stale RELEASE-NOTES commentary

2006-08-28 Thread Jason Brittain
On 8/23/06, William A. Rowe, Jr. <[EMAIL PROTECTED]> wrote: Yoav Shapira wrote: > Hi, > It's not only in the 4.1.31 release, it's even in the latest stable > 5.5.17. Let's change it in the next releases of 4.x and 5.x, starting > with 5.5.18 which should happen any day now. > > I think the advi

Re: stale RELEASE-NOTES commentary

2006-08-23 Thread Yoav Shapira
Hi, It's one reason we moved Announcement (httpd's short summary, similar to the tomcat RELEASE-NOTES) out of the project tree and tarball, and host those directly in /dist/httpd/ - they can be fixed/amended after the release without rerolling. I don't mind doing the same with Tomcat. We can

Re: stale RELEASE-NOTES commentary

2006-08-23 Thread William A. Rowe, Jr.
Yoav Shapira wrote: > Hi, > It's not only in the 4.1.31 release, it's even in the latest stable > 5.5.17. Let's change it in the next releases of 4.x and 5.x, starting > with 5.5.18 which should happen any day now. > > I think the advice was decent (and based on empirical evidence IIRC) > when or

Re: stale RELEASE-NOTES commentary

2006-08-23 Thread Yoav Shapira
Hi, It's not only in the 4.1.31 release, it's even in the latest stable 5.5.17. Let's change it in the next releases of 4.x and 5.x, starting with 5.5.18 which should happen any day now. I think the advice was decent (and based on empirical evidence IIRC) when originally issued, but that was mor

stale RELEASE-NOTES commentary

2006-08-23 Thread William A. Rowe, Jr.
...at least in 4.1.31... GLIBC 2.2 / Linux 2.4 users should also define an environment variable: export LD_ASSUME_KERNEL=2.2.5 Additionally, Redhat 9.0 users should use the same setting, to avoid stability problems. This is really, really horrific advice. A comment to for the user to fo