All, I have a version Paradox. I've searched the mailing lists and the general advice is to save or discard the version. Problem is I need the work that's gone on in there, but it's not yet ready for general consumption. Any other ideas? Phil phil.harris@zope.co.uk
Hi Phil... You could set up a separate Zope instance (with a copy of the database), commit the version in that instance, abort the version in the original instance. Then work on the copy and import it into the original when you're ready. Phil Harris wrote:
All,
I have a version Paradox.
I've searched the mailing lists and the general advice is to save or discard the version. Problem is I need the work that's gone on in there, but it's not yet ready for general consumption.
Any other ideas?
Phil phil.harris@zope.co.uk
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
-- Chris McDonough Zope Corporation http://www.zope.org http://www.zope.com "Killing hundreds of birds with thousands of stones"
Chris, Thanks, that's what I ended up doing. A question since you're a ZC employee. Do any of the developers at ZC use versions in any serious way? I've seen numerous posts now about versions being locked etc. The advice about saving/discarding is obviously not workable, since the whole idea is that it's a work in progress. Any comment? tia Phil ----- Original Message ----- From: "Chris McDonough" <chrism@digicool.com> To: "Phil Harris" <phil.harris@zope.co.uk> Cc: <zope@zope.org> Sent: Friday, August 03, 2001 1:40 PM Subject: Re: [Zope] VersionLockError
Hi Phil...
You could set up a separate Zope instance (with a copy of the database), commit the version in that instance, abort the version in the original instance. Then work on the copy and import it into the original when you're ready.
Phil Harris wrote:
All,
I have a version Paradox.
I've searched the mailing lists and the general advice is to save or
discard
the version. Problem is I need the work that's gone on in there, but it's not yet ready for general consumption.
Any other ideas?
Phil phil.harris@zope.co.uk
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
-- Chris McDonough Zope Corporation http://www.zope.org http://www.zope.com "Killing hundreds of birds with thousands of stones"
Phil Harris wrote:
Chris,
Thanks, that's what I ended up doing.
A question since you're a ZC employee.
Always a liability under questioning. ;-)
Do any of the developers at ZC use versions in any serious way? I've seen numerous posts now about versions being locked etc.
Well, versions are useful under certain circumstances, but I don't make much use of them personally. And most of our customers prefer the dev-stage-production model instead of versions for reasons like the one you've just experienced.
The advice about saving/discarding is obviously not workable, since the whole idea is that it's a work in progress.
I wouldn't personally depend on versions in any site that makes heavy use of incremental catalog indexing. Otherwise I might use them once in a while, but never as a sole staging tool.
----- Original Message ----- From: "Chris McDonough" <chrism@digicool.com> To: "Phil Harris" <phil.harris@zope.co.uk> Cc: <zope@zope.org> Sent: Friday, August 03, 2001 1:40 PM Subject: Re: [Zope] VersionLockError
Hi Phil...
You could set up a separate Zope instance (with a copy of the database), commit the version in that instance, abort the version in the original instance. Then work on the copy and import it into the original when you're ready.
Phil Harris wrote:
All,
I have a version Paradox.
I've searched the mailing lists and the general advice is to save or
discard
the version. Problem is I need the work that's gone on in there, but it's not yet ready for general consumption.
Any other ideas?
Phil phil.harris@zope.co.uk
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
-- Chris McDonough Zope Corporation http://www.zope.org http://www.zope.com "Killing hundreds of birds with thousands of stones"
-- Chris McDonough Zope Corporation http://www.zope.org http://www.zope.com "Killing hundreds of birds with thousands of stones"
Chris, I've always used the dev-stage-product metaphor, but needed to make a 'quickish' change, which eventually took a few days. I sort of guessed that ZC developers didn't make much use of them ;) OK, then versions are out. 8¬( Phil ----- Original Message ----- From: "Chris McDonough" <chrism@digicool.com> To: "Phil Harris" <phil.harris@zope.co.uk> Cc: <zope@zope.org> Sent: Friday, August 03, 2001 2:29 PM Subject: Re: [Zope] VersionLockError
Phil Harris wrote:
Chris,
Thanks, that's what I ended up doing.
A question since you're a ZC employee.
Always a liability under questioning. ;-)
Do any of the developers at ZC use versions in any serious way? I've seen numerous posts now about versions being locked etc.
Well, versions are useful under certain circumstances, but I don't make much use of them personally. And most of our customers prefer the dev-stage-production model instead of versions for reasons like the one you've just experienced.
The advice about saving/discarding is obviously not workable, since the whole idea is that it's a work in progress.
I wouldn't personally depend on versions in any site that makes heavy use of incremental catalog indexing. Otherwise I might use them once in a while, but never as a sole staging tool.
participants (2)
-
Chris McDonough -
Phil Harris