subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Sperling <s...@apache.org>
Subject Re: preventing accidental commit
Date Thu, 06 Jun 2013 19:12:36 GMT
On Thu, Jun 06, 2013 at 02:46:16PM -0400, Marshall Schor wrote:
>   a) checkout the part of the update site from the ...dist/release... spot;
>   b) update that, changing some files, adding others
>   c) put it somewhere for a vote, and after the vote passes,
>   d) commit the changes to the ...dist/release... spot

When you say "accidental commit", do you mean the release manager
is running 'svn commit' on a working copy from dist.a.o instead
of an unrelated working copy the commit was intended to be made
from, not realising the mistake until the commit has been made?

Or do you mean the release manager intentionally publishing the
release, not realising that votes are outstanding? In which case
I don't think there is a good technical solution to the problem.
Perhaps the release manager needs a break :)

In the first case:
Why don't you commit to and vote in dev/release, and when all votes
have passed, move the files to dist/release using svnmucc?
This is what we do in Subversion itself. See this script:
https://svn.apache.org/repos/asf/subversion/trunk/tools/dist/release.py
This approach makes it very unlikely that release artifacts
end up in the dist/release directory by accident.

Mime
View raw message