[ http://issues.apache.org/jira/browse/LUCENE-500?page=comments#action_12370729 ]
Doug Cutting commented on LUCENE-500: ------------------------------------- I think we should commit this, except leave DateField deprecated rather than remove it, since that is the promise made. We should probably remove that promise, however, so that we can eventually remove it. We said we'd remove all deprecated code, and we won't. But that won't break anyone who compiles in 1.9.1 without deprecation warnings, which is the more important promise. Then we'll have a proto-2.0 release for developers to test. We can separately decide how to handle dates in the QueryParser. It would not be wrong to continue doing the same thing we've done in 1.9, would it? That won't break anyone. In short, let's not let this issue stop us from removing all of the other deprecated code and finding out whether anything else breaks. > Lucene 2.0 requirements - Remove all deprecated code > ---------------------------------------------------- > > Key: LUCENE-500 > URL: http://issues.apache.org/jira/browse/LUCENE-500 > Project: Lucene - Java > Type: Task > Versions: 1.9 > Reporter: Grant Ingersoll > Attachments: deprecation.txt > > Per the move to Lucene 2.0 from 1.9, remove all deprecated code and update > documentation, etc. > Patch to follow shortly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
