[
https://issues.apache.org/jira/browse/SOLR-11490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexandre Rafalovitch resolved SOLR-11490.
------------------------------------------
Resolution: Implemented
Fix Version/s: 7.2
Ok. I'll treat that as the guidance ("since 3.1" for 3.1 and before on both
Lucene and Solr).
Now that the discussion is done, I will close this case and create new ones for
specific tagging groups/runs.
Regarding tagging parameters/methods, I suspect it can be done
semi-automatically as well, but I am not familiar with specific logic on what
to tag when and why. Perhaps somebody can explain that in a more details in a
separate case.
> 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
> Fix For: 7.2
>
>
> 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]
