Jim Gallacher wrote:
Jorey Bump wrote:
IOW, could you guys list the OS on which you run, and not merely test,
By you guys I assume you mean the above 4 people?
Yeah, youse 4 guys. :)
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.
No, I'm just interested in the core group. Everyone else gets an
opportunity to list platforms when testing new releases, in pass/fail
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.
A small checklist might be useful, such as Windows/Mac/Linux/UNIX/BSD.
This has been handled fairly well in the past, but that might be due to
luck. I'm concerned that some last minute fix will be checked into a
stable release candidate without sufficient cross-platform testing. I
mainly use Python in UNIX-like environments, and I forget how popular it
is on Windows (the same goes for Apache).
Ideally, it would be nice to solicit feedback from package maintainers.
I use Slackware, which doesn't include Apache 2 or mod_python, so I can
tell immediately how it's going to perform in my production systems.
Users of stock Red Hat, Debian, SUSE, Mandriva, FreeBSD, Mac, etc. can't
be so sure. The package maintainers are in the best position to flag
potential problems. But this is an issue shared by many open source
projects, and we'll need to be satisfied with the participation we get,
and try our best to create a stable release.