Gregory (Grisha) Trubetskoy wrote:
On Thu, 29 Dec 2005, Jim Gallacher wrote:
So are we happy with the state of svn trunk right now? If so I'll roll
the tarball for 3.2.6b.
Does anyone here have any opinion on whether this release should be
marked as "beta"?
I personally don't know enough to comment, so I'd release it as beta
just to be safe. But if anyone here thinks that that's a waste of our
collective "bandwidth" and we should just release it as a stable release
- let's hear it :-)
Grisha
I'm inclined to going right to a 3.2.6 release. It's not like the code
is completely untested - we've had 6 betas already with the first one
released in August. The difference between 3.2.5 and 3.2.6 is small,
with just a couple of fixes for segfaults that are were not new bugs in
3.2. The behaviour for handling iterables in publisher was also reverted
to the way it was done in 3.1.4.
Let's be bold and release it as 3.2.6 final, and then talk about ways to
speed up the release cycle for bug fixes and new versions.
Jim
For you reference:
http://issues.apache.org/jira/browse/MODPYTHON-96
Accessing req.boundary causes crash.
http://issues.apache.org/jira/browse/MODPYTHON-97
mod_python.publisher iterables and content_type broken
http://issues.apache.org/jira/browse/MODPYTHON-99
accessing some request or server object members causes a segfault
