[Deploying Sakai] STATUS UPDATE: Sakai Jira and Confluence Migration

Knoop, Peter knoop at umich.edu
Mon Jun 29 11:35:07 PDT 2009

Jira migration is in progress and should be completed in about 3 hours.

Confluence migration will be started once the Jira migration is complete.  If you are suffering from intense Confluence-withdrawal, you can currently access a read-only version of Confluence at:


This archival version of confluence will remain available over the next several days as we complete migration of content; however, it is in read-only mode, and only contains updates made through early this morning.  As spaces are migrated from this old server to the new server they will be hidden on the old server.  So, if you cannot find what you are looking for, then it should already be available on the new server at the normal URL (http://confluence.sakaiproject.org).   Once a space is made available on the new server it will be ready for use and back in read-write mode. 

If you have any questions, please let me know.


> -----Original Message-----
> From: Knoop, Peter
> Sent: Monday, June 22, 2009 9:27 AM
> Subject: Sakai Jira and Confluence Migration: 29 June 2009, Monday,
> 8:00AM Eastern US Time
> Next Monday, June 29th, the Sakai Jira and Confluence servers will be
> migrated to a new hosting service, wush.net.  It is unfortunate that we
> have to do this in the middle of the week, however, schedules and
> resources could not be aligned otherwise.  Please join me in thanking
> the University of California, Berkeley, for hosting these services for
> the community for the past year, and their assistance with this
> migration.
> Jira and Confluence will both be taken off-line for the move at 8:00AM
> Eastern US Time (other time-zones: http://tinyurl.com/kr8eun).  By
> 5:00PM Eastern US time, or earlier, Jira should again be available on
> the new server.  Confluence will become available as well, however, it
> will not have any content initially.  The process of migrating
> Confluence content is slow and involves a number of manual steps.  It
> is likely to take several days to complete based on our dry run a
> couple months ago.  (Any clean-up anyone wants to do in Confluence in
> the meantime will help accelerate this process!)  We will be moving the
> most-popular Confluence content first.  We maybe able to provide read-
> only access to some confluence content while it is in the migration
> queue.  Following the migration, we anticipate upgrading Jira and
> Confluence to their latest released versions in the near future.
> If you have any questions, please let me know.
> -peter
> Sakai Project Coordinator

More information about the production mailing list