Releasing Selenium

Luke Inman-Semerau edited this page Aug 2, 2016 · 7 revisions

Release criteria

The release manager needs to evaluate if the codebase is ready for release. This normally involves some subjective judgements. A few things can be noted:

  • go test_selenium should pass
  • chromedriver is not part of the project. While test failures are /interesting/, they are normally not blocking. Running tests without chromedriver on your path simplifies things a bit.

Known issues can be added to the release notes.

For Everything

  1. Gather feedback from other developers about the release: Define a time for the release, ask for release blockers and provide additional details that will help developers participate in the release process. This should be emailed to 'selenium-developers' though working on IRC alone is just fine.
  2. Bump the revision numbers at the top of the Rakefile and SELENIUM_VERSION
  3. Bump the revision number in javascript/firefox-driver/extension/install.rdf
  4. Commit version number bump.
  5. To find out the revision of the last release: git log --tags --simplify-by-decoration --pretty="format:%ci %d %h" | sort | tail -1 | awk '{print $NF}'. This will give you the abbreviated hashcode for the last revision.

For Java

  1. Update the Java CHANGELOG under java/CHANGELOG. Do this by finding the revision number of the last release and running git log oldRev..HEAD >> java/CHANGELOG. You'll then need to edit the file by hand.
  2. Update the SeHQ downloads page with updated links, release numbers and dates
  3. Run ./go clean release
  4. Upload the new versions of the ZIP files from "build/dist" to the downloads page. Alternatively, run ./go push_release to have the artifacts uploaded for you.
  5. Add a git tag: git tag selenium-3.<REVISION> hash where "hash" refers to the revision to tag. This creates a lightweight tag, so there's no need to add a log message. You'll need to push that change to the origin repo with git push origin --tags
  6. Update the api docs. See Update API Docs for Java and python

Updating the Maven Repos

  1. Prerequisite 1: Make sure Maven 2.2.1 and GnuPG are installed.
  2. Prerequisite 2: Make sure your ~/.m2/settings.xml contains the following lines in the <servers> section:
  1. Prerequisite 3: Make sure your GnuPG public key is distributed to hkp://
  2. Make sure the dependencies in all pom.xml files under the maven directory are correct -- if not, update them (Hint: check for changes in the third_party directory)
  3. Perform any manual steps/release hacks documented here:
    1. To provide the correct version info in a WebDriverException you should also replace "unknown" in the maven/api/pom.xml with the Git commit number wich forked the version branch:
-                <Selenium-Revision>unknown</Selenium-Revision>
+                <Selenium-Revision>12345</Selenium-Revision>
  1. Update the version number in all pom.xml files under the maven directory (but do not check in those changes) (mvn versions:set -DnewVersion=2.3.0 inside the "maven" folder)
  2. MAKE SURE YOU HAVE JAVA 7 DEFAULTED ON YOUR PATH (at least until the javadoc's are fixed to work with java 8)
  3. Execute:
    1. ./go release
    2. cd maven
    3. mvn -Dtest=skip -DfailIfNoTests=false install
  4. Execute: > > mvn source:jar javadoc:jar -Dtest=skip -DfailIfNoTests=false -Dgpg.passphrase=_your-GnuPG-key-passphrase_ -Psign deploy
  5. Goto, log in, close the staging repository.
  6. Test the artifacts, these are the real files you will be irreversibly promoting to central. You can do this easily by cloning the repo at and following the instructions there. (Once the staging repository has been closed you get the url to the repository by clicking on the repository. This url can be added to your project pom to test if you want to test using a different project. Remember that you may need to delete the artifacts in your local repository to make sure you re-download the staged artifacts).
  7. Promote that staged release in nexus (or drop it).
  8. Make sure any other manual hacks you did are documented in step 5 or committed back on trunk.
  9. Once the artifacts finally hit central (please wait till they are actually there), update the maven downloads page on SeHQ. If you can't wait don't update the page, someone will notice and update it.

For .NET

  1. Verify the build number is correct in dotnet/build.desc
  2. Verify the build number is correct in the AssemblyVersion and AssemblyFileVersion attributes in the AssemblyInfo.cs file of each of the following projects:
    • Selenium.Core
    • Selenium.WebDriverBackedSelenium
    • WebDriver
    • WebDriver.Support
  3. Run go clean //dotnet:release. Note that this will require you to have the .NET documentation generation tools installed.
  4. Upload the file from build/dotnet to the downloads page.
  5. Update the SeHQ downloads page with updated links, release numbers and dates

For Ruby


  1. To release a new gem you will need to be registered as a gem owner on
    1. Bump the version number in rb/build.desc.
    2. Update rb/CHANGES with a summary of changes since the last release.
    3. Update docs: rm -rf docs/api/rb && ./go //rb:docs (you'll need the YARD gem installed)
    4. Commit the changes.
    5. ./go //rb:gem:release
    6. Bump version number in rb/build.desc to "" and commit the change.
    7. Update the SeHQ downloads page with updated links, release numbers and dates

For Python

To release a new version you need to be registered as a Owner/Maintener on

  1. Bump the version numbers

    1. in
    2. in py/README
    3. in py/selenium/
    4. in py/selenium/webdriver/
    5. in py/docs/source/index.rst
  2. check that in.

  3. ./go py_release ~ have your credentials stored in ~/.pypirc
  4. Bump the version number to the next version with dev e.g. 2.(n+1).0 and commit changes
  5. Update the SeHQ downloads page with updated links, release numbers and dates
  6. See Update API Docs for Java and python

Update API Docs for Java and python

  1. from the root of the repo run: ./

Areas to Improve

  • We should really automate the version number bumps.