[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

How to handle document status?

From: Henrik Sundberg <storangen_at_gmail.com>
Date: Mon, 3 Mar 2008 13:21:50 +0100


In our current process documents are marked with their state, eg Draft
or Approved.

I think it is a bad idea to modify the documents at approval (the
approval should not change the thing it approves).

I was thinking of adding a property for this, eg ApprovedBy.

But. As soon as someone updates an approved document it should revert
to being a draft.
Forbidding modification of approved documents in the pre-commit hook
will only partly solve the problem, because it would force the updater
to remove the property for the approved version. I just want to remove
it for the new version.

Removing the property in the post-commit hook is tempting, but
considered not ok since it would make the committed version different
from the working copy.

Is there a better way to handle this?


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-03 13:22:24 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.