mocobeta opened a new pull request, #65:
URL: https://github.com/apache/lucene-jira-archive/pull/65
Close #63.
- Capture `[~username]` mentions as well as `@username` mentions.
- Show full name if a github account is not available for the Jira username.
e.g.,
![Screens
mocobeta opened a new issue, #66:
URL: https://github.com/apache/lucene-jira-archive/issues/66
During migration, some issues could receive additional comments.
These comments would be able to detect by their timestamp and migrated to
the corresponding GitHub issue afterward.
--
This is
mocobeta commented on PR #65:
URL:
https://github.com/apache/lucene-jira-archive/pull/65#issuecomment-1193086487
I'd merge this now - I need this for #66.
--
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
mocobeta merged PR #65:
URL: https://github.com/apache/lucene-jira-archive/pull/65
--
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
mocobeta closed issue #63: Jira username mentions are not converted?
URL: https://github.com/apache/lucene-jira-archive/issues/63
--
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.
mocobeta opened a new pull request, #67:
URL: https://github.com/apache/lucene-jira-archive/pull/67
Close #66
This will be performed after the main migration is completed.
- extracts Jira comments created after a specific timestamp (i.e. the point
at the latest Jira snapshot i
mocobeta commented on PR #67:
URL:
https://github.com/apache/lucene-jira-archive/pull/67#issuecomment-1193094082
Tested with the latest comments on LUCENE-10557.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
mocobeta merged PR #67:
URL: https://github.com/apache/lucene-jira-archive/pull/67
--
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
mocobeta closed issue #66: Handle new comments on existing Jira issues during
migration
URL: https://github.com/apache/lucene-jira-archive/issues/66
--
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 t
mikemccand commented on PR #65:
URL:
https://github.com/apache/lucene-jira-archive/pull/65#issuecomment-1193096003
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 s
mikemccand commented on issue #62:
URL:
https://github.com/apache/lucene-jira-archive/issues/62#issuecomment-1193097287
Oh! I see what happened here: the closing `)` was accidentally included as
part of the URL. I have often wondered how auto-hyperlinking handles this --
how does it know
mikemccand closed issue #62: Missing closing paren in conversion
URL: https://github.com/apache/lucene-jira-archive/issues/62
--
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
mikemccand commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193100921
OK I wrote a simple tool to aggregate all labels from my (nearly complete)
jira dump:
```
import os
import glob
import json
with_label_count = 0
labe
mikemccand commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193100969
Maybe we could import them under a `legacy-jira-label:XXX` to make it clear?
--
This is an automated message from the Apache Git Service.
To respond to the message, plea
mocobeta commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193104522
> Maybe we could import them under a `legacy-jira-label:XXX` to make it
clear?
I'm fine with this but it seems there are many labels that do not really
make much sen
mikemccand commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193106221
Sorry, I still feel we should not be the judges/arbiters of history here.
Our goal is to faithfully migrate and not pass personal judgement on what
should make the
mocobeta opened a new pull request, #68:
URL: https://github.com/apache/lucene-jira-archive/pull/68
#61
Port `Labels` as `legacy-jira-labels:xxx`.
e.g. `newdev` is preserved as `legacy-jira-labels:newdev`
![Screenshot from 2022-07-23
20-07-11](https://user-images.githubuser
mocobeta commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193108108
> Have we done such judgement on other Jira metadata? I.e. are there cases
where we could have migrated XYZ from labels (Jira export gave it to us, GitHub
import would acce
mocobeta commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193110759
Just to note, GitHub's search feature also search labels as well as issue
title and body with "partial match". I think we need to be a bit careful about
what labels we add
mocobeta opened a new pull request, #69:
URL: https://github.com/apache/lucene-jira-archive/pull/69
Noticed there is an optional or custom metadata field "Environment" in Jira.
This is not shown in the default view, but reporters can add arbitrary texts
(which can be very long) in the field
mocobeta commented on PR #69:
URL:
https://github.com/apache/lucene-jira-archive/pull/69#issuecomment-1193124873
I think this is important and should be ported to GitHub.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and us
mocobeta merged PR #69:
URL: https://github.com/apache/lucene-jira-archive/pull/69
--
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 issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193133017
> Just to note, GitHub's search feature also search labels as well as issue
title and body in "partial match" (I do not know what they do though, I imagine
GitHub tokeniz
mikemccand commented on PR #69:
URL:
https://github.com/apache/lucene-jira-archive/pull/69#issuecomment-1193133256
+1 thanks @mocobeta! What other custom fields does Lucene have?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitH
gsmiller merged PR #1044:
URL: https://github.com/apache/lucene/pull/1044
--
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...@lucene.apac
[
https://issues.apache.org/jira/browse/LUCENE-10659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Miller resolved LUCENE-10659.
--
Resolution: Fixed
> Fix random TestDisiPriorityQueue bug
> --
[
https://issues.apache.org/jira/browse/LUCENE-10659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570315#comment-17570315
]
Greg Miller commented on LUCENE-10659:
--
Patched this additional fix in as well. Ho
mikemccand opened a new issue, #70:
URL: https://github.com/apache/lucene-jira-archive/issues/70
I'm not sure what happened here but if you look a [this converted
issue](https://github.com/mikemccand/stargazers-migration-test/issues/959), the
\`MergePolicy.findFullFlushMerges\` somehow did
mocobeta merged PR #68:
URL: https://github.com/apache/lucene-jira-archive/pull/68
--
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
mocobeta commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193231561
I merged #68
--
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 co
mocobeta commented on issue #70:
URL:
https://github.com/apache/lucene-jira-archive/issues/70#issuecomment-1193234407
`{{X}}` is correctly converted to backticks here. The problem is that the
original text in Jira data includes escaping character `\\` before `{{X}}` for
some reason, and th
tang donghai created LUCENE-10660:
-
Summary: precompute the max level in LogMergePolicy
Key: LUCENE-10660
URL: https://issues.apache.org/jira/browse/LUCENE-10660
Project: Lucene - Core
Issue
tang-hi opened a new pull request, #1045:
URL: https://github.com/apache/lucene/pull/1045
### Description (or a Jira issue link if you have one)
[jira](https://issues.apache.org/jira/browse/LUCENE-10660)
--
This is an automated message from the Apache Git Service.
To respond to the mess
[
https://issues.apache.org/jira/browse/LUCENE-10480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570417#comment-17570417
]
Zach Chen commented on LUCENE-10480:
>From the latest nightly benchmark result, the
34 matches
Mail list logo
