quetz-mod_python-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Gallacher <...@jgassociates.ca>
Subject mod_python 3.3.0-dev-20061109 available for testing (release candidate)
Date Thu, 09 Nov 2006 14:00:57 GMT
The mod_python 3.3-0-dev-20061109 tarball is available for testing.

We are almost ready for a 3.3.0 release. It's been a while since we've 
had extensive testing of trunk and I think it would be wise to have a 
preliminary testing round. Unless there are huge problems we'll do an 
official beta next week. If it looks *really* good we might even jump 
right to the release.

At this point svn trunk should be considered frozen execpt to fix issues 
that testing exposes or minor documentation changes.

Here are the rules:

In order for a file to be officially announced, it has to be tested by
developers on the dev list. Anyone subscribed to this list can (and
should feel obligated to  :-)  ) test it, and provide feedback *to _this_
  list*! (Not the mod_python@modpython.org list, and preferably not me

The files are (temporarily) available here:


Please download it, then do the usual

$ ./configure --with-apxs=/wherever/it/is
$ make
$ (su)
# make install

Then (as non-root user!)

$ make check

Or for you Windows folks

$ cd test
$ python test.py

And see if any tests fail. If they pass, send a +1 to the list, if they
fail, send the details (the versions of OS, Apache, Apache-mpm, Python,
the test output, and suggestions, if any).

Please present your test results in the following format:
+1 OS version, Apache version (apache mpm), Python Version

For example:
+1 Linux Debian Sid, Apache 2.0.55 (mpm-worker), Python 2.3.5

Presenting your information in a consistent format will help in
tabulating the results. You can include additional information in each
section, just don't use extra commas. There is no need to include the
mod_python version in this string as that information is available in
the email subject. Who knows, one day I may actually write a script to
extract this information automatically.  :)

Thank you for your assistance,
Jim Gallacher

View raw message