I suggest not migrating the list but restarting the list from scratch. If an old issue is important or critical it will find its way to the new list.
On Jan 24, 2012 10:37 AM, "Robert Cimrman" <cimr...@ntc.zcu.cz> wrote:
>
> I have found another script, that, after some tweaking, does the job. Now should I migrate all issues (and close the fixed ones manually), or only the open ones? I am slightly in favor of the former option, to have a complete list at one place.
>
> r.
>
>
> On 01/20/12 16:36, Robert Cimrman wrote:
>>
>> Hi,
>>
>> does anyone lurking here have any experience with respect to migrating issues
>> from [1] to [2]? I have found some scripts for the task [3], [4], but they warn
>> about their alpha-status, so I would like to hear some success stories before
>> trying them for real...
>>
>> r.
>>
>> [1] http://code.google.com/p/sfepy/issues/list
>> [2] https://github.com/sfepy/sfepy/issues?sort=created
>> [3] https://github.com/dave0/gcode-issue-import
>> [4] https://github.com/arthur-debert/google-code-issues-migrator
>>
>
> --
> You received this message because you are subscribed to the Google Groups "sfepy-devel" group.
> To post to this group, send email to sfepy...@googlegroups.com.
> To unsubscribe from this group, send email to sfepy-devel...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/sfepy-devel?hl=en.
>