To: ietf-dav-versioning@w3.org From: "Tim Ellison/OTT/OTI" <Tim_Ellison@oti.com> Message-ID: <OFD1E8751B.D1AE5149-ON852568CF.0007DA8C@ott.oti.com> Date: Thu, 27 Apr 2000 22:48:33 -0400 Subject: Checkin without becoming default revision 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