On 6-Mar-08, at 7:18 PM, Kevin Grover wrote:
> On Thu, Mar 6, 2008 at 12:02 PM, Henrik Sundberg
> <storangen_at_gmail.com> wrote:
> 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
> 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
> 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 ... You could even set svn:needs-lock on those
> files so that they are not easily modified.
Or mark ready only with path based access control.
> - Kevin
Received on 2008-03-07 06:28:43 CET