Thanks Mark and everybody else involved! I do prefer this approach than the stepped transition that was planned previously. Here we know what we got and people don't have to spend time finishing the migration in the background.
It does look sane: attachments are still there, which is the main thing I am interested in. Just for curiosity, I checked an issue referred from the LO "first week development summary", Bug 100686: the patch is there in our bugzilla, so we can pick up relatively easily in some of those changes without diverging too much :). cheers, Pedro. --- On Thu, 8/25/11, Mark Thomas <ma...@apache.org> wrote: ... > All, > > The OOo Bugzilla data export provided to the ASF > infrastructure team has > been imported into a test instance[1] for your review. > > Please review the import and report any *show stopper* > issues to the > infrastructure team via the Jira ticket created for this > import. [2] > > Assuming no show stopper issues, the data will be > re-imported no sooner > that Monday 29 August 2011. > > Please note the following: > > 1. None of the OOo UI customisations were provided with the > export so > the UI is the same as the main ASF bugzilla instance apart > from the name > which has been changed to "Apache ooo Bugzilla" > > 2. The previous OOo Bugzilla instance was running on > Bugzilla 3.2.10. > This reached end-of-live over 6 months ago. It is not > acceptable to run > production services on unsupported software. As part of the > migration, > the bugzilla instance was upgraded to 4.0.0. > > 3. All usernames and passwords remain unchanged with one > exception: > users with system administration rights have been removed > from the admin > group. Access to this group will be limited to members of > the ASF > infrastructure team (new volunteers always welcome). > > Enjoy. > > Mark > > > [1] https://issues.apache.org/ooo/ > [2] https://issues.apache.org/jira/browse/INFRA-3884 > >
