Sebb created WHIMSY-303:
---------------------------
Summary: Should Secretary Workbench check SVN revision before
commit?
Key: WHIMSY-303
URL: https://issues.apache.org/jira/browse/WHIMSY-303
Project: Whimsy
Issue Type: Improvement
Reporter: Sebb
The workbench does various checks of the SVN repos to ensure files don't exist
etc.
However it's possible that a repo could be changed between the check and the
commit.
This is particularly true in the workbench as there will be a delay between the
two while the proposed changes are checked by the user.
Where several separate items are updated as part of a single transaction, this
could result in inconsistent data.
It might be sensible to record the revisions (last-changed) used for the
checks, and double-check those before committing. This would reduce (but not
eliminate) the update window.
Where the files all reside in the same repo, it should be possible to use
svnmucc to batch the updates together. However in that case, it would be
necessary to use the repository revision, rather than the last-changed-revision.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)