[Zope] Public CVS checkout hasn't updated files in several da ys

[Ken Manheimer]

Jim Cain wrote:

> I've been maintaining my copy of Zope using public CVS. When I ran
this
> command:
> 
> cvs -z7 -q up -P -d
> 
> on August 10 and again on August 12, there were no changes. I think
> the last time I received updates was August 5. Surely there have been
> changes since then.

Jim, the changes are being propagated - but not to the old 'Zope' CVS
module, which has been frozen with the release of Zope2.  All checkins
(since july 22) have been going to a new module, named of course
'Zope2'.  From what i can tell, the Zope2 public repository is up to
date, so i suspect that you're still tracking the old Zope module.  Let
me know if i'm that's not the case, and i'll see what i can glean.

Below is my announcement about the change - i tried to hit everywhere i
could, but it can't hurt to repeat it...

Ken Manheimer
klm@digicool.com

Date: Thu, 22 Jul 1999 14:02:07 -0400 (EDT)
To: zope-checkins@zope.org, digicool-cvs@zope.org,
    zope-announce@zope.org, zope-dev@zope.org
Subject: CVS checkin notifications reinstated

We've reinstated updates to the public CVS repository (before the
Zope2 release - looks like that may be a day or two) - *with an
important change*:

  Ongoing development is being applied to a new directory, Zope2.

The old Zope module, on which the prior public checkouts were based,
will *not* be revised, so:

 - If you want to get the new version you'll have to do a new checkout
   of the Zope2 module.

This actually simplifies a bunch of things from our internal
perspective, and a few things from the external perspective, and has
the benefit of providing a checkpoint of the last Zope1 release.  But
it is a change, and we want to be sure that you track it.

Questions?  Comments?  Lemme know.

Ken Manheimer
klm@digicool.com