We'll have to fix those integrations individually (they will all break, initially). For example, I don't have admin rights on Gerrit, and I'm not sure how to configure that integration. Although I have administrator rights for the Kudu project on ASF JIRA, I don't have administrator rights for the ASF JIRA as a whole. So I think that means I don't have rights to set up triggers for integrations with things like Slack, so if we want that we'll have to file INFRA tickets for it.
Mike On Mon, Feb 22, 2016 at 7:18 PM, Jean-Daniel Cryans <[email protected]> wrote: > Thanks for handling this migration, Mike! > > Are you fixing the integrations with Jira at the same or will we do this > after? For example, gerrit reviews ( > http://gerrit.cloudera.org:8080/#/c/978/) > currently point to issues.cloudera.org when it detects a Jira number. > > Thanks, > > J-D > > On Mon, Feb 22, 2016 at 12:52 AM, Mike Percy <[email protected]> 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) > > >
