mikemccand commented on issue #15:
URL:
https://github.com/apache/lucene-jira-archive/issues/15#issuecomment-1179701515
We should also make Jira effectively read-only by editing the workflow for
our project to disable any actual changes. @rmuir had suggested this is
possible and indeed so
mikemccand commented on issue #7:
URL:
https://github.com/apache/lucene-jira-archive/issues/7#issuecomment-1179701707
> Sure, I agree this can be postponed - I just wanted to signal that it'd be
a nice thing to have. We wouldn't be able to do it anyway - I think it'd have
to be a request t
mikemccand commented on issue #7:
URL:
https://github.com/apache/lucene-jira-archive/issues/7#issuecomment-1179702122
Could we separate step 2) into:
```
2a) Announce X days in advance that on Y date, Jira will go read-only and we
will migrate to GitHub issues, taking estimated Z
mikemccand commented on issue #15:
URL:
https://github.com/apache/lucene-jira-archive/issues/15#issuecomment-1179702708
I have not tested this, but as of Jira 5.0 (I think we are running 5.x at
Apache), we could use the [Jira REST
API](https://developer.atlassian.com/server/jira/platform/u
mocobeta commented on issue #15:
URL:
https://github.com/apache/lucene-jira-archive/issues/15#issuecomment-1179704284
> We should also make Jira effectively read-only by editing the workflow for
our project to disable any actual changes. @rmuir had suggested this is
possible and indeed som
mikemccand commented on issue #12:
URL:
https://github.com/apache/lucene-jira-archive/issues/12#issuecomment-1179704669
> *
[LUCENE-2230](https://github.com/mocobeta/sandbox-lucene-10557/issues/2472) -
won't fix, maybe not a big problem
Hi @mocobeta -- I couldn't understand what wen
mocobeta commented on issue #7:
URL:
https://github.com/apache/lucene-jira-archive/issues/7#issuecomment-1179704932
> 2b) On Y date, send email saying migration will start shortly, reminding
that Jira will be read-only for the duration.
> 2c) Then, make Jira read-only ([this seems like a
mocobeta commented on issue #12:
URL:
https://github.com/apache/lucene-jira-archive/issues/12#issuecomment-1179706447
> Hi @mocobeta -- I couldn't understand what went wrong in this issue?
I meant this comment. This should be plain text, not interpreted as headers.
.
This is a lower priority task, and should not block the migration.
mikemccand commented on issue #7:
URL:
https://github.com/apache/lucene-jira-archive/issues/7#issuecomment-1179715650
> I would love if these old URLs could simply redirect to github, unless a
special token is passed ("noredirect") was used in the URL - this is what
spring folks did.
mikemccand commented on issue #7:
URL:
https://github.com/apache/lucene-jira-archive/issues/7#issuecomment-1179716082
> I really don't want to say this but - just to be clear, I'm working on
this migration project as an individual without support/returns from any
organizations.
I to
mikemccand opened a new issue, #29:
URL: https://github.com/apache/lucene-jira-archive/issues/29
I think it is crazy trappy to leave Jira as writable after "switching" to
GitHub issues. New users, people seeing old emails in archives and clicking on
Jira links, old links in our Wiki/blog p
mikemccand commented on issue #7:
URL:
https://github.com/apache/lucene-jira-archive/issues/7#issuecomment-1179717138
> As for "making JIra read-only", can you please explicitly gain consensus
among devs in dev@ list, as I wrote in #15?
I opened #29 to make progress on this.
--
Th
mikemccand commented on issue #29:
URL:
https://github.com/apache/lucene-jira-archive/issues/29#issuecomment-1179717361
This [Atlassian JIra documentation looks like a great
start](https://confluence.atlassian.com/jirakb/how-to-make-jira-issues-read-only-using-workflow-properties-1063568771
mikemccand commented on issue #12:
URL:
https://github.com/apache/lucene-jira-archive/issues/12#issuecomment-1179718268
> I don't think unintentional markdowns will be properly rendered after
migration. Markdowns in Jira are (correctly) escaped in the converter.
Oh, I though the orig
mikemccand commented on issue #27:
URL:
https://github.com/apache/lucene-jira-archive/issues/27#issuecomment-1179719901
> ... but I'm have some trouble finding where this text is generated in the
Jira export / GitHub import source code...
[Found
it](https://github.com/apache/lucene-
mocobeta commented on issue #7:
URL:
https://github.com/apache/lucene-jira-archive/issues/7#issuecomment-1179720010
> For step 9, maybe we can ask/plan for volunteers in the dev community to
help check for anything that went wrong during the import process. We of course
should test as much
mocobeta commented on issue #12:
URL:
https://github.com/apache/lucene-jira-archive/issues/12#issuecomment-1179721279
> I sort of think this is a feature not a bug? But, it is not a priority to
handle these mixed cases well! If the converter is escaping some and missing
others I think we c
mikemccand opened a new pull request, #30:
URL: https://github.com/apache/lucene-jira-archive/pull/30
Thank you @mocobeta for the awesome `README` instructions! I was able to
migrate my own few Jira issues to [my test GitHub
repo](https://github.com/mikemccand/stargazers-migration-test/iss
mikemccand commented on code in PR #30:
URL: https://github.com/apache/lucene-jira-archive/pull/30#discussion_r917400656
##
migration/README.md:
##
@@ -54,14 +56,14 @@ LUCENE-10502
...
```
-Downloaded attachments should be committed to a dedicated repo/branch for them.
+Down
mocobeta commented on PR #30:
URL:
https://github.com/apache/lucene-jira-archive/pull/30#issuecomment-1179738207
Thank you @mikemccand for improving this, will merge this soon.
As for attachments, I have already committed all attachments for all issues
(from a snapshot) in this repo - pl
mocobeta merged PR #30:
URL: https://github.com/apache/lucene-jira-archive/pull/30
--
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-unsubscr...@lu
mikemccand commented on PR #30:
URL:
https://github.com/apache/lucene-jira-archive/pull/30#issuecomment-1179740996
> As for attachments, I have already committed all attachments for all
issues (from a snapshot) in this repo - please use them for testing.
Ahh yes thank you!
--
This
Vigya Sharma created LUCENE-10649:
-
Summary: Failure in
TestDemoParallelLeafReader.testRandomMultipleSchemaGensSameField
Key: LUCENE-10649
URL: https://issues.apache.org/jira/browse/LUCENE-10649
Proje
[
https://issues.apache.org/jira/browse/LUCENE-10649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564711#comment-17564711
]
Vigya Sharma commented on LUCENE-10649:
---
>From initial debugging, it seems that t
[
https://issues.apache.org/jira/browse/LUCENE-10649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564713#comment-17564713
]
Vigya Sharma commented on LUCENE-10649:
---
Could this be related to the merge-on-re
vigyasharma opened a new pull request, #1014:
URL: https://github.com/apache/lucene/pull/1014
This PR is based on the discussion in #738
([comment](https://github.com/apache/lucene/pull/738#issuecomment-1156523966)]..
`RateLimitedIndexOutput.writeBytes()` does not pause while writin
vigyasharma commented on PR #738:
URL: https://github.com/apache/lucene/pull/738#issuecomment-1179856740
Created #1014 to add the comment. Closing this PR now.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL ab
vigyasharma closed pull request #738: LUCENE-10448: Avoid instant rate write
bursts by writing bytes buffer in chunks
URL: https://github.com/apache/lucene/pull/738
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
[
https://issues.apache.org/jira/browse/LUCENE-10448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564743#comment-17564743
]
Vigya Sharma commented on LUCENE-10448:
---
Created PR - [https://github.com/apache/
[
https://issues.apache.org/jira/browse/LUCENE-10480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17564747#comment-17564747
]
Zach Chen commented on LUCENE-10480:
{quote}I'll see if I can run the original nigh
35 matches
Mail list logo
