On Aug 24, 2007, at 7:47 PM, Sander Temme wrote:
Ruediger Pluem wrote:
On 08/24/2007 02:54 PM, Jim Jagielski wrote:
To be honest, I can't see holding off the 1.3 release any longer
while we're waiting on APR as well as stuff is being added
to the 2.x trees... It's kind of embarrassing.
To be honest, I can't see holding off the 1.3 release any longer
while we're waiting on APR as well as stuff is being added
to the 2.x trees... It's kind of embarrassing.
So even though I have most of the files setup for triple
release, I think next week I'll just release 1.3 and we
can the
On 08/24/2007 02:54 PM, Jim Jagielski wrote:
To be honest, I can't see holding off the 1.3 release any longer
while we're waiting on APR as well as stuff is being added
to the 2.x trees... It's kind of embarrassing.
So even though I have most of the files setup for triple
release, I
Ruediger Pluem wrote:
On 08/24/2007 02:54 PM, Jim Jagielski wrote:
To be honest, I can't see holding off the 1.3 release any longer
while we're waiting on APR as well as stuff is being added
to the 2.x trees... It's kind of embarrassing.
+1.
As far as I understand this downgrade scenario
Sander Temme wrote:
We can even do the same for 2.0.x once we have our regression fixed, and
then make a splash for all three when 2.2.x is done.
2.0 and 2.2 both have piped log issues.
For 2.0 this is slightly more critical, we still invoke the log pipe app
directly, and then pid_kill the
