ctubbsii commented on code in PR #351: URL: https://github.com/apache/accumulo-website/pull/351#discussion_r1001000003
########## contributor/making-release.md: ########## @@ -20,7 +20,19 @@ Follow these steps to make a release of Apache Accumulo. There are number of things that are required before attempting to build a release. 1. Use gpg-agent, and be sure to increase the gpg-agent cache timeout (via .gnupg/gpg-agent.conf) to ensure that the agent doesn't require re-authentication mid-build, as it will cause things to fail. For example, you can add `default-cache-ttl 6000` to increase the timeout from the default of 10 minutes to over an hour. If you do not have a GPG key, reference the very thorough [ASF release signing documentation][1]. -2. Once you are able to sign a release, add your gpg key to the [KEYS file][keys-file] (instructions are at the top of the file). This will require updating the SVN repository (more below). +2. Once you are able to sign a release, add your gpg key to the [KEYS file][keys-file] (instructions are at the top of the file). This will require updating the SVN repository (more information below about the SVN repository). You can use something similar to the instructions below for updating the KEYS file: + ``` + # install git-svn + sudo yum install -y git-svn + # clone the SVN repo into the directory accumulo-dist-gitsvn + git svn clone https://dist.apache.org/repos/dist/release/accumulo accumulo-dist-gitsvn + cd accumulo-dist-gitsvn + # make changes to KEYS file, then commit the changes locally + git add KEYS + git commit + # push the changes to the remote SVN repo + git svn dcommit --username=<ASF_Username> + ``` Review Comment: I think mine is a simpler example, as a bare minimum. But, I don't want our doc to be bloated with training people to be competent with tools that we aren't responsible for (those tools' own docs are best for that). So, if you think yours are better for most of us, go with that one. I'd rather not have two, because then where does it end? Should we provide instructions with TortoiseSVN, eSvn, etc.? Best to stick with one. I think the native svn CLI is the best example of bare minimum functionality, but more of our devs are used to git. Then again, git-svn is a whole different beast on top of git. So, I'll leave it to your discretion. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
