mikemccand commented on PR #74:
URL:
https://github.com/apache/lucene-jira-archive/pull/74#issuecomment-1193835019
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 speci
mikemccand commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193837603
I wonder what is the difference between `creator` and `reporter`? Oh I see,
I (`mikemccand`) can create an issue but list another user as `reporter`.
Curious ;) I wond
mikemccand commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193843373
Heh, 13 times too:
```
issue LUCENE-288, fields["reporter"]["name"]='vajda',
fields["creator"]["name"]='a...@osafoundation.org'
issue LUCENE-7726, fields["rep
mocobeta commented on issue #1:
URL:
https://github.com/apache/lucene-jira-archive/issues/1#issuecomment-1193852170
> With a few further small fixes, I'll run a full migration next week once
again. It will hopefully be the final iteration, I'll make it publicly
available to let others chec
mikemccand commented on issue #1:
URL:
https://github.com/apache/lucene-jira-archive/issues/1#issuecomment-1193860507
Thanks @mocobeta -- the conversions are looking great -- I spot checked
around a dozen issues yesterday.
Once you have the new full migration done, I suggest sending
[
https://issues.apache.org/jira/browse/LUCENE-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomoko Uchida updated LUCENE-10557:
---
Reporter: mike Ma (was: Tomoko Uchida)
> Migrate to GitHub issue from Jira
> -
[
https://issues.apache.org/jira/browse/LUCENE-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomoko Uchida updated LUCENE-10557:
---
Reporter: Michael McCandless (was: Tomoko Uchida)
> Migrate to GitHub issue from Jira
> --
[
https://issues.apache.org/jira/browse/LUCENE-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomoko Uchida updated LUCENE-10557:
---
Reporter: Tomoko Uchida (was: mike Ma)
> Migrate to GitHub issue from Jira
> -
mikemccand commented on issue #1:
URL:
https://github.com/apache/lucene-jira-archive/issues/1#issuecomment-1193870585
I suggest also sending a separate email asking for people to state their
GitHub id / Jira id mapping, if they are comfortable doing so?
Rather than having everyone ma
mikemccand commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193871524
> I think "Lucene Fields" has only two values - "New" and "Patch Available".
OK let's maybe not carry those over?
--
This is an automated message from the Apache
mocobeta commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193872039
> I wonder what is the difference between creator and reporter? Oh I see, I
(mikemccand) can create an issue but list another user as reporter. Curious ;)
I wonder how ofte
[
https://issues.apache.org/jira/browse/LUCENE-10557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomoko Uchida updated LUCENE-10557:
---
Reporter: Tomoko Uchida (was: Michael McCandless)
> Migrate to GitHub issue from Jira
> --
mocobeta commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193881378
> > I think "Lucene Fields" has only two values - "New" and "Patch
Available".
>
> OK let's maybe not carry those over?
I once considered/looked at it and deci
mocobeta commented on issue #1:
URL:
https://github.com/apache/lucene-jira-archive/issues/1#issuecomment-1193898346
> Rather than having everyone make a PR / commit a change, I lower the
barrier, maybe just allow them to reply to the email? I volunteer to go through
all replies and carry t
mikemccand commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193923036
Hmm how about `legacy-jira-priority`?
```
python print_priority.py
Major 6182
Minor 3540
Trivial 604
Blocker 202
Critical 117
```
E.g. "h
manishbafna opened a new pull request, #75:
URL: https://github.com/apache/lucene-jira-archive/pull/75
My account info added
--
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.
mikemccand commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193930028
Does GitHub have a way to vote (+1) on issues?
Also, do GitHub labels support numeric types?
If we carried over `legacy-jira-votes` how would we search it? C
mikemccand commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193930893
> I didn't know that, but I noticed we (reporters? committers?) can set an
arbitrary username to Reporter fields in Jira.
LOL I did not know either! Furthermore, y
mikemccand commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193931342
> I once considered/looked at it and decided not to carry them over to
GitHub - I would do nothing for it if you are ok with that.
Yeah +1. They drop even below my
mocobeta commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193953267
> Hmm how about `legacy-jira-priority`?
I'm fine with it if it's needed.
> If we carried over `legacy-jira-votes` how would we search it? Could we
sort by it?
mocobeta commented on code in PR #75:
URL: https://github.com/apache/lucene-jira-archive/pull/75#discussion_r928803845
##
migration/mappings-data/account-map.csv.20220722.verified:
##
@@ -169,3 +169,4 @@ mharwood,markharwood,Mark Harwood
hossman,hossman,Chris M. Hostetter
mune
mocobeta commented on code in PR #75:
URL: https://github.com/apache/lucene-jira-archive/pull/75#discussion_r928803845
##
migration/mappings-data/account-map.csv.20220722.verified:
##
@@ -169,3 +169,4 @@ mharwood,markharwood,Mark Harwood
hossman,hossman,Chris M. Hostetter
mune
mocobeta commented on code in PR #75:
URL: https://github.com/apache/lucene-jira-archive/pull/75#discussion_r928823975
##
migration/mappings-data/account-map.csv.20220722.verified:
##
@@ -169,3 +169,4 @@ mharwood,markharwood,Mark Harwood
hossman,hossman,Chris M. Hostetter
mune
mikemccand commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1193991508
> > Hmm how about `legacy-jira-priority`?
>
> I'm fine with it if it's needed.
>
> > If we carried over `legacy-jira-votes` how would we search it? Could we
mikemccand opened a new pull request, #76:
URL: https://github.com/apache/lucene-jira-archive/pull/76
I ran on one issue that had votes and peeked at the output JSON and it looks
correct!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on
mikemccand commented on issue #29:
URL:
https://github.com/apache/lucene-jira-archive/issues/29#issuecomment-1194003309
Have we confirmed that INFRA is able to make the whole Jira project
read-only after we are done migrating? Is it just a matter of opening a ticket
and it's quick/easy?
mikemccand commented on issue #29:
URL:
https://github.com/apache/lucene-jira-archive/issues/29#issuecomment-1194003681
Maybe we just open an INFRA issue now, but make it clear not to actually do
it yet, to get it on their radar?
--
This is an automated message from the Apache Git Servic
mikemccand commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1194005927
Woops, I failed to link the PR properly:
https://github.com/apache/lucene-jira-archive/pull/76
--
This is an automated message from the Apache Git Service.
To respond t
mocobeta commented on PR #76:
URL:
https://github.com/apache/lucene-jira-archive/pull/76#issuecomment-1194018160
Please feel free to merge this. I cannot run/test this right now.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHu
mikemccand commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1194019029
`watches` is a Jira field for people who have explicitly subscribed to
updates on a Jira issue.
I don't think GitHub has the same capability? You can watch at the
mocobeta commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1194021106
> So maybe we leave `watches` behind (do not migrate that field to GitHub)?
I agree with it.
--
This is an automated message from the Apache Git Service.
To respon
apeteri opened a new pull request, #77:
URL: https://github.com/apache/lucene-jira-archive/pull/77
I saw my name in the account map candidates file at this location:
https://github.com/apache/lucene-jira-archive/blob/1309c3ff9b7815d660484b123b30be1789b672f4/migration/mappings-data/account-ma
mocobeta commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1194025672
> You can watch at the repo level, but not on individual issues?
You can watch/unwatch particular issues/PRs by Subscribe/Unsubscribe the
issue/PR. (a button with a b
mikemccand commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1194027968
I think we really should migrate `parent` in some way, since we already
migrate the reverse direction (sub-tasks)?
--
This is an automated message from the Apache Git S
mikemccand commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1194029781
> > You can watch at the repo level, but not on individual issues?
>
> You can watch/unwatch particular issues/PRs by Subscribe/Unsubscribe the
issue/PR. (a button
mocobeta commented on PR #77:
URL:
https://github.com/apache/lucene-jira-archive/pull/77#issuecomment-1194030016
Thanks @apeteri for verifying it. We couldn't manually check all candidate
accounts.
--
This is an automated message from the Apache Git Service.
To respond to the message, pl
mocobeta merged PR #77:
URL: https://github.com/apache/lucene-jira-archive/pull/77
--
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 opened a new issue, #78:
URL: https://github.com/apache/lucene-jira-archive/issues/78
Spinoff from #61.
We should try to briefly summarize what we did during the migration, fields
we chose to leave out, limitations (e.g. if you were not "verified" then you
are not "mention
apeteri commented on PR #77:
URL:
https://github.com/apache/lucene-jira-archive/pull/77#issuecomment-1194036688
No worries! Thank you and everyone involved for handling the migration!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
mocobeta commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1194043812
> Ahh OK, hmm. But we cannot carry over these watches on behalf of all
users, I assume. Users will have to re-watch the issues they care about (even
the legacy Jira ones) a
mikemccand commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1194061412
> > Ahh OK, hmm. But we cannot carry over these watches on behalf of all
users, I assume. Users will have to re-watch the issues they care about (even
the legacy Jira one
mikemccand commented on issue #61:
URL:
https://github.com/apache/lucene-jira-archive/issues/61#issuecomment-1194063267
OK I looked at all of the fields (listed above) and I think we are done,
except for this one!:
> I think we really should migrate `parent` in some way, since we alr
mikemccand closed issue #61: Should we carry over Jira "labels"?
URL: https://github.com/apache/lucene-jira-archive/issues/61
--
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 opened a new issue, #79:
URL: https://github.com/apache/lucene-jira-archive/issues/79
Spinoff from #61.
We already carry the other direction (`sub-tasks`).
It looks like 333 issues have a parent.
--
This is an automated message from the Apache Git Service.
To respo
mocobeta commented on issue #79:
URL:
https://github.com/apache/lucene-jira-archive/issues/79#issuecomment-1194074037
GitHub automatically adds mature links if we link from one issue to another
issue, but I agree that it'd be good to explicitly mention parent issues.
--
This is an automa
[
https://issues.apache.org/jira/browse/LUCENE-10592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570912#comment-17570912
]
ASF subversion and git services commented on LUCENE-10592:
--
Co
mikemccand commented on issue #79:
URL:
https://github.com/apache/lucene-jira-archive/issues/79#issuecomment-1194082464
OK I have a PR; it renders LUCENE-618 opening description like this:
-
The last GData - Server commit does not build due to a wrong commit.
Yonik did
mikemccand merged PR #76:
URL: https://github.com/apache/lucene-jira-archive/pull/76
--
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...@
mikemccand opened a new pull request, #80:
URL: https://github.com/apache/lucene-jira-archive/pull/80
Render the parent link in the `Legacy Jira` section.
I also removed ` details` from `Legacy Jira details` header. It seemed
redundant / self-explanatory already.
--
This is an aut
mikemccand commented on issue #60:
URL:
https://github.com/apache/lucene-jira-archive/issues/60#issuecomment-1194092727
Reminder: once we have the draft migrated test repo public, find some Jira
issues that have exotic Unicode escapes/characters and confirm that migrated
properly.
--
Th
[
https://issues.apache.org/jira/browse/LUCENE-10592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570929#comment-17570929
]
ASF subversion and git services commented on LUCENE-10592:
--
Co
mocobeta commented on code in PR #80:
URL: https://github.com/apache/lucene-jira-archive/pull/80#discussion_r928947072
##
migration/src/jira_util.py:
##
@@ -83,6 +83,15 @@ def extract_assignee(o: dict) -> tuple[str, str]:
return (name, disp_name)
+def extract_parent(o:
iverase commented on PR #1017:
URL: https://github.com/apache/lucene/pull/1017#issuecomment-1194123352
Hey Nick,
Why so much hurry with this change? I appreciate everything you are trying
to do to signal the feature as experimental and adding the version on the doc
value but still it
iverase commented on code in PR #1017:
URL: https://github.com/apache/lucene/pull/1017#discussion_r928955670
##
lucene/core/src/java/org/apache/lucene/document/ShapeDocValues.java:
##
@@ -0,0 +1,907 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+
mocobeta commented on issue #29:
URL:
https://github.com/apache/lucene-jira-archive/issues/29#issuecomment-1194132316
I would open two issues at the same time when we ask infra to start the
migration; one for running the import script, and one for making Jira
read-only. Anyway, it'll need
mikemccand commented on code in PR #80:
URL: https://github.com/apache/lucene-jira-archive/pull/80#discussion_r928980448
##
migration/src/jira_util.py:
##
@@ -83,6 +83,15 @@ def extract_assignee(o: dict) -> tuple[str, str]:
return (name, disp_name)
+def extract_parent(o
mocobeta commented on PR #81:
URL:
https://github.com/apache/lucene-jira-archive/pull/81#issuecomment-1194161000
Thaks @tang-hi
--
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 comm
mocobeta merged PR #81:
URL: https://github.com/apache/lucene-jira-archive/pull/81
--
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
[
https://issues.apache.org/jira/browse/LUCENE-10592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julie Tibshirani updated LUCENE-10592:
--
Attachment: Screen Shot 2022-07-25 at 9.04.11 AM.png
> Should we build HNSW graph on
[
https://issues.apache.org/jira/browse/LUCENE-10592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570976#comment-17570976
]
Julie Tibshirani commented on LUCENE-10592:
---
It looks like this commit gave a
[
https://issues.apache.org/jira/browse/LUCENE-10592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570976#comment-17570976
]
Julie Tibshirani edited comment on LUCENE-10592 at 7/25/22 4:10 PM:
-
[
https://issues.apache.org/jira/browse/LUCENE-10592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570976#comment-17570976
]
Julie Tibshirani edited comment on LUCENE-10592 at 7/25/22 4:10 PM:
-
[
https://issues.apache.org/jira/browse/LUCENE-10592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570976#comment-17570976
]
Julie Tibshirani edited comment on LUCENE-10592 at 7/25/22 4:10 PM:
-
nknize commented on PR #1017:
URL: https://github.com/apache/lucene/pull/1017#issuecomment-1194649110
Thanks @iverase.
> Why so much hurry with this change? ...it will be nice to have something
production ready.
Just a few points here.
1. I don't believe the proposed PR is
visionarywind opened a new issue, #1048:
URL: https://github.com/apache/lucene/issues/1048
### Description
As I know, lucene doc is a internal docId, it cannot be used as an external
id.
Why is it designed like this ?
Could it be designed to be constant ?
Thank you.
--
T
JoeHF commented on PR #1003:
URL: https://github.com/apache/lucene/pull/1003#issuecomment-1195050814
no obvious regression or perf improvement, guess there are no such cases in
benchmark
wikimedium10k:
TaskQPS baseline StdDevQPS
my_modified_version
[
https://issues.apache.org/jira/browse/LUCENE-10616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17571217#comment-17571217
]
fang hou commented on LUCENE-10616:
---
I think this pr [https://github.com/apache/lucen
67 matches
Mail list logo
