Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification.
The "ReleaseDeployment" page has been changed by sebbapache: https://wiki.apache.org/commons/ReleaseDeployment?action=diff&rev1=3&rev2=4 === Disadvantages === * once the RC completes, the tarballs have to be copied from Nexus to the release directory in SVN. - This process is quite awkward. + This process is quite awkward. + * Alternatively, the tarballs can be copied from the local repo (they appear to be staged here as part of the deploy); again this is awkward. * the tarballs should then be deleted from Nexus; this stage is error-prone as it's easy to delete the wrong files. + + === Improving the manual parts === + + Using Maven to create and deploy all the artifacts is quite straightforward; no manual intervention is required. + The tricky part of the process is tidying up the staging areas and copying the tarballs to the dev or release SVN trees. + + == Alternative deploy process == + + Maven deploy can easily create all the required files in a local directory; this is what the -Ptest-deploy profile does. + + So an alternate approach would be to create the Nexus and dist staging areas directly from the local directory. + This should allow the tarballs to be uploaded to the dist/dev area, and everything else would be uploaded to Nexus. + + Assuming ths can be automated, it would eliminate most of the error-prone stages. + The Nexus staging area would still need to be closed (or maybe that can be automated?) but there would be no need to tidy up Nexus. == Alternative tarball process == --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
