I'm planning to merge the new-install-branch efforts recently discussed on this list into the Zope 2 trunk tomorrow. There will be things to do after the merge, but the basic functionality will be more easily testable and easier to contribute to. There's a bit more testing to be done before the merge can occur; I'll be doing that tonight and tomorrow morning. I'll send a note to the zope-coders list before I actually start the merge. For a description of the changes (and the ensuing discussion), refer to this thread: http://mail.zope.org/pipermail/zope-dev/2003-March/018999.html Perhaps the most immediate change is that the Windows tests may become completely wedged, since we've not had time to do any testing on Windows yet. If anyone has time to do so (and a suitable platform), please don't hesitate to send bug reports before the merge! Checkout instructions are included in the message referenced above. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> PythonLabs at Zope Corporation
Fred L. Drake, Jr. wrote:
I'm planning to merge the new-install-branch efforts recently discussed on this list into the Zope 2 trunk tomorrow. There will be things to do after the merge, but the basic functionality will be more easily testable and easier to contribute to.
Will I have to change the way Zope is built and/or the etsts are run? If so, where could I find otu what they now need to look like? cheers, Chris
Chris Withers writes:
Will I have to change the way Zope is built and/or the etsts are run?
Yes.
If so, where could I find otu what they now need to look like?
There is a <scenario> for Linux in the newinstallbranch.xml in Packages/TestScripts; I'll test it again before the merge takes place. I don't know about the Windows <scenario>, but it's probably OK for now. It may need to change in the future (I'll try to help as much as possible; Tim just tried the new-install-branch tests on Windows and we found one buglet there). I won't be in front of a Windows box myself until tonight. -Fred -- Fred L. Drake, Jr. <fred at zope.com> PythonLabs at Zope Corporation
Fred L. Drake, Jr. wrote:
Chris Withers writes:
Will I have to change the way Zope is built and/or the etsts are run?
Yes.
If so, where could I find otu what they now need to look like?
There is a <scenario> for Linux in the newinstallbranch.xml in Packages/TestScripts; I'll test it again before the merge takes place.
...it doesn't appear to work on Windows, since VC++ doesn't provide 'make'.
I don't know about the Windows <scenario>, but it's probably OK for now. It may need to change in the future (I'll try to help as much as possible; Tim just tried the new-install-branch tests on Windows and we found one buglet there). I won't be in front of a Windows box myself until tonight.
Well, I tried subbing 'nmake' for 'make' in the Linux scenario, and got this: """ cvs export: Updating Zope/var U Zope/var/.cvsignore U Zope/var/Data.fs.in Running: c:\python22\python -c "import sys; print sys.version" Running: configure Running: nmake build 'configure' is not recognized as an internal or external command, operable program or batch file. Microsoft (R) Program Maintenance Utility Version 6.00.8168.0 Copyright (C) Microsoft Corp 1988-1998. All rights reserved. NMAKE : fatal error U1073: don't know how to make 'build' Stop. """ I'm guessing that the real culprit here is 'configure' not working. How did Tim get it to work? cheers, Chris PS: For safety's sake, I'll disable the Zope HEAD tests tonight, pendign this isssue being resolved...
[Fred L. Drake, Jr.]
I'm planning to merge the new-install-branch efforts recently discussed on this list into the Zope 2 trunk tomorrow.
...
http://mail.zope.org/pipermail/zope-dev/2003-March/018999.html
Perhaps the most immediate change is that the Windows tests may become completely wedged, since we've not had time to do any testing on Windows yet. If anyone has time to do so (and a suitable platform), please don't hesitate to send bug reports before the merge!
I'm running the Windows tests on this branch (Python 2.2.2 + new-install-branch + Win2000), and it's going well. We found one Windows-specific problem, and Fred checked in a fix for that. Two ZEO tests are failing, but that appears to be a cross-platform problem introduced yesterday and not unique to the branch.
I wrote:
I'll send a note to the zope-coders list before I actually start the merge. For a description of the changes (and the ensuing discussion), refer to this thread:
http://mail.zope.org/pipermail/zope-dev/2003-March/018999.html
The unit tests work on Windows for the branch at this point, so I don't expect any real surprises there just yet. I'm starting the mechanics of the merge into the trunk now; I'll send another email when the merge is complete. Anyone running an automated test of the Zope 2 trunk should review this message to determine what impact this will have on the test process: http://mail.zope.org/pipermail/zope-coders/2003-March/003450.html -Fred -- Fred L. Drake, Jr. <fred at zope.com> PythonLabs at Zope Corporation
Fred L. Drake, Jr. writes:
I'm starting the mechanics of the merge into the trunk now; I'll send another email when the merge is complete.
I'm done. The new-install-branch is now dead. -Fred -- Fred L. Drake, Jr. <fred at zope.com> PythonLabs at Zope Corporation
participants (4)
-
Chris Withers -
Fred L. Drake, Jr. -
Fred L. Drake, Jr. -
Tim Peters