Author: allee8285
Date: Thu Nov 15 23:49:00 2012
New Revision: 1410112
URL: http://svn.apache.org/viewvc?rev=1410112&view=rev
Log:
CMS migration updates.
Modified:
openjpa/site/trunk/WhoIsWorkingOnWhat.txt
openjpa/site/trunk/content/release-setup.mdtext
Modified: openjpa/site/trunk/WhoIsWorkingOnWhat.txt
URL:
http://svn.apache.org/viewvc/openjpa/site/trunk/WhoIsWorkingOnWhat.txt?rev=1410112&r1=1410111&r2=1410112&view=diff
==============================================================================
--- openjpa/site/trunk/WhoIsWorkingOnWhat.txt (original)
+++ openjpa/site/trunk/WhoIsWorkingOnWhat.txt Thu Nov 15 23:49:00 2012
@@ -102,7 +102,7 @@ done quick-start.mdtext
recovering-from-a-vetoed-release.mdtext
related-projects.mdtext
release-management.mdtext
- release-setup.mdtext
+leealber release-setup.mdtext
releasing-openjpa-1.0.x-or-1.1.x-(old-scp-steps).mdtext
releasing-openjpa-1.2.x-(old-scp-steps).mdtext
running-openjpa-examples.mdtext
Modified: openjpa/site/trunk/content/release-setup.mdtext
URL:
http://svn.apache.org/viewvc/openjpa/site/trunk/content/release-setup.mdtext?rev=1410112&r1=1410111&r2=1410112&view=diff
==============================================================================
--- openjpa/site/trunk/content/release-setup.mdtext (original)
+++ openjpa/site/trunk/content/release-setup.mdtext Thu Nov 15 23:49:00 2012
@@ -1,54 +1,62 @@
Title: Release Setup
+<a name="Release-Setup"></a>
+
These setup steps only need to be performed on a particular machine once.
-Developers using Linux workstations can skip over the references to Cygwin.
If using Windows, install cygwin, including __Utils/gnupg__ and __Net/openssh__
packages.
+
+ > Developers using Linux workstations can skip over the references to Cygwin.
If using Windows, install cygwin, including **Utils/gnupg** and
**Net/openssh** packages.
<a name="ReleaseSetup-CreateandinstallaSSHkey"></a>
### Create and install a SSH key
1. Open a shell window. If using Windows, open a cygwin window.
1. Use ssh-keygen to create an SSH key.
-{note}
- * ssh-keygen dsa key type only accept 1024 bits; use rsa / 4096 bits
instead.
+
+ > ssh-keygen dsa key type only accept 1024 bits; use rsa / 4096 bits
instead.
+
$ ssh-keygen -t rsa -b 4096
- Program defaults should be fine. No passphrase is required for the ssh
key generation. The keys will be saved in ~/.ssh/id_rsa (private) and
~/.ssh/id_rsa.pub (public).
+ Program defaults should be fine. No passphrase is required for the ssh key
generation. The keys will be saved in ~/.ssh/id_rsa (private) and
~/.ssh/id_rsa.pub (public).
- See [Authenticating By Public
Key(OpenSSH)](http://www.networknewz.com/networknewz-10-20030707AuthenticatingbyPublicKeyOpenSSH.html)
for a good description on why and how to perform this task.
+ > See [Authenticating By Public
Key(OpenSSH)](http://www.networknewz.com/networknewz-10-20030707AuthenticatingbyPublicKeyOpenSSH.html)
for a good description on why and how to perform this task.
1. scp your SSH public key ~/.ssh/id_rsa.pub created in last step to
~/id_rsa.pub on people.apache.org.
- $ cd ~/.ssh
- $ scp id_rsa.pub <your userid>@people.apache.org:id_rsa.pub
+ $ cd ~/.ssh
+ $ scp id_rsa.pub <your userid>@people.apache.org:id_rsa.pub
- You will be prompted for your password.
+ You will be prompted for your password.
1. Use ssh to login to people.apache.org
- $ cd ~
- $ ssh <your userid>@people.apache.org
+ $ cd ~
+ $ ssh <your userid>@people.apache.org
At this point, you will still be prompted for your password.
+
1. Create a ~/.ssh folder in your home directory on people.apache.org and
change its file mode to 700.
- $ mkdir ~/.ssh
- $ chmod 700 ~/.ssh
+ $ mkdir ~/.ssh
+ $ chmod 700 ~/.ssh
1. Move or append ~/id_rsa.pub to ~/.ssh/authorized_keys and change its file
mode to 600.
- $ mv ~/id_rsa.pub ~/.ssh/authorized_keys
-or
- $ cat ~/id_rsa.pub >> ~/.ssh/authorized_keys
- $ chmod 600 ~/.ssh/authorized_keys
-
- * Each public key in the {{authorized_keys}} spans only one line.
- * For example:
- "{{ssh-dss AAAAB3NzaC1kc3MAAA ..... agBmmfZ9uAbSqA==
dsa-key-20071107}}"
- * '#' in the first column is a comment line.
+ $ mv ~/id_rsa.pub ~/.ssh/authorized_keys
+ or
+ $ cat ~/id_rsa.pub >> ~/.ssh/authorized_keys
+ $ chmod 600 ~/.ssh/authorized_keys
+
+ > * Each public key in the {{authorized_keys}} spans only one line.
+ > * For example:
+ > "{{ssh-dss AAAAB3NzaC1kc3MAAA ..... agBmmfZ9uAbSqA==
dsa-key-20071107}}"
+ > * '#' in the first column is a comment line.
+
1. Exit out of this ssh session.
+
1. Start a new ssh session. No login should be required this time due to the
private ssh key on your local box matching up with the public ssh key in your
home directory (~/.ssh).
- $ ssh <your userid>@people.apache.org
-If you are still prompted for a password, then you have not set up the ssh
keys properly. Review the steps above and ensure that all of the steps
were followed properly. Or, maybe the instructions are still not quite right
and they still need some adjusting. In that case, please update the
instructions accordingly. :-)
+ $ ssh <your userid>@people.apache.org
+
+ > If you are still prompted for a password, then you have not set up the
ssh keys properly. Review the steps above and ensure that all of the
steps were followed properly. Or, maybe the instructions are still not quite
right and they still need some adjusting. In that case, please update the
instructions accordingly. :-)
<a name="ReleaseSetup-CreateaGPGkey"></a>
