Below is a proposed policy on backward compatibility for Zope.
Zope Policy on Backward Compatibility
=
Backward compatibility needs to be a very high priority. Clean
software also needs to be a high priority. Unfortunately, these goals
are often at odds.
This sounds good. I would add perhaps the concept of a 'smoke test'
application for backwards compatibility testing.
For Zope 2, the smoke test might be Plone or another large app written
on top of it.
Maybe someone involved in Zope 2 release management would volunteer to
run the smoke test app
On Oct 27, 2004, at 15:49, Jim Fulton wrote:
Below is a proposed policy on backward compatibility for Zope.
Zope Policy on Backward Compatibility
=
snip
+1, even regardless of its actual content. Having a policy at all is a
lot better than the I gotta ask X
Chris McDonough wrote:
This sounds good. I would add perhaps the concept of a 'smoke test'
application for backwards compatibility testing.
For Zope 2, the smoke test might be Plone or another large app written
on top of it.
Maybe someone involved in Zope 2 release management would volunteer to
En/na Jim Fulton ha escrit:
Chris McDonough wrote:
This sounds good. I would add perhaps the concept of a 'smoke test'
application for backwards compatibility testing.
For Zope 2, the smoke test might be Plone or another large app written
on top of it.
Maybe someone involved in Zope 2 release
Maybe we should have a bw compat category in the collector(s) for this
to make it easy to find bw compat issues. It would make it easy to get
a list of showstopper issues around release time.
- C
On Wed, 2004-10-27 at 14:22 -0400, Jim Fulton wrote:
Andreas Jung wrote:
--On Mittwoch,
Chris McDonough wrote:
Maybe we should have a bw compat category in the collector(s) for this
to make it easy to find bw compat issues. It would make it easy to get
a list of showstopper issues around release time.
Great idea!
Jim
--
Jim Fulton mailto:[EMAIL PROTECTED] Python
