[
https://issues.apache.org/jira/browse/UIMA-998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590927#action_12590927
]
Burn Lewis commented on UIMA-998:
---------------------------------
OK - I think I get it ... no point in documenting something twice ... known
problems should be in Jira with the FAQ reserved for problems we can't fix
(presumably because they're bugs outside UIMA.) Perhaps we might call these
"Limitations" or "Restrictions" and keep the word "issue" for the Jira ones.
Even the "won't fix" ones are problematic ... perhaps they may get fixed one
day ... e.g. somebody might tackle the Jcasgen merge one in the FAQ.
Perhaps we could expose this distinction by adding a line to the FAQ and
shipped readmes saying that "Known problems and any workarounds have been
entered as Jira isues."
> The UIMA website should have a list of known problems and any work-arounds
> --------------------------------------------------------------------------
>
> Key: UIMA-998
> URL: https://issues.apache.org/jira/browse/UIMA-998
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Burn Lewis
> Priority: Minor
>
> The list of known problems in the shipped README is rather brief, and is soon
> out-of-date. It would be nice to have a page on the website listing known
> problems and any work-arounds.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
