On 26/11/2012 17:23, sebb wrote: > On 26 November 2012 17:01, Ralph Goers <ralph.go...@dslextreme.com> wrote: >> Actually, if you use the Release plugin the artifacts will be uploaded to >> the staging repository. At least that is what VFS does. They can be voted >> on there and then checked into SVN. You can easily verify they didn't >> change because the MD5s go along with them. > > But do the MD5s get automatically added to the release vote? > And how can one prove later that the MD5s in the VOTE thread are the > same as the ones in the staging repo? > > AFAICT that is no different from uploading to anywhere else, unless I > misunderstand what the release staging repository is. > > The point is that uploading to SVN and voting on the URL+revision > automatically provides traceability. > Whereas AFAICT the other methods don't, at least not without > additional work by the RM and all reviewers.
That may be the case (I haven't thought through the logic) but it is not the primary driver. The primary driver is removing the need to hand out a shell account on people.a.o to every committer. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
