Page History

...

Cutting a release candidate involves a two steps. First, we use the Maven release plug-in to create a release commit (a single commit where all of the version files have the correct number) and publish the code associated with that release to a staging repository in Maven. Second, we check out that release commit and package binary releases and documentation.

Setting up EC2

...

Instance (

...

Recommended)

• The process of cutting a release requires a number of tools to be locally installed (maven, jekyll, etc). And it takes a long time to create the release artifacts. For convenience, you can offload the creation to EC2 instance. Still, if you want to cut the release on your own machine, then skip this section. Note that if you are using a MacUbuntu users can install those tools via apt-get. However, it may be easier most convenient to use a EC2 instance than install the right versions of the necessary softwares.To create the EC2 instance, you can use the based on the AMI ami-4c721b7c (available is US-West) which . This has all the necessary tools installed. Or you can create Mac users are especially recommended to use a EC2 instance instead of attempting to install all the necessary tools. If you want to prepare your own EC2 instance by , follow the steps given in the Miscellaneous section (see at the end of this document).
• Consider using CPU-optimized instances, which may provide better bang for the buck.

• Transfer your GPG keys from your home machine to the EC2 instance.

  Code Block
  language bash
  # == On home machine == gpg --list-keys # Identify the KEY_ID of the key you generated gpg --output pubkey.gpg --export <KEY_ID> gpg --output ---export-secret-key <KEY_ID> | cat pubkey.gpg - | gpg --armor --output keys.asc --symmetric --cipher-algo AES256 # Copy keys.asc to EC2 instance   # == On EC2 machine == gpg --no-use-agent --output - keys.asc | gpg --import rm keys.asc

• Edit ~/.m2/settings.xml and specify your Apache user name and password. 

  Code Block
  language xml
  <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"> <servers> <server> <id>apache.snapshots.https</id> <username>APACHE_USERNAME</username> <password>PASSWORD</password> </server> <server> <id>apache.releases.https</id> <username>APACHE_USERNAME</username> <password>PASSWORD</password> </server> </servers> </settings>

• Download appropriate version of Spark that has the right scripts related to the releases.

...