On Sun, Sep 25, 2016 at 09:25:16AM +1000, Gavin McDonald wrote: > > > > -----Original Message----- > > From: Ariel Constenla-Haile [mailto:arie...@apache.org] > > Sent: Sunday, September 25, 2016 9:01 AM > > To: dev@openoffice.apache.org > > Subject: [4.1.3 release] Procedure for uploading binaries > > > > Hi there, > > > > IIRC we used to upload the packages to our home directory at > > people.apache.org, once there I don't recall what the RM did until the > > packages ended on the subversion dist repo. > > > > Where should we upload the binaries now? > > The normal place is > > https://dist.apache.org/repos/dist/dev/openoffice/ > > From there the RM can just 'svn mv' them from 'dev' to 'release'
OK. So I started playing (do not get nervous, just with 4 files). This is my experiment: "svn mv" needs a working copy, so you need to checkout the repo, but there is no need to checkout the whole repo. Using http://svnbook.red-bean.com/en/1.7/svn.advanced.sparsedirs.html you can do the following: svn co --depth immediates https://dist.apache.org/repos/dist cd dist/ svn up --set-depth immediates dev svn up --set-depth immediates dev/openoffice svn up --set-depth immediates release svn up --set-depth immediates release/openoffice If different committers are going to upload different binaries, it seems better to use svn import instead of checking out and then committing; for example: svn import \ -m "Prepare 4.1.3 release" \ --username arielch \ Apache_OpenOffice_4.1.3_MacOS_x86-64_install_ast.dmg.asc \ https://dist.apache.org/repos/dist/dev/openoffice/4.1.3/binaries/ast/Apache_OpenOffice_4.1.3_MacOS_x86-64_install_ast.dmg.asc (right now I checked these 4 files under dist/dev/openoffice/4.1.2 in order to test svn mv 4.1.2 4.1.3 with my previous sparse-dirs checkout). If someone knows a better way of doing this, please share it :) Regards -- Ariel Constenla-Haile La Plata, Argentina
signature.asc
Description: Digital signature
