Issue Details (XML | Word | Printable)

Key: JSR348-95
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: lightguard
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
jsr348

Section 1.1.2 needs a little rewording to alleviate ambiguities

Created: 23/Aug/11 11:07 PM   Updated: 08/Sep/11 08:29 PM   Resolved: 08/Sep/11 08:29 PM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Related
 

Tags:
Participants: lightguard and pcurran


 Description  « Hide

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."?



pcurran added a comment - 08/Sep/11 08:29 PM

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.