[Zope-Coders] ZopeVersionControl

[Casey Duncan]

An easy solution would be to do a dated checkout (cvs up -D1/15/03) from=20
before Shane made the change. Which I think happened sometime in January.

That's one problem with using "unreleased" software, there are no release=
=20
versions to rely upon.=20

So really its just a matter of applying proper version control to your ve=
rsion=20
control ;^)

-Casey

On Thursday 20 February 2003 02:51 pm, Magnus Heino wrote:
> Hi.
>=20
> I'm trying to get PloneStaging to work .=20
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/collective/PloneStaging/
>=20
> Before, when we updated the stages with the 'plone' site object, all it=
s=20
> contents were updated.
>=20
> st.updateStages(plone, 'dev', ['review', 'prod'])
>=20
> Then Shane made some changes:
>=20
> "
> Containers are now versioned independently of their ObjectManagerish=20
contents.
> This means it is now possible to put versioned objects in a hierarchy.
> The current implementation ignores the fact that the user may actually =
want
> to version the item names and item history IDs. Instead, it only
> versions the aspects of the container that are not items.
> "
>=20
> Now just the the plone object and none of its contents are updated.
>=20
> ...help! :-)
>=20
> --=20
>=20
>   /Magnus
>=20
> _______________________________________________
> Zope-Coders mailing list
> Zope-Coders@zope.org
> http://mail.zope.org/mailman/listinfo/zope-coders
>=20