> This one https://github.com/mocobeta/forks-migration-test-2/issues/8964
> seems to be missing its attachment - not sure if this was expected
> with this round? EG
Yes, I need to explain it.
Currently, all attachments are disappeared since I just moved all
attachments to another branch
Yes, looks amazing! All I could find was:
This one https://github.com/mocobeta/forks-migration-test-2/issues/8964
seems to be missing its attachment - not sure if this was expected
with this round? EG
Hi Tomoko,
this looks all great! Go ahead and thanks for taking care. I will follow
the INFRA issue during my vacation.
Uwe
Am 08.08.2022 um 17:42 schrieb Tomoko Uchida:
Hi,
this is the latest iteration of the migrations test.
https://github.com/mocobeta/forks-migration-test-2/issues
I
> Or did we make that improvement after you generated this latest version
maybe?
Yes. The latest walk-through test was done three days ago before this was
merged.
https://github.com/apache/lucene-jira-archive/pull/128 (2 days ago)
Tomoko
2022年8月9日(火) 2:49 Michael McCandless :
> Hi Tomoko,
>
>
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,
I looked at a few issues and they look absolutely fabulous. What a great
achievement, Tomoko!
Dawid
On Mon, Aug 8, 2022 at 5:43 PM Tomoko Uchida
wrote:
> Hi,
> this is the latest iteration of the migrations test.
> https://github.com/mocobeta/forks-migration-test-2/issues
>
> I fixed a few
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
On Sat, Jul 30, 2022 at 8:47 PM Tomoko Uchida
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
> 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
Is it intentional that we do not set Assignees on migration?
E.g. this issue (
https://github.com/mocobeta/forks-migration-test/issues/5916) is assigned
to Ryan in Jira, but has no Assignees in GitHub issue.
Mike
On Sat, Jul 30, 2022 at 6:40 PM Michael McCandless <
luc...@mikemccandless.com>
On Sat, Jul 30, 2022 at 6:29 PM Michael McCandless <
luc...@mikemccandless.com> wrote:
How about hidden (secure) issues? I assume they did not migrate as well?
> Do GitHub issues offer such hidden/secure issues?
>
OK nevermind -- Tomoko already raised this question here on June 15 and the
Oh that's a good point!
How about hidden (secure) issues? I assume they did not migrate as well?
Do GitHub issues offer such hidden/secure issues?
Mike
On Sat, Jul 30, 2022 at 6:20 PM Michael Sokolov wrote:
> Oh I noticed one other thing. I was checking
>
Oh I noticed one other thing. I was checking
https://github.com/mocobeta/forks-migration-test/issues/10005 which is
the copy of https://issues.apache.org/jira/browse/LUCENE-10054, the
issue that has been receiving a lot of spam comments lately. Lo and
behold - the spam is gone! I am guessing it
Oh, Tomoko already made this change, at Dawid's suggestion, but after she
had generated this test set of issues. Great minds think alike! (You and
Dawid).
I think she also fixed a few conversion bugs as well.
It takes at least ~24 hours to re-generate the full issues export so I
think she
I did some spot-checking. ooh, it looks so nice!
I have one suggestion, totally optional/cosmetic, but I wonder if we
could make the original comment authors' names more prominent by
moving the [Legacy Jira: ${Name} (@${user}) on ${date}] to the top of
each comment rather than the bottom? That
Hi Team,
Thanks to Tomoko's amazing hard work, we are close to done with the tooling
to migrate Jira issues to GitHub issues.
But we need your help!!
Please spot-check the trial migrated issues here:
https://github.com/mocobeta/forks-migration-test/issues
Ever Jira issue and its comments as of
16 matches
Mail list logo
