...
Monday, 12:00 | Make sure the #One time setup steps have been performed.
| |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Monday, 12:01 | Create a sub-branch off of the parent branch from which to make the release. Releasing from a branch will allow any cosmetic changes that need to be made for the release to be approved to be done without preventing other more disruptive advances in the trunk from potentially causing problems with the release. A branch can be made by running:
| |||||||||
Monday, 12:02 | Checkout the branch using command line svn.
| |||||||||
Monday, 12:04 | Update the text files which are included in the release. See instructions at Update release text files for details. | |||||||||
Monday, 12:10 | Commit these changes back to the branch
| |||||||||
Monday, 12:11 | Do a dry run of the release plugin. The dry run will not commit any changes back to SVN and gives you the opportunity to verify that the release process will complete as expected. You will be prompted for the following information :
| |||||||||
Monday, 12:30 | Validate that the release process completed as expected. The release plugin will create pom.xml.tag files which contain the changes that would have been committed to SVN. The only differences between pom.xml.tag and it's corresponding pom.xml file should be the version number. If other formatting changes have been made you should rollback the release and commit the changes manually.
| |||||||||
Monday, 12:31 | Assuming the .tag files look OK you may proceed and do any other validation you feel necessary. The following list may be helpful
| |||||||||
Monday, 12:52 | Prepare the release. You'll be prompted for the version information and optionally your GPG passphrase again.
| |||||||||
Monday, 13:15 | Perform the release. This step will create a maven repository for use in testing on people.apache.org:/home/userName/public_html/openjpa/newVersion. You will may be prompted for your people.apache.org password several times if you have not added a ssh key to .authorized_keys. One time setup #One time setup#people.apache.org.
| |||||||||
Monday, 13:40 | Create and upload the site. This step also uploads data to people.apache.org.
| |||||||||
Monday, 13:40 | Unzip the binary archive the staging site directory
| |||||||||
Monday, 13:41 | Send an email to dev@openjpa.apache.org requesting a vote. Vote email example | |||||||||
Tuesday, Wednesday, Thursday | A -1 vote does not necessarily mean that the vote must be redone however it is usually a good idea to rollback the release if a -1 vote is received. Recovering from a vetoed release | |||||||||
Thursday, 13:41 | If the vote passes copy the release artifacts from your home directory to the ibiblio-rsync-repository using the maven stage plugin.
After the stage plugin completes it's a good idea to check the permissions on the file system.
| |||||||||
Thursday, 14:00 | Copy build artifacts to the openjpa/builds location on people.apache.org.
| |||||||||
Thursday, 14:10 | Copy the distribution files to dist on people.apache.org.
| |||||||||
Thursday, 14:15 | Update the JIRA versions page to mark the version as "released", and set the date to the date that the release was approved. You may also need to make a new release entry for the subsequent release. | |||||||||
Friday, 14:15 | After the mirrors have had time to update (24 hours to be on the safe side) update the downloads page with the new release | |||||||||
Friday, 14:15 | Make a news announcement on the OpenJPA wiki.
| |||||||||
Friday, 14:15 | Make an announcement about the release on the users@openjpa.apache.org list (and, for major releases, on the announce@apache.org list as per the Apache Announcement Mailing Lists page). The announcement might look something like this. | |||||||||
Friday, 14:20 | Make an announcement for the freshmeat.net OpenJPA project (optional) | |||||||||
Friday, 14:30 | Have a beer and enjoy your weekend while the world's grateful programmers revel in yet another high-quality release of Apache OpenJPA! |
...
Info |
---|
Developers using Linux workstations can skip over the references to PuTTY and CygwinCygwin. If using Windows, install cygwin, including Utils/gnupg and Net/openssh packages. |
Create and install a SSH key
1 | Install PuTTY | Open a shell window. If using Windows, open a cygwin window. | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
2 2a | Use ssh-keygen to create a an SSH key.
| |||||||||||
2b | In Windows platform, use PuttyGen to create a SSH key (see Putty help for details).
| |||||||||||
| ||||||||||||
3 | | 3 | | 4 | Use PuTTY to login to id_dsa.pub on people.apache.org. | |||||||
5 | Create a | |||||||||||
| 6 | Move or append ~/authorized_keys to
| ||||||||||
7 | Configure putty to use your private key and save the session
|
Create a PGP key
1 | Install cgywin, including Utils/gnupg and Net/openssh packages, or install gpg from | ||
---|---|---|---|
2 | Generate a key-pair with
| ||
3 | Backup your cygwin home directory to another media | ||
4 | Add your public key to | ||
5 | Following the instructions in http://people.apache.org/~henkp/trust/ and ask someone in the OpenJPA project to sign your public key. | ||
6 | Submit your public key to a key server. E.g. http://pgp.surfnet.nl:11371/ or http://pgp.mit.edu/ |
Update Maven settings for our servers
| ||||||||||
4 | Use ssh to login to people.apache.org
| |||||||||
---|---|---|---|---|---|---|---|---|---|---|
5 | Create a ~/.ssh folder in your home directory on people.apache.org and change its file mode to 700.
| |||||||||
6 | Move or append ~/id_dsa.pub to ~/.ssh/authorized_keys and change its file mode to 600.
| |||||||||
7 | Exit out of this ssh session. | |||||||||
8 | 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).
| |||||||||
Create a GPG key
1 | Open a shell window. If using Windows, open a cygwin window. | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
2 | Generate a key-pair with gpg, using default key kind ("DSA and Elgamal") and ELG-E keys size (2048).
| |||||||||
3 | Backup your cygwin home directory to another media | |||||||||
4 | Add your public key to ![]() }}. See the commands describe at the beginning of this KEYS file to perform this task. The gpg key-pair is used to sign the published artifacts for the OpenJPA releases.
| |||||||||
5 | Following the instructions in http://people.apache.org/~henkp/trust/ and ask someone in the OpenJPA project to sign your public key. | |||||||||
6 | Submit your public key to a key server. E.g. http://pgp.surfnet.nl:11371/ or http://pgp.mit.edu/ |
Update Maven settings for our servers
1 | Create a settings.xml under .m2 (in your Document and Settings folder in Windows) | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| ||||||||||||
1 | Create a settings.xml under .m2 (in your Document and Settings folder in Windows) | ||||||||||||
|
|
Expose a copy of known hosts to Maven
Info |
---|
Is this step even necessary? Due to the question mark below without an explanation of the new location for this alternate .ssh folder, I never performed these steps. And, the release process still seemed to work okay for me... The next person to use these instructions can verify whether any tricks had to be played with the .ssh folders... |
1 | From cygwin, ssh to people.apache.org, save the public key if prompted, and exit |
---|---|
| cygwin will save the known hosts to your |
2 | From cygwin (not Windows) create another |
3 | Copy the |
...