Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Revisions

kernel trunk r62359 (1.1-SNAPSHOT refresh)
kernel-1.0.x r62388 (1.0.8, 1.0.9-SNAPSHOT)

New versions

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

Review 1.0.x/1.0.8 (tentative) merges

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

Testing exceptions

None.

Performing the release

...

Backup /kernel repo directory

(warning) Be conservative. Back up https://source.sakaiproject.org/maven2/org/sakaiproject/kernel/

...

(warning) Be conservative. Back up the target until we are sure that Maven properly pushes the new release to the repo.

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

(minus) ACHTUNG! BASE POM <distributionManagement> RELEASE REPO TARGET HAS NOT BEEN UPDATED

David: the release repo target still points to file:///tmp/maven2. Unless, the pom is updated to automate this step you must copy the Maven2 the contents of org/sakaiproject/kernel locally to /tmp/maven2/org/sakaiproject/kernel.

Copy Maven2 /kernel locally

(warning) This step will be rendered obsolete if changes to <distributionManagement> to point directly at the Maven2 repo are implemented.

Start now as this can take some time. Folder copy will later serve as target for deploying artifacts generated during the deploy phase.

...

No Format
mvn clean install 
mvn release:prepare

Trunk vs Branch releases

(warning) Not applicable for this release.

...

Update 2.6.x and 2.6.0 branch poms to bind to kernel-1.0.8. 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.8 version to released; add 1.0.8 9 (tentative).

Jira Release Mgmt project

...

No Format
I've released sakai-kernel-1.0.6 and updated the Sakai maven2 repo with fresh artifacts.  
1.0.6 has been released in support of the upcoming sakai-2.6.0 release.  
The issues addressed by 1.0.6 can be reviewed in Jira at

http://bugs.sakaiproject.org/jira/browse/KNL/fixforversion/11476

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

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


MAVEN2 REPO

The maven2 repo includes the following new or refreshed artifacts:

https://source.sakaiproject.org/maven2/org/sakaiproject/kernel/

1.0.6
1.0.7-SNAPSHOT
1.1-SNAPSHOT


SVN

The 1.0.6 release has been tagged and the 2.6.x branch /master/pom.xml file 
has been updated to bind to 1.0.7-SNAPSHOT.  
When the next 2.6.0 tag is cut it will bind to K1 1.0.6.


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 -Dmaven.test.skip=true sakai:deploy

cheers,

Anthony

...