Pre-Release tasks

The following tasks should be performed at least one day before starting the actual maven release!

• Check that the latest apache-parent pom is used from http://repo1.maven.org/maven2/org/apache/apache/

• Check that all maven plugins are used in the latest version

  Code Block
  $> mvn versions:display-plugin-updates

• Check that all maven dependencies are used in the latest version

  Code Block
  $> mvn versions:display-dependency-updates

Release Preparations

• Heads up on the mailing-lists

...

first steps for the next release

hi @ all,

if there are no objections, i'll start with the first steps for the next release (review, documentation,...).
it would be great to start with the release procedure next week.

regards,
...

• Check the documentation https://cwiki.apache.org/confluence/display/DeltaSpike/Temporary+Documentation^{Image Removed}
• Check https://analysis.apache.org/dashboard/index/org.apache.deltaspike:deltaspike-project^{Image Removed}
• Check diff with tag of version-1
• Check the Jenkins builds at https://builds.apache.org/view/A-F/view/DeltaSpike/^{Image Removed}
• Check the integration tests
• Create release notes and commit them to https://git-wip-us.apache.org/repos/asf?p=incubator-deltaspike.git;a=tree;f=deltaspike^{Image Removed} /readme/ (format READMEversion.txt)
• rat check

...

mvn release:prepare -DdryRun=true

//attention: use an useful tag-name (asked before the new version numbers) format [deltaspike-[version]]


//important: check the generated javadoc

//important: check if content was lost during release:prepare (especially license headers in pom.xml files)

mvn release:clean

mvn deploy

//check http://repository.apache.org/content/repositories/snapshots/org/apache/deltaspike/*

mvn release:prepare -Papache-release
//attention: use an useful tag-name (asked before the new version numbers)
//attention: invoke x2 (esp. in european countries)

//check tag in svn

// ATTENTION, THIS IS ONLY A WORKAROUND!
// AND WILL NOT BE NEEDED AFTER THE NEW maven-release-plugin GOT RELEASED 
cp -r ../git . 
// DON'T FORGET TO DELETE deltaspike/deltaspike/.git AGAIN AFTER THE RELEASE! 

mvn release:perform -Papache-release

//login to https://repository.apache.org/ and go to "Staging Repositories"
//check the shadded configs and esp. ...-[version]-source-release.zip
//close the repository

...

create a link to the release notes at http://s.apache.org^{Image Removed} (format DeltaSpike_version)

...

If the binding majority approved the vote continue.

• Login to https://repository.apache.org/^{Image Removed} and release the repository
• Create the release at jira (https://issues.apache.org/jira/plugins/servlet/project-config/DELTASPIKE/versions^{Image Removed})
• Close the corresponding tickets of the version
• Wait some hours and check http://repo2.maven.org/maven2/org/apache/deltaspike^{Image Removed}

Announce the Release

...

• Write blog entries

Post release steps

• Update https://cwiki.apache.org/confluence/display/DeltaSpike/History^{Image Removed}
• Add the release to the DeltaSpike report
• Check all version numbers

Push release branch and tag

git remote add release_repo [release repo]
git fetch release_repo

git checkout master
git pull --rebase

git checkout -b deltaspike-0.1-incubating release_repo/deltaspike-0.1-incubating   //now we are on the release branch
git push origin deltaspike-0.1-incubating
git push origin deltaspike-project-0.1-incubating

Merge back release branch

git checkout master
git pull --rebase
git merge deltaspike-0.1-incubating
git push //origin master

git remote rm release_repo