mocobeta opened a new issue, #116:
URL: https://github.com/apache/lucene-jira-archive/issues/116
I think it's impossible to address. Just wanted to raise an issue for a
heads-up.
In old issues sometimes bare source code or patches are embedded in issue
descriptions or comments withou
mocobeta closed issue #1: Fix markup conversion error
URL: https://github.com/apache/lucene-jira-archive/issues/1
--
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
mocobeta commented on issue #1:
URL:
https://github.com/apache/lucene-jira-archive/issues/1#issuecomment-1207165658
I'm closing this - known conversion errors will be adderessed in follow-up
issues (if it's possible to fix).
--
This is an automated message from the Apache Git Service.
To
mocobeta closed issue #3: Create mapping on Jira user id -> GitHub account
URL: https://github.com/apache/lucene-jira-archive/issues/3
--
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 com
mocobeta commented on issue #3:
URL:
https://github.com/apache/lucene-jira-archive/issues/3#issuecomment-1207165906
I'm closing this, but we'll accept improvements on mapping until the actual
migration.
--
This is an automated message from the Apache Git Service.
To respond to the messag
mocobeta commented on issue #5:
URL:
https://github.com/apache/lucene-jira-archive/issues/5#issuecomment-1207166132
We confirmed the migration scripts generally work fine. I'm closing this.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log
mocobeta closed issue #5: Prepare complete migration script to GitHub issue
from Jira (best effort)
URL: https://github.com/apache/lucene-jira-archive/issues/5
--
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 commented on issue #12:
URL:
https://github.com/apache/lucene-jira-archive/issues/12#issuecomment-1207166202
I'm closing this.
--
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 specif
mocobeta closed issue #12: Make a test set for improving markup conversion
quality
URL: https://github.com/apache/lucene-jira-archive/issues/12
--
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 sp
mocobeta commented on issue #91:
URL:
https://github.com/apache/lucene-jira-archive/issues/91#issuecomment-1207166344
I'd leave this as won't fix.
--
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
mocobeta commented on issue #106:
URL:
https://github.com/apache/lucene-jira-archive/issues/106#issuecomment-1207166962
I'd leave this as "won't fix" - these issues will be manually corrected
afterward with the best effort.
--
This is an automated message from the Apache Git Service.
To
mocobeta commented on issue #96:
URL:
https://github.com/apache/lucene-jira-archive/issues/96#issuecomment-1207167065
Can we close this?
--
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 speci
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 Apach
kaivalnp commented on code in PR #932:
URL: https://github.com/apache/lucene/pull/932#discussion_r939497872
##
lucene/core/src/test/org/apache/lucene/util/hnsw/KnnGraphTester.java:
##
@@ -730,4 +794,61 @@ protected int comparePivot(int j) {
return Float.compare(score[pivo
mocobeta opened a new pull request, #117:
URL: https://github.com/apache/lucene-jira-archive/pull/117
In this description, "LUCENE-10654" should
mocobeta merged PR #117:
URL: https://github.com/apache/lucene-jira-archive/pull/117
--
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...@
mocobeta closed issue #109: Cross-issue link isn't remapped if it appears at
the beggining of a line
URL: https://github.com/apache/lucene-jira-archive/issues/109
--
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
mocobeta opened a new pull request, #118:
URL: https://github.com/apache/lucene-jira-archive/pull/118
I think we shouldn't apply any normalization such as full-width -> halfwidth
but can try to refine the regex.
mocobeta merged PR #119:
URL: https://github.com/apache/lucene-jira-archive/pull/119
--
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...@
mocobeta commented on issue #111:
URL:
https://github.com/apache/lucene-jira-archive/issues/111#issuecomment-1207174492
Fixed in #119
--
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 specifi
mocobeta closed issue #111: Jira mention is not captured if it contains
whitespace
URL: https://github.com/apache/lucene-jira-archive/issues/111
--
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
mocobeta opened a new pull request, #120:
URL: https://github.com/apache/lucene-jira-archive/pull/120
The regex needs to be fixed to properly capture mentions at the end of a
line.
e.g.,
https://github.com/mocobeta/migration-test-3/issues/535
![Screenshot from 2022-08-06
17
mocobeta merged PR #120:
URL: https://github.com/apache/lucene-jira-archive/pull/120
--
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...@
mocobeta closed issue #113: Jira mention is not captured if it appears at the
end of a line.
URL: https://github.com/apache/lucene-jira-archive/issues/113
--
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 g
mocobeta opened a new pull request, #121:
URL: https://github.com/apache/lucene-jira-archive/pull/121
Properly capture mentions that follow `{` or `[`.
https://github.com/mocobeta/migration-test-3/issues/540
![Screenshot from 2022-08-06
18-00-39](https://user-images.githubuserc
mocobeta merged PR #121:
URL: https://github.com/apache/lucene-jira-archive/pull/121
--
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...@
mocobeta closed issue #114: Avoid wrong mentions.
URL: https://github.com/apache/lucene-jira-archive/issues/114
--
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,
vlsi commented on issue #4:
URL:
https://github.com/apache/lucene-jira-archive/issues/4#issuecomment-1207179288
@mocobeta , can you please clarify why you have decided to do two-pass
migration?
Why don't you just import the issues with the proper cross-references in the
first place?
mocobeta commented on issue #4:
URL:
https://github.com/apache/lucene-jira-archive/issues/4#issuecomment-1207182733
We could predict the issue numbers as you pointed out, but we must
prioritize safety. Importing takes 24 hours and if there are short-time GItHub
outages (it's not very uncom
vlsi opened a new issue, #122:
URL: https://github.com/apache/lucene-jira-archive/issues/122
"Legacy Jira: by" does not seem to add much value, however, it makes it
harder to read the comments (see
https://github.com/mocobeta/forks-migration-test-2/issues/10595#issuecomment-1205993910)
vlsi opened a new issue, #123:
URL: https://github.com/apache/lucene-jira-archive/issues/123
See
https://github.com/mocobeta/forks-migration-test-2/issues/1872#issue-1328214873
Does "Legacy" add much value? I do not think so.
Something like "Migrated from
[LUCENE-1879](https://iss
vlsi opened a new issue, #124:
URL: https://github.com/apache/lucene-jira-archive/issues/124
If you consider GitHub issues to be primary, then it probably makes sense to
put GitHub links first, and move JIRA links after GitHub ones for backup
purposes only.
See
https://github.com/mo
vlsi opened a new issue, #125:
URL: https://github.com/apache/lucene-jira-archive/issues/125
See https://gist.github.com/scmx/eca72d44afee0113ceb0349dd54a84a2
The following issue contains lots of "git commit" comments "ASF subversion
and git services", and it makes it absolutely hard
vlsi opened a new issue, #126:
URL: https://github.com/apache/lucene-jira-archive/issues/126
Sample issue:
https://github.com/mocobeta/forks-migration-test-2/issues/10595#issue-1329388218
(https://issues.apache.org/jira/browse/LUCENE-10644)
Please add the `` tag to display images inl
mocobeta commented on issue #4:
URL:
https://github.com/apache/lucene-jira-archive/issues/4#issuecomment-1207185268
There will also be pull requests (we already heavily use it) - @vlsi I'm
just curious if there is a way to correctly determine the issue numbers while
new issues/PRs are arri
vlsi opened a new issue, #127:
URL: https://github.com/apache/lucene-jira-archive/issues/127
See
https://github.com/mocobeta/forks-migration-test-2/issues/10159#issue-1329359180
raw.githubusercontent.com is not supposed to be used at scale, so it is
better to use GitHub pages to avoi
vlsi commented on issue #4:
URL:
https://github.com/apache/lucene-jira-archive/issues/4#issuecomment-1207186354
> There will also be pull requests (we already heavily use it)
Just in case: I'm doing the migration for Apache JMeter (see
https://github.com/vlsi/bugzilla2github).
vlsi commented on issue #4:
URL:
https://github.com/apache/lucene-jira-archive/issues/4#issuecomment-1207186973
> We won't be able to stop new issues/PRs
Do you know GitHub has "Temporary interaction limits"?
I think it should be able to prevent creating issues and PRs during t
mocobeta commented on issue #4:
URL:
https://github.com/apache/lucene-jira-archive/issues/4#issuecomment-1207187514
Thanks for your suggestions.
> I think it should be able to prevent creating issues and PRs during the
import:
Personally, I wish we could temporarily stop all n
mocobeta commented on issue #122:
URL:
https://github.com/apache/lucene-jira-archive/issues/122#issuecomment-1207188679
I'm fine with removing "Legacy Jira" from the header - what do you think
@mikemccand?
--
This is an automated message from the Apache Git Service.
To respond to the me
mikemccand commented on issue #122:
URL:
https://github.com/apache/lucene-jira-archive/issues/122#issuecomment-1207189001
I'm OK with shortening it somehow if we can, but I think the sentiment must
remain -- we need to convey this was a migrated comment to future people who
didn't even kno
mocobeta commented on issue #123:
URL:
https://github.com/apache/lucene-jira-archive/issues/123#issuecomment-1207189029
Relates to #122 - @mikemccand do you have thoughts on it?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
mikemccand commented on issue #123:
URL:
https://github.com/apache/lucene-jira-archive/issues/123#issuecomment-1207189274
Just repeating what I said on #122
I'm OK with shortening it somehow if we can, but I think the sentiment must
remain -- we need to convey this was a migrated co
vlsi commented on issue #122:
URL:
https://github.com/apache/lucene-jira-archive/issues/122#issuecomment-1207189627
> I think the sentiment must remain -- we need to convey this was a migrated
comment to future people
I just thought the comment date (and the fact it would be created
mocobeta commented on issue #125:
URL:
https://github.com/apache/lucene-jira-archive/issues/125#issuecomment-1207189951
Collapsing long texts with `` is a really nice feature, and I often
use it.
But I think we should keep it as-is; we should carry the original Jira
comments without twe
mocobeta commented on issue #122:
URL:
https://github.com/apache/lucene-jira-archive/issues/122#issuecomment-1207190807
> we need to convey this was a migrated comment to future people who didn't
even know we did this issue migration. Maybe "Prior Jira: "? "Migrated Jira: "?
I'm also
vlsi commented on issue #122:
URL:
https://github.com/apache/lucene-jira-archive/issues/122#issuecomment-1207191411
How about changing from
[Legacy Jira: by Yuting Gan (@ Yuti-G) on [Jul 10
2022](https://issues.apache.org/jira/browse/LUCENE-10644?focusedCommentId=17564642&page=com.at
mikemccand commented on issue #4:
URL:
https://github.com/apache/lucene-jira-archive/issues/4#issuecomment-1207192249
> > I think it should be able to prevent creating issues and PRs during the
import:
>
> Personally, I wish we could temporarily stop all new issues/PRs during
migrat
mikemccand commented on issue #122:
URL:
https://github.com/apache/lucene-jira-archive/issues/122#issuecomment-1207192509
> The date is already present in GitHub UI, so duplicating it does not add
much.
+1, I like that. It can just say "migrated from Jira" (no need to say
comment/d
mocobeta commented on issue #124:
URL:
https://github.com/apache/lucene-jira-archive/issues/124#issuecomment-1207192781
Thanks for your suggestion. I considered the implications and effects of
this change.
I'd prefer the current format - "Linked issues" or "Sub-tasks" are not
GitHub
mocobeta commented on issue #4:
URL:
https://github.com/apache/lucene-jira-archive/issues/4#issuecomment-1207193324
Current two-pass migration is carefully considered and safe, and there is no
risk; though I admit it's a bit complicated. I don't think we should change the
two-pass migratio
mikemccand commented on issue #126:
URL:
https://github.com/apache/lucene-jira-archive/issues/126#issuecomment-1207193639
Whoa, I love the color on that inlined patch @vlsi! Does GitHub just
auto-detect a diff/patch inside a ``` block?
If the original Jira commenter/author inlined t
vlsi commented on issue #124:
URL:
https://github.com/apache/lucene-jira-archive/issues/124#issuecomment-1207193708
> Jira issues to GitHub while preserving the original contents as far as
possible
In the new world, you would have GitHub issues only, and new issues would
reference o
mikemccand commented on issue #124:
URL:
https://github.com/apache/lucene-jira-archive/issues/124#issuecomment-1207193836
+1 to make the GItHub link prominent (first link) and then legacy Jira link
after.
I agree we should design this for ease-of-use in a GitHub world.
--
This is
vlsi commented on issue #126:
URL:
https://github.com/apache/lucene-jira-archive/issues/126#issuecomment-1207194067
The markup there "diff language":
Preview of ```BUG_42248.patch```:
```diff
Index: src/core/org/apache/jmeter/gui/GuiPackage.java
==
vlsi commented on issue #126:
URL:
https://github.com/apache/lucene-jira-archive/issues/126#issuecomment-1207194439
> Would we need to load the image and check its size before doing so?
Here's a sample issue with big screenshots:
https://github.com/vlsi/tmp-jmeter-issues/issues/4743
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 sp
mikemccand closed issue #96: Some user references don't convert?
URL: https://github.com/apache/lucene-jira-archive/issues/96
--
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 #96:
URL:
https://github.com/apache/lucene-jira-archive/issues/96#issuecomment-1207194931
Yes, sorry for the delay!
--
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
mikemccand closed issue #106: Inlined patches don't migrate correctly
URL: https://github.com/apache/lucene-jira-archive/issues/106
--
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 commen
mikemccand commented on issue #106:
URL:
https://github.com/apache/lucene-jira-archive/issues/106#issuecomment-1207194996
+1
--
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 commented on issue #106:
URL:
https://github.com/apache/lucene-jira-archive/issues/106#issuecomment-1207195204
@mikemccand sorry, I didn't mean we should close this - I think it'd be
better to keep open (forever) to show what cannot be done in this migration.
--
This is an autom
mocobeta commented on issue #124:
URL:
https://github.com/apache/lucene-jira-archive/issues/124#issuecomment-1207195604
OK, the change would be easy - I'll update the conversion script.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on t
mocobeta commented on issue #122:
URL:
https://github.com/apache/lucene-jira-archive/issues/122#issuecomment-1207195977
OK makes sense to me, I'll change the header like this.
Yuting Gan (@ Yuti-G) ([migrated from
JIRA](https://issues.apache.org/jira/browse/LUCENE-10644?focusedCommen
mocobeta commented on issue #126:
URL:
https://github.com/apache/lucene-jira-archive/issues/126#issuecomment-1207198390
It's really cool to show the patch in the colored diff.
As for images, we have already shown them inline in the comments (without
`alt`).
https://github.com/moco
mocobeta commented on issue #126:
URL:
https://github.com/apache/lucene-jira-archive/issues/126#issuecomment-1207199512
The reason the image in this issue is not shown inline, the author attached
the image but did not create a link to it - I think we cannot determine where
to insert the im
vlsi commented on issue #126:
URL:
https://github.com/apache/lucene-jira-archive/issues/126#issuecomment-1207199987
> I think we cannot determine where to insert the image if the author does
not create the link to it?
If users do not mention the image, then the image should probably
mocobeta commented on issue #126:
URL:
https://github.com/apache/lucene-jira-archive/issues/126#issuecomment-1207200567
> > I think we cannot determine where to insert the image if the author does
not create the link to it?
>
> If users do not mention the image, then the image should
mocobeta commented on issue #127:
URL:
https://github.com/apache/lucene-jira-archive/issues/127#issuecomment-1207201764
Thanks, GitHub pages are actually scalable. I think we need to ask ASF infra
(GitHub pages are per user/organization).
--
This is an automated message from the Apache G
vlsi commented on issue #127:
URL:
https://github.com/apache/lucene-jira-archive/issues/127#issuecomment-1207202628
> I think we need to ask ASF infra
I do not think so.
GitHub pages is a self-service thing. See "GitHub Pages" in
https://cwiki.apache.org/confluence/display/INFRA/
mocobeta commented on issue #127:
URL:
https://github.com/apache/lucene-jira-archive/issues/127#issuecomment-1207203014
> GitHub pages is a self-service thing. See "GitHub Pages" in
https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features
I didn't notice it, thanks
mocobeta opened a new pull request, #128:
URL: https://github.com/apache/lucene-jira-archive/pull/128
Suggested in #122 and #123.
- Remove "Legacy Jira" header from issue description. Instead, add "Migrated
from" before Jira key (link)
- Shorten comment header (remove created and u
mocobeta commented on issue #122:
URL:
https://github.com/apache/lucene-jira-archive/issues/122#issuecomment-1207209281
Addressed in #128.
--
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 spe
mocobeta commented on issue #123:
URL:
https://github.com/apache/lucene-jira-archive/issues/123#issuecomment-1207209332
Addressed in #128.
--
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 spe
mocobeta opened a new issue, #129:
URL: https://github.com/apache/lucene-jira-archive/issues/129
For example, there are cross-issue links such as `SOLR-`, `INFRA-`,
or `LEGAL-`. At least we can/should create links to frequent projects in
Lucene?
--
This is an automated messag
mocobeta opened a new pull request, #130:
URL: https://github.com/apache/lucene-jira-archive/pull/130
Suggested in #124
See https://github.com/mocobeta/migration-test-3/issues/544.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on
mocobeta commented on PR #130:
URL:
https://github.com/apache/lucene-jira-archive/pull/130#issuecomment-1207213022
It's a trivial format change, I'd merge this.
--
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 #130:
URL: https://github.com/apache/lucene-jira-archive/pull/130
--
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...@
mocobeta commented on issue #124:
URL:
https://github.com/apache/lucene-jira-archive/issues/124#issuecomment-1207213143
Addressed in #130.
--
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 spe
mocobeta commented on issue #129:
URL:
https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207218732
I don't think we should cover all ASF Jira projects, but we can list all
related projects to Lucene.
![Screenshot from 2022-08-06
22-50-26](https://user-images.git
mocobeta commented on issue #129:
URL:
https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207219901
- PyLucene: https://issues.apache.org/jira/projects/PYLUCENE
- Open Relevance: https://issues.apache.org/jira/projects/ORP
- Solr: https://issues.apache.org/jira/proj
vlsi commented on issue #129:
URL:
https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207221618
What if you export all the ASF project names and cross-link them?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to Gi
mocobeta commented on issue #129:
URL:
https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207221972
> What if you export all the ASF project names and cross-link them?
Can we export all ASF projects? I'm not really familiar with Jira APIs.
--
This is an automate
vlsi commented on issue #129:
URL:
https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207222313
See https://issues.apache.org/jira/rest/api/latest/project
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub an
mocobeta commented on issue #129:
URL:
https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207222671
Thanks! I'll try to include all Jira projects - if the regex to capture
issue keys is not too slow.
--
This is an automated message from the Apache Git Service.
To resp
vlsi commented on issue #129:
URL:
https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207222737
Just in case: the links might come in multiple flavours.
For instance:
* short form: `SOLR-2355`
* URL: `https://issues.apache.org/jira/projects/ARTEMIS/issues/ART
mocobeta commented on issue #129:
URL:
https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207223134
For this issue, we need to consider only the "short form"; GitHub properly
recognizes URLs and automatically generates links for them.
--
This is an automated message f
vlsi commented on issue #129:
URL:
https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207223133
> is not too slow.
Do you mean `(?:SOLR|LUCENE|...|...)-\d+?` ?
In any case, something like `[A-Z]{2,7}-\d+` should be sufficiently fast,
and then you could double-c
vlsi commented on issue #129:
URL:
https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207223302
>GitHub properly recognizes URLs and automatically generates links for them.
Just to double-check. Do you already recognize URL-links to LUCENE issues
and convert them
mocobeta commented on issue #129:
URL:
https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207225166
> Do you already recognize URL-links to LUCENE issues and convert them to
"github issue + jira fallback"?
No - we do not touch URL-style links to LUCENE (or other p
mocobeta commented on issue #129:
URL:
https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207226410
If the authors just paste https://issues.apache.org/jira/browse/LUCENE-10661
in an issue, GitHub interprets it's an ordinary hyperlink. It'd be great if we
replace it wit
vlsi commented on issue #129:
URL:
https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207226888
There might be issues.apache.org/-style references, see
https://github.com/vlsi/bugzilla2github/issues/7
--
This is an automated message from the Apache Git Service.
To res
mikemccand commented on issue #106:
URL:
https://github.com/apache/lucene-jira-archive/issues/106#issuecomment-120720
Ahh OK +1 then. We should note that in the known limitations of migration.
I'll add it to that doc:
https://docs.google.com/document/d/10m6--f7vbU9OC_SfANN6vbNDvu25CO
mikemccand commented on issue #129:
URL:
https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207233814
> If the authors just paste
https://issues.apache.org/jira/browse/LUCENE-10661 in an issue, GitHub
interprets it's an ordinary hyperlink. It'd be great if we replace it
mikemccand merged PR #128:
URL: https://github.com/apache/lucene-jira-archive/pull/128
--
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..
mocobeta commented on issue #129:
URL:
https://github.com/apache/lucene-jira-archive/issues/129#issuecomment-1207234626
> > If the authors just paste
https://issues.apache.org/jira/browse/LUCENE-10661 in an issue, GitHub
interprets it's an ordinary hyperlink. It'd be great if we replace it
mikemccand commented on issue #126:
URL:
https://github.com/apache/lucene-jira-archive/issues/126#issuecomment-1207235027
> > > I think we cannot determine where to insert the image if the author
does not create the link to it?
> >
> >
> > If users do not mention the image, then
1 - 100 of 148 matches
Mail list logo
