On Thu, Mar 6, 2008 at 12:02 PM, Henrik Sundberg <storangen_at_gmail.com>
> 2008/3/4, Thomas Hemmer <themmer_at_go-engineering.de>:
> > maybe I have not fully understood your requirements.
> > Sounds like if you were performing some kind of multi-stage release
> > process?
> > Provided this were your very use case, the solution could be to
> > introduce different tag directories "to be approved" and "approved".
> Thanks for your patience.
> We decided to test another, unorthodox method.
> When something is approved we add an -approved suffix.
> Ie: svn mv test.odf test-approved.odf
> I can easily prohibit modification to approved documents in the
> pre-commit. And an approved document will be seen as approved no
> matter how it is copied in the structure.
> And when updetes are needed we'll start with renaming the document again.
> Do you expect me to get in trouble due to this solution?
> Is this dangerous now, but will be safe in the 1.5 release (I've read
> about better rename handling)
You could just branch it: either create an /approved directory off the main
directory (or you could put in /branches/approved, or even
/tags/approved). 'branches' is probably not the best place, because, by
custom, those files are not considered 'fixed'.
You could then also filter on the path in hooks.
Or, you could attach your own property mycompany:status and set it to
'approved' when that's the case. This is easy to test for. You could even
set svn:needs-lock on those files so that they are not easily modified.
Received on 2008-03-07 01:19:26 CET