incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raphael Bircher <>
Subject Re: migration stuff, wiki page
Date Fri, 24 Jun 2011 14:23:15 GMT
Am 24.06.11 16:07, schrieb Rob Weir:
> I think the plan happens on several levels.
> At one level it is the survey of existing OOo website resources, how
> active they are, what licenses they are covered by, what formats they
> are in.  That is the survey level.
> Then we need a proposal for how those resources map into the Apache
> infrastructure.  This could be high level, like Hg ->  SVN, Bugzilla ->
> Bugzilla, etc.
> Then we need an execution plan.  This is going to require the
> coordination of Apache volunteers, Apache
> Infrastructure, volunteers from the legacy OpenOffice website and
> Oracle IT personal.  We want to transfer the soup without spilling it.
> A top level decision will be whether we do this incrementally, system,
> by system, or whether we need to do a "big bang" migration.
> For example, an incremental approach might say that we migrate over
> the defect tracker in one week:
> 0) Back up existing bug tracking database.
> 1) Project volunteer does trial migration on their own server, to
> verify that the process can go smoothly. Make the instance available
> to the Apache project for testing/verification.  Document the steps
> needed, any special settings, workarounds, required patches, etc.
> Iterate until the test migration works reliably.
> 2) Agree on a date to do the real migration.  At that time, kock the
> defect tracker in the legacy OOo site to prevent updates.  Put notice
> on that site that we are in the process of migrating.
> 3) Working with Apache Infrastructure, do the real migration, using
> any special instructions documented in step 1.  Keep the Apache
> instance of the defect tracker read-only except for project members,
> until we've tested and verified that it is working properly,
> 4) Once we've agreed that the new instance is working correctly, get
> the admin of the legacy OOo website to do a redirect of requests to
> the legacy OOo defect tracker to the Apache instance.
> 5) Enable public access to Apache instance
> 6) Pray.
I agree with that but I don't understand what's the difference between 
"site transition" and "Site PPMC Plan"

Is Site PPMC Plan for organisation? "Site transiting" sounds like al the 
technical stuff we need for the migration.

Greetings Raphael

My private Homepage:

View raw message