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

Re: How to handle document status?

From: Henrik Sundberg <storangen_at_gmail.com>
Date: Mon, 3 Mar 2008 16:48:08 +0100

2008/3/3, Thomas Hemmer <themmer_at_go-engineering.de>:
> > From: Henrik Sundberg [mailto:storangen_at_gmail.com]
> > 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?

> my first guess would be to treat your documents exactly the same way
> program sources are handled, i. e. the "approved" state would be
> reflected by pulling an "svn cp" of that very document from the trunk
> into some "tags" directory.
> All further work on the document would happen within the trunk, leaving
> the once approved versions untouched.

Thanks. I might need to do this but it is a little troublesome.
I have ~200 components each with 4-10 official documents. I intend to
let the documents live in the trunk in a directory parallel to the
code. I'd like it to be possible to review and approve individual
documents and then when everything is ok, make a component release
(tag) of the total. If the documents are tagged separately, I'd have
problem to see their state in the component release.

Does it make sense? Can this be handled in a nice way?


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 17:09:34 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.