Jorey Bump wrote:
Mike Looijmans wrote:

Seriously, I think Grisha's way is right - the three musketeers should decide based on the feedback they get. There's no substitute for running on other people's machines...

2006/1/19, Gregory (Grisha) Trubetskoy <[EMAIL PROTECTED]>:

Thanks Roy. Very timely, since 3.2.6 is (so far) going to be a
final/stable release.

I propose that for starters those people are:

me (I'm also in the Apache HTTP Server PMC)
Jim Gallacher
Nicolas Lehuen
Graham Dumpleton

+1 here, but since the build process and typical MPM differs among platforms, could we see a list that this group represents? I'm most interested in default nonvirtualized environments used in production or for principal development. This information will be useful when reviewing release candidates, to make sure we haven't overlooked any key platforms.

IOW, could you guys list the OS on which you run, and not merely test, mod_python?

By you guys I assume you mean the above 4 people? I'm not sure how relevant this is since looking at that information from just 4 people is too small a sample to determine if the code is ready for release. Hopefully Roy will clarify, but I see the role of the core group more as meta voters, where we vote on the voting. So in theory, the core group could vote for a release even if none of them has ever actually compiled or used mod_python.

On the other hand, you may mean *all* the people on python-dev who test a release candidate should list their production platform. This would be useful to the core group as another data point in deciding on casting a binding vote to proceed to release.

That being said, I do eat my own dogfood, so here is my setup:

Development and testing (mod_python and my own stuff):
  Linux Debian unstable, Apache 2.0.55 mpm-prefork, python 2.3.5

Testing (mod_python only, using qemu)
  Linux Debian stable (sarge), Apache 2.0.54 mpm-prefork, python 2.3.4
  Linux Debian stable (sarge), Apache 2.0.54 mpm-worker, python 2.3.4

  Linux Debian stable (sarge), Apache 2.0.54 mpm-prefork, python 2.3.4

Similar to Nicolas, I need mpm-prefork as there are some php applications on the production server.

Your point on making sure we don't overlook any key platforms in our testing is a good one. Should we (python-dev people) put together a list of key platforms as a future guide? It's likely a good idea, even at the risk of a flamewar. ;) I thought I'd put together a summary of 3.2.6 test results in the next few days anyway, which should be a good starting point for the key list.


Reply via email to