The notifications are now sent to issues@ list. Still, it could be noisy to
have them in there for many of you, we could not set a fake mail address to
completely silence the notification.
You might want to set a mail filter to screen out the notifications from
the migration repository.
Thanks.
I set https://github.com/apache/lucene-jira-archive/blob/main/.asf.yaml to
send all notifications to my ASF address, but this did not help...
2022年6月29日(水) 19:24 Tomoko Uchida :
> Sorry, it seems the all updates in
> https://github.com/apache/lucene-jira-archive are noticed in dev@ list.
> I
mocobeta commented on issue #1:
URL:
https://github.com/apache/lucene-jira-archive/issues/1#issuecomment-1169860211
Thanks for reporting.
I found Jira's number list (`#`) is not correctly converted and it is
interpreted as headers in Markdown.
Jira dump
```
"body":
Sorry, it seems the all updates in
https://github.com/apache/lucene-jira-archive are noticed in dev@ list.
I don't see the configuration/setting for the repository. Could anyone mute
this?
Tomoko
2022年6月29日(水) 19:06 GitBox :
>
> mocobeta opened a new issue, #1:
> URL:
mocobeta opened a new issue, #3:
URL: https://github.com/apache/lucene-jira-archive/issues/3
To correctly map Jira user ids in issues (reporter/assignee/author) to
GitHub account, we need an account mapping file.
This could be inferred from https://github.com/orgs/apache/people?
--
mocobeta opened a new issue, #2:
URL: https://github.com/apache/lucene-jira-archive/issues/2
All attachments should be archived in `attachments/`. They will be referred
from the migrated issues in https://github.com/apache/lucene.
For files with the same names, we keep the latest
dweiss commented on issue #1:
URL:
https://github.com/apache/lucene-jira-archive/issues/1#issuecomment-1169793482
This is what the bold block-issue looks like.
--
This is
mocobeta opened a new issue, #1:
URL: https://github.com/apache/lucene-jira-archive/issues/1
There are various errors in converting Jira markup to Markdown.
For example:
- tables are broken
- bullet lists converted to bold blocks (?)
- bullet lists include unnecessary spaces
I looked at the first random issue and noticed these (perhaps known) issues -
https://github.com/mocobeta/sandbox-lucene-10557/issues/10838
1) lists are converted into bold blocks (without the list):
https://github.com/mocobeta/sandbox-lucene-10557/issues/10838#issuecomment-1166777318
2) inline
I think it's a matter of tradeoff. For example when you do faceting then we
require complete evaluation, and since this field-matching is a kind of
aggregation I think it's OK if that's how it works. Users can choose which
technique they want to apply based on their usecase.
Anyway I don't think
10 matches
Mail list logo
