You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by GitBox <gi...@apache.org> on 2022/08/01 10:12:57 UTC
[GitHub] [lucene-jira-archive] mikemccand opened a new issue, #104: Should we regenerate another full export?
mikemccand opened a new issue, #104:
URL: https://github.com/apache/lucene-jira-archive/issues/104
I know this is a hassle and adds delay, but, we have fixed a number of issues since the last full test export.
And e.g. @msokolov's first comment on this current iteration is just such an example.
If we take another iteration we can bring fresh eyes on the latest changes?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #104: Should we regenerate another full export?
Posted by GitBox <gi...@apache.org>.
mocobeta commented on issue #104:
URL: https://github.com/apache/lucene-jira-archive/issues/104#issuecomment-1206028981
All issues were successfully imported to https://github.com/mocobeta/forks-migration-test-2/issues with the latest main.
Issue link remapping is ongoing.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #104: Should we regenerate another full export?
Posted by GitBox <gi...@apache.org>.
mocobeta commented on issue #104:
URL: https://github.com/apache/lucene-jira-archive/issues/104#issuecomment-1213225632
Thank you, please open reports if you notice anything. I think we still have some time for small improvements.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #104: Should we regenerate another full export?
Posted by GitBox <gi...@apache.org>.
mocobeta commented on issue #104:
URL: https://github.com/apache/lucene-jira-archive/issues/104#issuecomment-1207145653
Done.
https://github.com/mocobeta/forks-migration-test-2/issues
Generally it looks fine. I noticed some minor glitches like #109 and #110. I'll address them (if it's easy and safe to fix).
I think we can open an INFRA issue for the migration next week.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-jira-archive] mikemccand commented on issue #104: Should we regenerate another full export?
Posted by GitBox <gi...@apache.org>.
mikemccand commented on issue #104:
URL: https://github.com/apache/lucene-jira-archive/issues/104#issuecomment-1213220222
+1, let's close this, yay!! Thank you @mocobeta!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-jira-archive] mikemccand closed issue #104: Should we regenerate another full export?
Posted by GitBox <gi...@apache.org>.
mikemccand closed issue #104: Should we regenerate another full export?
URL: https://github.com/apache/lucene-jira-archive/issues/104
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #104: Should we regenerate another full export?
Posted by GitBox <gi...@apache.org>.
mocobeta commented on issue #104:
URL: https://github.com/apache/lucene-jira-archive/issues/104#issuecomment-1207167409
Before opening INFRA issues, I'll try to address issues I found in the latest migration test and run another full import.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #104: Should we regenerate another full export?
Posted by GitBox <gi...@apache.org>.
mocobeta commented on issue #104:
URL: https://github.com/apache/lucene-jira-archive/issues/104#issuecomment-1201026632
Yes - I plan another full import. I don't think we need to walk through the complete migration steps written in #7 again, but at least we can pick the most critical parts - conversion and import.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-jira-archive] mikemccand commented on issue #104: Should we regenerate another full export?
Posted by GitBox <gi...@apache.org>.
mikemccand commented on issue #104:
URL: https://github.com/apache/lucene-jira-archive/issues/104#issuecomment-1207194850
Thanks @mocobeta.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #104: Should we regenerate another full export?
Posted by GitBox <gi...@apache.org>.
mocobeta commented on issue #104:
URL: https://github.com/apache/lucene-jira-archive/issues/104#issuecomment-1212671024
Hi, here is the latest migration result. All recent improvements (e.g., #128, #131, #136, etc.) are applied.
https://github.com/mocobeta/forks-migration-test-3/issues
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org
[GitHub] [lucene-jira-archive] mocobeta commented on issue #104: Should we regenerate another full export?
Posted by GitBox <gi...@apache.org>.
mocobeta commented on issue #104:
URL: https://github.com/apache/lucene-jira-archive/issues/104#issuecomment-1213212384
I checked several issues from new to old. I see no degradations from the previous one.
If you are okay with that, the actual migration will be the same as this except for the issue reporter and assignees (the issue reporter should be an ASF bot account and assignees should be correctly set).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org