- Finish all of our Manual Testing for Selenium Core. (Beware! Selenium Core requires quite a bit of manual testing.)
- Change the version number at the top of pom.xml to final version number (no -SNAPSHOT) (hence, if we
were at 1.2.3-SNAPSHOT, make it 1.2.3) - Check in, do an official build
- Download the official build from http://maven.openqa.org/org/openqa/selenium/core/selenium-core/ inside the "1.2.3" directory (corresponding to the official build you just did)
- Login to release.openqa.org as the user release (you will need an SSH private key to do this, ask Patrick Lightbody for one): ssh -i myprivatekey release@release.openqa.org
- cd release.openqa.org/htdocs/selenium-core/; mkdir 1.2.3
- Upload the selenium-core official build to the directory you just made
- Change pom.xml to the next version, with -SNAPSHOT. The
version you're going towards (hence, if we're releasing 1.2.3, make it
1.2.4-SNAPSHOT) - Manage the versions in JIRA; create a new version we're moving towards,
make sure bugs are targeted for correct versions. Click on the "Release"
link to mark the current version as "released"; this gives it a release
date. - Edit meta.xml; create a new <release> containing your new version
number, new Jira ID, new URL to download - Check in a new website/reference.html with the versions from the latest build.
- Write up some release notes; Add them to release-notes.html.
- Copy those release notes into the Wiki News section.
http://wiki.openqa.org/display/SEL/Home Click on "Add News" in the
upper-right corner. This will eventually push news out to the website. - Update index.html to include a reference to the proper latest version
- Check in website changes; wait five minutes for changes to appear in
index.html - meta.xml doesn't get refreshed until you "clear the project cache":
http://www.openqa.org/clearProjectCache.jsp (don't bother until index.html
is updated) - Make sure everything looks good on the website before sending e-mail
- Send out the mail! selenium-users@openqa.org;
selenium-dev@openqa.org