Hi Tomoko,
I had thought that we improved the "Legacy Jira: by..." wording, but I
still see e.g.:]
[Legacy Jira: by Steven Rowe (@sarowe) on Apr 26 2013]
Or did we make that improvement after you generated this latest version
maybe?
Mike McCandless
http://blog.mikemccandless.com
On Mon, Aug 8, 2022 at 11:43 AM Tomoko Uchida <tomoko.uchida.1...@gmail.com>
wrote:
> Hi,
> this is the latest iteration of the migrations test.
> https://github.com/mocobeta/forks-migration-test-2/issues
>
> I fixed a few conversion errors I noticed on that, but there should remain
> glitches that are relatively easy to fix I didn't notice.
> Please pick one or two of your memorial issues and if they are correctly
> converted into Markdown (i.e. can be used as references for future usage)
> when you have some time.
>
> We cannot iterate the time-consuming test forever. I plan to run the final
> iteration this week.
>
> Tomoko
>
>
> 2022年7月31日(日) 18:21 Michael McCandless <luc...@mikemccandless.com>:
>
>> On Sat, Jul 30, 2022 at 8:47 PM Tomoko Uchida <
>> tomoko.uchida.1...@gmail.com> wrote:
>>
>> > Is it intentional that we do not set Assignees on migration?
>>>
>>> You can assign a GitHub account only when it has push access to the
>>> repository; it was infeasible to give push access to all committers to the
>>> test repo (an invite/accept flow is needed for each committer).
>>> Assignees will be set when the actual migration on apache/lucene repo -
>>> every assignee in Jira should have push access to it.
>>>
>>
>> Woops OK thanks Tomoko! I think you explained this already at least two
>> times now, sorry ;)
>>
>> Mike McCandless
>>
>> http://blog.mikemccandless.com
>>>
>>>
