[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Migrating Subversion issues to ...

From: Ivan Zhakov <ivan_at_visualsvn.com>
Date: Fri, 18 Sep 2015 15:47:06 +0200

On 18 September 2015 at 14:37, Ivan Zhakov <ivan_at_visualsvn.com> wrote:
> On 16 September 2015 at 14:44, Ivan Zhakov <ivan_at_visualsvn.com> wrote:
>> On 15 September 2015 at 22:20, Ivan Zhakov <ivan_at_visualsvn.com> wrote:
>>> On 15 September 2015 at 20:02, Greg Stein <gstein_at_gmail.com> wrote:
>>>> You can do it. File an INFRA ticket for porting our issues into JIRA, and
>>>> note that you have some content for a test load. They do test loads often
>>>> for incoming, so they have a runbook for that.
>>>> (and post the INFRA ticket here, so others can Watch the ticket if they
>>>> like)
>>> Done:
>>> https://issues.apache.org/jira/browse/INFRA-10439
>> Just to keep everyone updated: ASF Infra team performed first test
>> migration for us:
>> https://issues.apache.org/jira/browse/SVN
> Status update:
>> Please report me any problems or suggestions. Current TODO list:
>> - Migrate attachments [IN PROGRESS]
> Some attachments was successfully migrated, but some didn't. I
> provided probably fixed import data to INFRA team and waiting for fix
> round of test migration.
Attachments was successfully migrated after multiple attempts and help
from ASF Infra team. This how Subversion issue tracker will look like:

I'm ready to perform final migration, but I think we should make issue
tracker on tigris.org read only. It also would nice finalize tigris ->
asf user name mappings, at least for most referenced users.

Ivan Zhakov
Received on 2015-09-18 15:47:39 CEST

This is an archived mail posted to the Subversion Dev mailing list.