THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Update the Spark Apache repository
Checkout the tagged commit for the release candidate and apply the correct version tag
Code Block language bash # Apply the correct tag $ git checkout v0.9.1-rc3 # checkout the RC that passed $ git tag v0.9.1 $ git push apache v0.9.1 # Verify on the Apache git repo that the tag has been applied correctly # Remove the old tag $ git push apache :v0.9.1-rc3
- Update remaining version numbers in the release branch
- If you are doing a patch release, see the similar commit made after the previous release in that branch. For example, for branch 1.0, see this example commit.
- In general, there should not be any reference to previous the just-released version, and all references to current next version should have -SNAPSHOT at the end. Grep through the repository to find such occurrences.
- Update the spark-ec2 scripts
- Upload the binary packages to the S3 bucket s3n://spark-related-packages (ask pwendell to do this)
- Alter the init scripts in mesos/spark-ec2 repository to pull new binaries (see this example commit and remember to update v2 branch for branch-0.9 releases)
- You can audit the ec2 set-up by launching a cluster and running this audit script
- Make sure you create cluster with default instance type (m1.xlarge)
- Update the Spark website
The website repo is at: https://svn.apache.org/repos/asf/spark
Code Block language bash $ svn co https://svn.apache.org/repos/asf/spark
Copy new documentation to spark/site/docs and update the "latest" link. Make sure that the docs were generated with PRODUCTION=1 tag, if it wasnt already generated with it.
Code Block language bash $ PRODUCTION=1 jekyll build
- Update the rest of the Spark website. See how previous release are documented on the site.
- Take a look at the changes to *.md files in this commit (all the html file changes are generated by jekyll).
- Create release notes
- Update documentation page
- Update downloads page
- Update the main page with a news item
- Take a look at the changes to *.md files in this commit (all the html file changes are generated by jekyll).
- Once everything is working (ec2, website docs, website changes) create an announcement on the website and then send an e-mail to the mailing list
- Enjoy an adult beverage of your choice, congrats on making a Spark release
...