Jump to: navigation, search

Jetty/Contributor/Release Process

Eclipse Jetty Release Notes

This release script is for jetty7, to release jetty8 the script is equivalent except instead of 'master' branch we use 'jetty-8' branch and instead of 'release' branch we use 'release-8'

1) Pick your version identification strings.

Example:

 Release Version         	: 7.5.0.v20110901  (v[year][month][day])
	(be sure you follow debian/redhat/osgi version naming rules)
 Next Development Version	: 7.5.0-SNAPSHOT
 Tag Name                	: jetty-7.5.0.v20110901

2) We use the 'release' branch to avoid problems with other developers actively working on the master branch.

  // Get all of the remotes
  $ git pull origin
  // Create a local tracking branch (if you haven't already)
  $ git branch --track release refs/remotes/origin/release
  // Check out your local tracking branch.
  $ git checkout release
 // Merge from master into the branch (this becomes your point in time 
 // from master that you will be releasing from)
  $ git merge --no-ff master

3) Update the VERSION.txt with changes from the git logs, this populates the resolves issues since the last release.

  $ mvn -N -Pupdate-version

4) Edit the VERSION.txt file to set the 'Release Version' at the top alongside the Date of this release.

  $ vi VERSION.txt
  

5) Make sure everything is commit'd and pushed to git.eclipse.org

  $ git commit -m "Updating VERSION.txt top section" VERSION.txt
  $ git push origin release

5.5) codehaus-only, you also want to update the pom.xml to set the jetty-version property to the correct value and commit then push that as well.


6) Prepare the Release

NOTE: This step updates the <version> elements in the pom.xml files, does a test build with these new versions, and then commits the pom.xml changes to your local git repo.

  $ mvn release:prepare -DreleaseVersion=7.5.0.RC2 -DdevelopmentVersion=7.5.0-SNAPSHOT -Dtag=jetty-7.5.0.RC2

7) Perform the Release

NOTE: This step performs the release and deploys it to a oss.sonatype.org staging repository.

  $ mvn release:perform

8) Set up files for next development versions.

Edit VERSION.txt for 'Next Development Version' at the top. Do not date this line.

Make sure everything is commit'd and pushed to git.eclipse.org

  $ git commit -m "Updating VERSION.txt top section" VERSION.txt
  $ git push origin release

8.5) codehaus-only, you want to reset the jetty-version to another development version

9) Merge back into master (or jetty-8 depending)

  $ git checkout master
  $ git merge --no-ff release
  $ git push origin master