Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Current »

Revisions

kernel trunk r63343 (1.1-SNAPSHOT refresh)
kernel-1.0.x r63328 (1.0.9, 1.0.10-SNAPSHOT)

New versions

Tag: 1.0.9
Branch: 1.0.10-SNAPSHOT
Trunk 1.1-SNAPSHOT

Review 1.0.x/1.0.9 (tentative) merges

Confirm that all merges scheduled for kernel-1.0.9 have been merged to the 1.0.x branch.

Testing exceptions

None.

Backup Sakai Maven2 Repo /kernel

(warning) Be conservative. Back up https://source.sakaiproject.org/maven2/org/sakaiproject/kernel/ until we are sure that Maven properly pushes the new release to the repo.

cd /var/www/html/maven2/org/sakaiproject
tar -czvf  kernel-[YEARMONTHDAYHOURMINSEC].tgz kernel

Checkout the kernel project

Checkout a clean version of the project using SVN not git.

svn co https://source.sakaiproject.org/svn/kernel/branches/kernel-1.0.x/ kernel-1.0.x

(warning) Avoid opening 1.0.x in Eclipse; otherwise you will pollute the projects with Eclipse metadata files that will have to be deleted before performing the release. Checkout with svn (not git)

Clean out local repo

Verify that a clean build works ok with no external dependencies. Issuing mvn -o clean install ensures that .m2 repo is populated, a requirement for the assembly plugin. If the build fails because external dependencies are missing in .m2 run mvn clean install, then delete /kernel and run mvn -o clean install again.

rm -rf ~/.m2/repository/org/sakaiproject/kernel
mvn -o clean install

Note: check for Eclipse metadata files (.classpath, .project) and remove. Uncommitted versions of these files will cause mvn release:prepare to fail.

Run integration tests

(warning) Note: not sure if we are ready for this step.

See integration test set up instructions at https://source.sakaiproject.org/svn/test-harness/trunk/xdocs/README-INTEGRATION-TESTING.txt

Create tag

Issue the following release plugin goals. Do a dry run first.

mvn release:prepare -DdryRun=true
mvn release:clean release:prepare release:perform

(warning) Unlicensed user: the combination of Maven 2.0.10 (or 2.1.0), Subversion 1.5.6 and maven-release-plugin 2.0-beta-9 on Mac 10.5.7 (Leopard) resulted in a svn commit failure during the release:perform phase when attempting to update the branch pom <version>. I resolved this issue by first performing a rollback and then added my username and password as arguments to the clean/prepare/perform goals. This problem occurred despite my abilit to commit to our SVN SCM system normally using either my username/password or SSH private/public key.

mvn release:rollback
mvn -Dusername=arwhyte@umich.edu -Dpassword=mypassword release:clean release:prepare release:perform

When prompted for new versions:

#set the released version to 1.0.9
#set the tag to kernel-1.0.9
#set the the new version to 1.0.10-SNAPSHOT

Should the build fail rerun the following mvn goals to restart the build:

mvn clean install 
mvn release:prepare

Trunk vs Branch releases

(warning) Not applicable for this release.

When releasing from trunk, issue the branch goal to create a new branch:

mvn release:clean  (clean up release)  
mvn release:branch -DbranchName=kernel-1.1.x

The release plugin will then branch the current trunk to branches/kernel-1.1.x.
Edit the poms to 1.2-SNAPSHOT and commit.

(warning) If the release:perform should hang for some reason you can check out the tag do the following:

  1. restore maven2/org/sakaiproject/kernel from backup *.tgz
  2. check out 1.0.9 tag and generate release from tag:
cd 1.0.9
mvn release:perform -DconnectionUrl=scm:svn:https://source.sakaiproject.org/svn/kernel/tags/kernel-1.0.9

Check 1.0.9 tag

The release plugin will generate a 1.0.9 tag. Check it out and make sure it works, binding it against a local working copy of 2.6.x.

Refresh Maven Repo with 1.0.9, 1.0.10-SNAPSHOT and 1.1-SNAPSHOT artifacts

For each new version (release, SNAPSHOT) issue the following command from the root folder:

If a release:

mvn -Prelease clean install deploy -DupdateReleaseInfo=true

if a SNAPSHOT:

mvn clean install javadoc:jar source:jar deploy

1. Check out 1.0.x branch (1.0.10-SNAPSHOT) and perform

mvn deploy

2. Check out kernel trunk (1.1-SHAPSHOT) and perform

mvn clean install javadoc:jar source:jar deploy

Maven will deploy the new artifacts to the Sakai Maven2 SNAPSHOT Repo automatically.

Confirmation

  1. Confirm Maven2 repo and Maven2 snapshot repo are populated with new artifacts
  2. Confirm repo permissions are correct
sudo chown -R apache:apache kernel

Repo cleanup

Move old /kernel backup archive to /var/www/html/tarball. Delete kernel-1.0.9.tgz.

Base pom.xml updates

Update 2.6.x and 2.6.0 branch poms to bind to kernel-1.0.9. File a Jira on this in order to document pom updates.

Jira Kernel project

Go to "manage versions" console at http://bugs.sakaiproject.org/jira/secure/project/ManageVersions.jspa?pid=10410

Set 1.0.9 version to released; add 1.0.9 (tentative).

Jira Release Mgmt project

Update home page and Kernel page.

Inform community with email.

(warning) links for fixforversion need to be updated to point to 1.0.9.

Example:

I've released sakai-kernel-1.0.9 and updated both the Sakai maven2 release and snapshot repositories with fresh artifacts (1.0.9, 1.0.10-SNAPSHOT; 1.1-SNAPSHOT was refreshed yesterday).  Both Sakai 2.6.x and the upcoming sakai-2.6.0-rc05 will bind to 1.0.9.  The issues addressed by 1.0.9 can be reviewed in Jira at

http://jira.sakaiproject.org/jira/browse/KNL/fixforversion/11505

Issues addressed by earlier releases can also be reviewed in Jira at

http://jira.sakaiproject.org/jira/browse/KNL?report=com.atlassian.jira.plugin.system.project:versions-panel

KERNEL (K1) PROJECT INFO

Jira: http://bugs.sakaiproject.org/jira/browse/KNL
Confluence: http://bugs.sakaiproject.org/confluence/display/REL/Kernel+1+(K1)

NOTICE: TRUNK/CONTRIB DEVELOPERS DEVELOPING AGAINST K1

Please refresh your local development environment.

1. MVN: Backup/delete the .m2/repository/org/sakaiproject/kernel of
your repo
2. SVN: perform an svn update on sakai trunk code (this will pick up
Sakai updates that complement the K1 updates)
3. MVN: perform a clean and install on your sakai trunk code to
refresh your .m2 repo with updated kernel 1.1-SNAPSHOT artifacts.
4. Build and deploy to Tomcat.

cd master
mvn clean install
cd ..
mvn clean install sakai:deploy

cheers,

Anthony

References

Maven Release Plugin
Maven mini-guide
J. Ferguson, "Using the Maven Release Plugin"

  • No labels