[JSR348-95] Section 1.1.2 needs a little rewording to alleviate ambiguities Created: 23/Aug/11  Updated: 08/Sep/11  Resolved: 08/Sep/11

Status: Closed
Project: jsr348
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: lightguard Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
is related to JSR348-71 Issue Tracker should be a defined term Closed


In section 1.1.2 it's stated that a publicly readable issue tracker should be used for the specification but implies users can add comments (doesn't say anything about the public being able to add issues). With all the explicit defining that has gone into the current drafts, should this be clarified a bit more to allow addition of issues / comments by the public or simple remove the word "readable" and simply go with "Issues must be tracked through a public issue tracking mechanism."?

Comment by pcurran [ 08/Sep/11 ]

The new wording proposed for section 1.1.2 in
JSR348-71 Issue Tracker should be a defined term addresses this concern.

I'm closing this issue. Further comments can be added to JSR348-71 if necessary.

Generated at Thu Oct 27 18:46:29 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.