- Run the manual tests.
- Change all POMs to final version number (no -SNAPSHOT) (hence, if we
were at 1.2.3-SNAPSHOT, make it 1.2.3)
- Do a build
- Login to release.openqa.org as the user release (you will need an SSH private key to do this, ask Patrick Lightbody for one)
- cd release.openqa.org/htdocs/selenium-remote-control/; mkdir 1.2.3
- wget the latest build from http://maven.openqa.org/org/openqa/selenium/selenium-remote-control/ into the directory you just created
- wget the latest documentation zip from http://maven.openqa.org/org/openqa/selenium/selenium-rc-documentation/ Extract the documentation into the 1.2.3 directory; this should create a 1.2.3/doc directory containing all of the doc dirs.
- Change the POMs to the next version, with -SNAPSHOT. The version you're going towards (hence, if we were 1.2.3, make it
- Update clients/perl/create_www_selenium.pl to refer to the new version (1.2.4)
- Check in and let the new 1.2.4-SNAPSHOT build go through
- Now we need to update the "latest nightly" link on the download page. Login to release.openqa.org again. cd release.openqa.org/cgi-bin. In there there's a perl script called "selenium-remote-control-redirect.zip". (It's called .zip so it doesn't confuse the browsers.) Edit it and change the version number at the top of the file to 1.2.4.
- Manage the versions in JIRA; create a new version we're moving towards, (1.2.4)
make sure bugs are targeted for correct versions. Click on the "Release"
link to mark the current version as "released"; assign it a release
date. Note the Jira ID of v1.2.4, you'll need it in a second.
- Edit meta.xml; create a new <release> containing your just-released version
number, Jira ID, new URL to download. Update the "latest nightly" Jira ID to point to the 1.2.4 changelog.
- Write up some release notes; Add them to release-notes.html.
- In the *.html files in website, replace the URLs to the JavaDoc, NDoc, PerlDoc, PhpDoc, PyDoc, and RubyDoc with newer versions. Note that the Perl doc is actually stored in the website directory (to give it some styling), so be sure to replace website/perl/* with the updated doc; website/perl.html therefore doesn't need updating
- Copy those release notes into the Wiki News section.
http://wiki.openqa.org/display/SRC/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
- meta.xml doesn't get refreshed until you "clear the project cache":
http://www.openqa.org/clearProjectCache.jsp (don't bother until index.html
- Make sure everything looks good on the website before sending e-mail
- Send out the mail! email@example.com;