History for MakeZopeStable

??changed:
-
There have been reports of Zope instability lately and they are proving
exceedingly difficult to establish a pattern against.  In order to
help us establish a pattern, please include the following information
in your bugreport.

- Zope version (2.5, 2.4.4, etc).  Note that
  there are known stability issues with
  Zopes versioned 2.4.0 - 2.4.3 and you
  should definitely be using either 2.4.4
  or 2.5.0.  Note that Zope 2.3.3 is also
  quite stable.

- Python version (2.1.1, 2.1.2, etc.)
  Note that there are known stability issues
  with Pythons versioned 2.0, 2.1, and 2.1.1.
  You should be using Python 2.1.2.  Note
  that if you are willing to use Zope 2.3.3,
  that you may use Python 1.5.2, which is
  quite stable.

- Operating system (Linux, Windows 2k, etc).

- Your installed Zope Products (LocalFS,
  Transparent Folders, etc.)

- Your installed Zope database adapter(s)
  (MySQLDA, Pyscopg, etc.)

- The results of running Zope with the environment
  variable ZOPE_SECURITY_POLICY=PYTHON
  set in the shell from which Zope was started
  (as opposed to without).  If you can run
  Zope without crashes when this is set,
  this is a good data point for the Zope
  developers to know.

- The results of running Zope in
  single-threaded mode by using the -t1 value
  to the "start.py", "start-bat" or "z2.py"
  scripts when starting Zope.  Usually Zope
  runs multithreaded.  If your Zope
  runs OK in single-threaded mode but
  crashes frequently in multithreaded
  mode, that's a good data point for
  the Zope developers to know.

If you've got toubleshooting steps that you think
might help us pin the problem down, please send mail
to the Zope maillist and I'll revise this page with
those suggestions.