[
https://issues.apache.org/jira/browse/LUCENE-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784153#action_12784153
]
Michael McCandless commented on LUCENE-2094:
--------------------------------------------
bq. I consider this as a misunderstanding caused by too much instant messaging.
We need to strive to keep technical discussions public, for this reason. If
you ever find yourself discussing technical direction of changes to Lucene,
privately, kick yourself and others near you and then take it back to the list
:)
You all probably felt that you reached consensus (over IM), but to the rest of
us, it suddenly felt like you committed while we were still debating the
approach. Like Mark, I'm certainly not saying anything bad was done, but, it's
a dangerous precedent that "consensus reached in private is then acted on in
public without corresponding public consensus".
Erring on the side of caution, moving more slowly, when consensus is iffy, is
best. Mark's original idea -- to separately open the question of "hey let's
commit this as it stands now and then debate the Version vs separate boolean
separately" would've been a good approach, I think.
Also, I think other Apache communities have public chats, where
devs/contributors/users can hang out and discuss stuff, and it's well
publicized that this is the standard place where things are discussed, anyone
can join in, etc. We could consider taking that step for Lucene? Those of us
who are online can then hang out. I don't like that it's not
archived/searchable (or... is it? Anyone know what other communities do? EG,
is there a way to set up an IRC channel and have it archived?). IM clearly is
a nice, fast interactive way to discuss things, far better than email /
appending to Jira issues.
> Prepare CharArraySet for Unicode 4.0
> ------------------------------------
>
> Key: LUCENE-2094
> URL: https://issues.apache.org/jira/browse/LUCENE-2094
> Project: Lucene - Java
> Issue Type: Bug
> Components: Analysis
> Affects Versions: 3.0
> Reporter: Simon Willnauer
> Assignee: Uwe Schindler
> Fix For: 3.1
>
> Attachments: LUCENE-2094.patch, LUCENE-2094.patch, LUCENE-2094.patch,
> LUCENE-2094.patch, LUCENE-2094.patch, LUCENE-2094.patch, LUCENE-2094.txt,
> LUCENE-2094.txt, LUCENE-2094.txt
>
>
> CharArraySet does lowercaseing if created with the correspondent flag. This
> causes that String / char[] with uncode 4 chars which are in the set can not
> be retrieved in "ignorecase" mode.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
