Release Process

Here are the simple steps to release a new set of docker-selenium images.

For Selenium 4, trunk branch

1. Pull down the latest changes from master
2. Trigger the release with an empty commit and add [deploy] to the commit message.
   1. e.g. git commit --allow-empty -m "Trigger release [deploy]"

To do a prerelease (a Grid build that is not yet officially released)

1. Make the Grid jar available and downloadable via a public URL.
2. Change the base docker image and use the URL created in step 1.
3. Commit your changes and add [deploy][prerelease] to the commit message.
   1. e.g. git commit -m "Grid version X.Y prerelease [deploy][prerelease]"

For Selenium 3, selenium-3 branch. This branch is still released until Selenium 4 is released.

1. Pull down the latest changes from selenium-3
2. # VERSION=3.141.59-<YYYYMMDD> make generate_all
3. Mass replace in the directory the old version, with the new
4. # git commit -am "3.141.59-<YYYYMMDD> release"
5. # git tag 3.141.59-<YYYYMMDD>
6. # git push origin selenium-3 && git push --tags

• See the tagging convention explanation here.