- Change 3 POMs (pom.xml, server/pom.xml, clients/java/pom.xml) and
clients/build.xml to final version number (no -SNAPSHOT) (hence, if we
were at 1.2.3-SNAPSHOT, make it 1.2.3)
- Do a build
- (BEA only) Promote that build to INTERNAL
- Login to release.openqa.org as the user release (requires a private
key)
- cd release.openqa.org/htdocs/selenium-remote-control/; cp -R nightly/
[yourversion] (you will need an SSH private key to do this, ask Patrick Lightbody for one)
- Change the POMs + build.xml to the next version, with -SNAPSHOT. The
version you're going towards (hence, if we were 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
- 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/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
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; selenium-rc-users@openqa.org;
selenium-rc-dev@openqa.org
|
|
