Next message: Geoffrey M. Clemm: "Re: DAV:repository-report"
Date: Fri, 28 Apr 2000 16:50:22 -0400 (EDT)
Message-Id: <200004282050.QAA06866@tantalum.atria.com>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
Subject: Re: Checkin without becoming default revision
If you want your checkin to not be visible to others, wouldn't you
be working in a different workspace?
On a server that does not support workspaces, you can achieve a
similar effect by naming some label as your Target-Selector for the
CHECKIN. This would move the label to the new revision, but leave the
default target alone. I think you'd probably want to track all your
new revisions in this way anyway.
Cheers,
Geoff
From: "Tim Ellison/OTT/OTI" <Tim_Ellison@oti.com>
Date: Thu, 27 Apr 2000 22:48:33 -0400
7.3 Checkin
It sure would be helpful if there was some way to indicate that the
newly
checked in revision should NOT become the default revision. Maybe part
of
the check-in policy?
<geoff/>
What use case would motivate this?
Those of us who operate under the model of distinct 'create a revision' &
'release' steps.
As it stands, I cannot create a new revision without it becoming a target
of the workspace.
If I had the opportunity to do auto-version (i.e. atomic
checkout-put-checkin) and the opportunity to NOT 'release' then I could
create entries in the revision history without affecting the view of the
world as seen by friends in my workspace.
Tim