[
https://issues.apache.org/jira/browse/SOLR-11490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463002#comment-16463002
]
Jan Høydahl commented on SOLR-11490:
------------------------------------
I think Robert says that "3.1" is fine, since that is a valid version. We can
view lucene/solr as a "new product" separate since the merger, and that product
started as v3.1. I'm ok with that as well, since the goal of Javadoc is not to
track svn/git history, we still have repos for that, but to give a hint what
releases a particular class has been present in.
PS: When we had the Solr docs in the old wiki, we used to tag features,
parameters etc with a "since" tag which was often very useful. I hope that
adding these since annotations can get back some of that. I guess we can also
tag new methods, not only classes?
> Add @since javadoc tags to the interesting Solr/Lucene classes
> --------------------------------------------------------------
>
> Key: SOLR-11490
> URL: https://issues.apache.org/jira/browse/SOLR-11490
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Alexandre Rafalovitch
> Assignee: Alexandre Rafalovitch
> Priority: Minor
>
> As per the discussion on the dev list, it may be useful to add Javadoc since
> tags to significant (or even all) Java files.
> For user-facing files (such as analyzers, URPs, stream evaluators, etc) it
> would be useful when trying to identifying whether a particular class only
> comes later than user's particular version.
> For other classes, it may be useful for historical reasons.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
