Anthony Whyte's Sakai blog

sakai-2.6.0-rc04 now available

arwhyte@sakaifoundation.org — Fri, 22 May 2009 10:58:47 GMT

I've cut the sakai-2.6.0-rc04 tag that binds to the new kernel-1.0.8 release. It is ready for installation to QA servers.

The tag is available at

https://source.sakaiproject.org/svn/sakai/tags/sakai-2.6.0-rc04/

sakai-2.6.0-rc04 issues addressed:

http://bugs.sakaiproject.org/jira/browse/SAK/fixforversion/11500

sakai-2.6.0-rc03 tag cut and kernel-1.0.7 released

arwhyte@sakaifoundation.org — Sat, 09 May 2009 04:33:12 GMT

I've cut the sakai-2.6.0-rc03 tag that binds to the new kernel-1.0.7 release. It is ready for installation to QA servers. I held off on cutting the tag for a day in order to include a fix for an assignments blocker that was discovered and resolved on Friday.

The tag is available at

https://source.sakaiproject.org/svn/sakai/tags/sakai-2.6.0-rc03/

[INFO] sakai-2.6.0-rc03 issues addressed:

http://bugs.sakaiproject.org/jira/browse/SAK/fixforversion/11489

[INFO] kernel-1.0.7 issues addressed:

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

[WARN] I've moved all kernel SNAPSHOT artifacts to the new Sakai Maven2 SNAPSHOT repo. Sakai trunk, 2.6.x and 2.6.0 branch and sakai-2.6.0-rc3 /master/pom.xml have all been updated to operate with this new repo. If you have your own vendor dump or custom master/pom.xml please add the following declaration to the section of your master/pom.xml:

sakai-maven2-snapshots
Sakai Maven Repo
default
http://source.sakaiproject.org/maven2-snapshots

true

KERNEL REPO (stable releases):

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

KERNEL SNAPSHOT REPO:

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

sakai-kernel-1.0.6 has been released

arwhyte@sakaifoundation.org — Tue, 21 Apr 2009 12:47:00 GMT

I've released sakai-kernel-1.0.6 and updated the Sakai maven2 repo. 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. Issues addressed by earlier releases can also be reviewed in Jira.

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

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

K1 RELEASE: sakai-kernel-1.0.4

arwhyte@sakaifoundation.org — Fri, 27 Mar 2009 13:42:22 GMT

I've released sakai-kernel-1.0.4 and updated the Sakai maven2 repo. 1.0.4 has been released in support of the upcoming sakai-2.6.0 release. The issues addressed by 1.0.4 can be reviewed in Jira. Issues addressed by earlier releases can also be reviewed in Jira.

MAVEN2 REPO

The maven2 repo includes the following new or refreshed artifacts:

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

1.0.4
1.0.5-SNAPSHOT
1.1-SNAPSHOT

SVN

The 1.0.4 release has been tagged and the 2.6.x branch /master/pom.xml file has been updated to bind to 1.0.5-SNAPSHOT. When the next 2.6.0 tag is cut (either beta04 or rc01) it will be bound to K1 1.0.4.

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

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

Upcoming sakai-kernel-1.0.4 release (feedback requested)

arwhyte@sakaifoundation.org — Wed, 25 Mar 2009 14:49:10 GMT

The K1 team plans to release Kernel (K1) 1.0.4 on Friday, 27 March 2009 in order to address a small set of issues prior to the release of the next Sakai 2.6.0 tag (quite possibly sakai-2.6.0-rc01, otherwise sakai-2.6.0-beta04). If all goes well, the 1.0.4 release will be the final K1 release before the advent of Sakai 2.6.0. We invite review and comment on the upcoming release including open discussion of non-security-related issues that are currently not targeted for 1.0.4.

We have begun the process of subjecting K1 code to FindBugs scrutiny; issues generated by FindBugs are being addressed in trunk but in the main have not been merged to the 1.0.x branch given that we are in the final Sakai 2.6.0 testing phase.

K1 1.0.4 issues (fixed):

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

Outstanding K1 issues

http://bugs.sakaiproject.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&pid=10410&resolution=-1&sorter/field=updated&sorter/order=DESC

K1 Project

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

K1 Team

The following community members currently comprise the K1 team. If you have experience working with Sakai core services and are interested in either submitting patches or becoming an active K1 committer please contact me. Joining the team requires approval by the current membership but don't let that requirement prevent you from expressing interest.

Ian Boston, Cambridge
Ray Davis, UC Berkeley
David Horwitz, UCT
Beth Kirschner, UMich
Stephen Marquard, UCT
Seth Theriault, Columbia
Anthony Whyte, Sakai Foundation/UMich

We plan on soliciting community feedback on all future non-security-related releases.

sakai-maven-plugin 1.2.0 released

arwhyte@sakaifoundation.org — Tue, 03 Mar 2009 23:11:00 GMT

Last night I released version 1.2.0 of the sakai-maven-plugin in support of the upcoming Sakai 2.6.0 release. This is a trunk release of 1.2-SNAPSHOT (no maintenance branch having previously been created). 1.2-SNAPSHOT has been in use for some time now as a Maven build plugin dependency in both the Sakai trunk and Sakai 2.6.x master/pom.xml and a release is well overdue.

I have also created a plugin 1.2.x maintenance branch (1.2.1-SNAPSHOT) as well as updated plugin trunk to 1.3-SNAPSHOT. The maven2 repo has been updated with all three artifacts.

A quick test of the 1.2.0 repo artifact against an empty .m2/repository/org/sakaiproject/maven folder and a Sakai trunk build was successful. The new plugin artifact was downloaded and Sakai trunk was built, deployed and started up in Tomcat.

Usually, suggested bindings would be as follows:

tag: 1.2.0 (Sakai 2.6.0)
branch: 1.2.1-SNAPSHOT (Sakai 2.6.x)
trunk: 1.3-SNAPSHOT (Sakai 2.7.0/trunk)

However, the sakai-maven-plugin is a stable project with low code volatility so I plan to bind Sakai trunk, the 2.6.x branch and 2.6.0 to the 1.2.0 release.

sakai-2.6.0-beta03 ready for testing

arwhyte@sakaifoundation.org — Sat, 28 Feb 2009 07:48:16 GMT

I've generated the sakai-2.6.0-beta03 tag and it's ready for deployment to the QA servers. Beta03 binds to Kernel 1.0.3 and includes a number of additional Samigo fixes merged into the 2.6.x branch this morning by David Horwitz.

The tag downloads, builds, deploys and starts up in Tomcat 5.5.26 against my local MySQL 5.0.51 database.

https://source.sakaiproject.org/svn/master/tags/sakai-2.6.0-beta03/

Cheers from sunny, breezy Cape Town.

Instituto Politécnico de Bragança in production with Sakai

arwhyte@sakaifoundation.org — Sat, 28 Feb 2009 07:25:26 GMT

Paulo Alves reports that the Instituto Politécnico de Bragança (Portugal) is now running Sakai 2.5.3 in production. IPB.virtual (https://virtual.ipb.pt/portal) replaces Moodle, ATutor and a home-grown system. IPB's Sakai installation is home to over 800 sites and serves 5,891 users. The application is supported by 1.9 FTEs.

All good news.

NWU Mafikeng revisited

arwhyte@sakaifoundation.org — Thu, 26 Feb 2009 00:28:49 GMT

I was invited to speak again at the Sakai eFundi showcase at the Mafikeng campus of North West University. I had to get my jet-lagged body up at 5:00 am in order to join a combie of NWU Potch folks for the two and a half hour drive from the Potchestroom campus to Mafikeng but it was well worth the effort.

Mafikeng began using eFundi in 2008 (a year or so after Potch). It represents their first foray into online collaboration and learning and many of the faculty, staff and students have little experience with computers let alone the internet. In 2008 only 5 modules (approximating a course) were available to Mafikeng students; online Mafikeng modules have now risen to over 60.

I was asked to provide a Sakai briefing, Although I spoke at Mafikeng in 2008 many in room remain ignorant of the Sakai-eFundi relationship and the wider commmunity involved in the development of Sakai software. So my briefing helped set the context for the following talks discussing the uses of eFundi. I outlined briefly the nature, purpose and activities of the Sakai Community and Foundation before turning to discuss some of the enhancements that are included in the upcoming 2.6.0 release.

I then discussed Sakai 3 and the new approaches informing its development. Social learning, client-side widgets, a new user experience bulked large in the discussion. I expected that all this would be new to my listeners but as we talked I learned that few had ever heard of Facebook or even Google. Ignorance of Google was a surprise; in response I spent a few minutes talking about Google search, docs, spreadsheets, calendar and groups. I expect that many in the audience will give Google a look.

Mafikeng represents an interesting challenge for both NWU and the Sakai Community as little of what we take for granted in our daily discourse informs the thinking of campuses like Mafikeng. Hopefully, my briefing provided the NWU Mafikeng faculty and students with a few new ideas and resources to investigate. I look forward to returning in 2010.

Sakai 2.5.4 release artifacts

arwhyte@sakaifoundation.org — Tue, 10 Feb 2009 04:09:40 GMT

I generated the 2.5.4 release artifacts late last week and testing is nearly complete. I'd like to encourage Sakai Community members to grab an artifact (or two), make sure they build and start up in Tomcat and report back your findings.

The Sakai 2.5.4 maintenance release addresses 130+ issues. You can review the issues addressed in Jira. More information on the release can be found in the Release Management space in Confluence.

You can download the release artifacts (demo, bin, src) from the release page:

http://source.sakaiproject.org/release/2.5.4/

A tag is also available if you want to check out the code directly from our SVN repo:

svn co https://source.sakaiproject.org/svn/sakai/tags/sakai-2.5.4/ sakai-2.5.4

I've tested both the sakai-src-2.5.4.tgz and the sakai-2.5.4 tag.

Local test environment:

clean local .m2/repository/org/sakaiproject repo
clean Tomcat 5.5.26
empty MySQL 5.0.51 database

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

In both cases the 2.5.4 src *.tgz and the tag clean, install and deploy to Tomcat. Sakai starts in Tomcat. Login as admin. Project site created successfully. Logout.