[ZCM] [ZC] 1980/ 3 Comment "Bad test.py in 2.9b1 release"

[Collector: Zope Bugs, Features, and Patches ...]

Issue #1980 Update (Comment) "Bad test.py in 2.9b1 release"
 Status Resolved, Zope/bug critical
To followup, visit:
  http://www.zope.org/Collectors/Zope/1980

==============================================================
= Comment - Entry #3 by philikon on Dec 21, 2005 2:33 am

Instead of copying the test.py to releases/Zope2 and thus creating copies that can easily get out of sync, one could also simply delete releases/Zope2/test.py and put an entry in releases/Zope2/PACKAGE.cfg to refer to the root test.py:

  <load>
    ...
    test.py     svn://svn.zope.org/repos/main/Zope/tags/*/test.py
  </load>

Then the tarball's test.py will actually always be the root test.py from the checkout. Perhaps that isn't what we want, though...
________________________________________
= Resolve - Entry #2 by ajung on Dec 21, 2005 1:49 am

 Status: Pending => Resolved

Fixed (Trunk/2.9 branch)
________________________________________
= Request - Entry #1 by jim on Dec 20, 2005 3:05 pm

The test.py script in the root of the 2.9b1 release is different from the test.py in the root of a branch (or trunk) checkout.
==============================================================