Jim Gallacher wrote: > Jorey Bump wrote: >> +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. > > 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.
As a non-x86 user (amd64 here), I second the notion that we need some non-Linux non-x86 platform testing out there, if people were willing to commit to be available to build and test when that time comes around (I think it's been pretty good, about every 2 months it's been on average?). I know there are people on PPC OSX, FreeBSD, AIX, Tru64, Solaris, and I just think it's a good idea to have a general concensus that a build will work on at least some of these platforms that both apache and Python are also supported and has worked for in the past. I'm not sure which of these you can identify as "key," but I would say that *BSD, OSX and Solaris should top the list. I also suggest Linux x86_64 of some kind, since it's becoming more and more widely used; I know we've got 2 or 3 people that normally respond to release tests that do. Nick
