[
https://issues.apache.org/jira/browse/SOLR-11490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16462523#comment-16462523
]
Alexandre Rafalovitch commented on SOLR-11490:
----------------------------------------------
Yes, I will mark it resolved and come back to it later in more targeted groups.
The only issue this tagging created is that there will always be new classes
that are not (yet) tagged. And they will look identical as ones not tagged
because they are pre-3.1
We had agreed that pre-3.1 classes will get no since tag. But perhaps I can
retag them all "pre-3.1". This way only the newest classes in the particular
category will be untagged. Obviously, this mostly matters to the Lucene/Solr
newbies, but that's exactly my target audience with this JIRA.
[~rcmuir] - is that ok with you to have a common-joint historical tag instead
of no tag at all?
I just want to resolve this in this case, as it was more common, to have the
discussion finalized in one place.
> 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]
