kudu-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Percy <mpe...@apache.org>
Subject Re: Migrating Kudu JIRA to the ASF
Date Tue, 23 Feb 2016 23:18:38 GMT
Update: I've exported all Kudu issues from issues.cloudera.org and have
given a JSON dump to ASF infra for import into issues.apache.org. The
import is scheduled to happen today, so I've marked the Kudu project on
issues.cloudera.org READ ONLY so that we don't lose any edits in the
migration. Users without special privileges (that's most users) will not be
able to make any changes to Kudu JIRA at this time (committers, please
don't make any edits).

Sorry for any inconvenience this migration might cause. I'll send out an
email when it is complete.


On Mon, Feb 22, 2016 at 10:52 AM, Mike Percy <mpercy@apache.org> wrote:

> Hi all,
> Over the last few weeks I've been working with Apache infra to come up
> with a procedure to migrate our current JIRA instance over to Apache. We've
> done a bunch of testing and now have a date for the final migration. We'll
> be performing the migration on Tuesday, Feb 23, at 12:30pm PST. About an
> hour prior to that, I'll export a JIRA dump from the existing JIRA and run
> the scripts to prepare it for import into another JIRA instance. As soon as
> that export is done, I'll set the current JIRA [1] to read-only and we'll
> begin the import process. This may take an hour or two to complete. Once
> this is done, I'll send out a new email pointing to the new JIRA [2] and
> letting folks know that the process is complete.
> Please let me know if you have any concerns and thank you for your
> patience during the migration process.
> Mike
> [1] Current Kudu JIRA instance: https://issues.cloudera.org/browse/KUDU
> [2] ASF Kudu JIRA instance: https://issues.apache.org/jira/browse/KUDU
> (note: this instance will only contain a few test issues until after the
> migration is complete)

View raw message