Jetty/Contributor/Release Process

Eclipse Jetty Release Notes

Pick your version identification strings.

Example:

 Release Version         	: 7.5.0.RC2
	(be sure you follow debian/redhat/osgi version naming rules)
 Next Development Version	: 7.5.0-SNAPSHOT
 Tag Name                	: jetty-7.5.0.RC2

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

Update the VERSION.txt with changes from the git logs

  $ mvn -N -Pupdate-version

Edit the VERSION.txt file to set the 'Release Version' at the top. Along with the Date of this release.

  $ edit VERSION.txt
  

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

  Commit it.

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

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

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

  $ mvn release:perform

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

Merge back into master

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

Note: