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 <msoko...@gmail.com> wrote: > 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 did not get transferred > because the spam comments are all locked so they are visible only to > logged-in JIRA users. It seems possible we might have other comments > like that which we *would* want to transfer? I'm not sure how to > search for something like that though. Personally, I don't know of any > issues like that (except this SPAM!), so I'd be happy if we don't > change anything here :) > > On Sat, Jul 30, 2022 at 6:12 PM Michael Sokolov <msoko...@gmail.com> > wrote: > > > > 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 would make it a little less > > jarring perhaps to see all (legacy) comments authored by mocobeta? If > > it's too late for such tweaking, I completely understand - do with it > > what you will. > > > > Thank you Tomoko (and Mike) for all your hard work on this; I think > > it's going to be a nice improvement. > > > > On Sat, Jul 30, 2022 at 11:56 AM Michael McCandless > > <luc...@mikemccandless.com> wrote: > > > > > > 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 a couple days ago should be > there. > > > > > > Compare each GitHub issue to its corresponding Jira issue and if you > see something wrong, please reply on this thread, or open an issue here: > > > https://github.com/apache/lucene-jira-archive > > > > > > Tomoko plans around one week for this spot-checking, and then she will > open INFRA issues to do the actual migration and then switch Jira to > read-only. > > > > > > Thank you Tomoko!!! I have never seen such an unrelenting solo sprint > for so long and making such incredible progress on so many tricky problems. > > > > > > Mike > > > -- > > > Mike McCandless > > > > > > http://blog.mikemccandless.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > > -- Mike McCandless http://blog.mikemccandless.com
