On 22 March 2013 14:24, Gary Gregory <garydgreg...@gmail.com> wrote: > On Fri, Mar 22, 2013 at 10:20 AM, sebb <seb...@gmail.com> wrote: > >> On 22 March 2013 13:16, Stefan Bodewig <bode...@apache.org> wrote: >> > On 2013-03-22, sebb wrote: >> > >> >> On 19 March 2013 17:05, sebb <seb...@gmail.com> wrote: >> >>> Commons is currently still publishing mon-Maven releases from >> >>> people.a.o dist/commons. >> > >> >>> There is an outstanding JIRA issue for this to be changed to svnpubsub: >> > >> >>> https://issues.apache.org/jira/browse/INFRA-5929 >> > >> >>> Until this is implemented, it is vital that the dist SVN and people >> >>> directories are kept in sync at all times. >> > >> >> The JIRA has now been completed - it is no longer possible to write >> >> directly to dist/commons on people.a.o. >> > >> > I'm in the process of publishing a change to the "preparing a release" >> > doc where it talks about putting the KEYS file into that area. >> > >> > My current plan is to finally document the release process this weekend >> > and I'll cover the new publishing process via svn. >> >> Great! >> >> I don't know whether you want to mention the dist/dev tree - that can >> be used for staging releases instead of a user's home directory. >> The files can then be moved in SVN to the release tree if the vote >> succeeds or deleted otherwise. >> > > Hi, > > If you a svn move, that will delete the source, right? So do you mean a one > 'move' operation or a split 'copy' and 'delete'.
Which ever you prefer; I think SVN implements move as copy/delete anyway. In either case SVN history will show that the release tree files came from a specific revision of the dev tree - which is all that matters. Ideally the move/copy should be done as a single commit (easier to follow). However I think that can only be done with svnmucc. I don't think SVN can do a merge of the contents of a directory to an existing targe directory. > Gary > >> >> If the RC vote includes the revision number of the tree, then it gives >> traceability from the vote to the release directory. >> >> The Nexus URL already includes a sort of revision number (not unique >> over time) which will appear in the RC vote and the Nexus status >> change emails. >> This should be suffiicently unique to trace back from the repository, >> should it ever prove necessary. >> >> > Stefan >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> > For additional commands, e-mail: dev-h...@commons.apache.org >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > > > -- > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org > JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0 > Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
