Skip to content
This repository has been archived by the owner on Mar 5, 2024. It is now read-only.

Issues: jcp-org/jsr358

56 Open 16 Closed
56 Open 16 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

JSR358-101: Clarification in section 3.7.7 around JSR ballot rules bug
#72 opened Mar 17, 2017 by apastsya
1
JSR358-100: The Process Document contains a reference to "one or both Executive Committees" bug
#71 opened May 19, 2016 by apastsya
1
JSR358-99: Maintenance Lead to specify at Maintenance Release whether future changes are expected bug
#70 opened Apr 12, 2016 by apastsya
1
JSR358-98: Require a renewal ballot when Dormant JSRs are revived? bug
#69 opened Apr 12, 2016 by apastsya
1
JSR358-97: Further changes to the Maintenance Review process bug
#68 opened Feb 3, 2016 by apastsya
3
JSR358-96: Create errata process, separate from the MR process New Feature
#67 opened Apr 13, 2015 by apastsya
4
JSR358-94: Patrick: Assign specific issues for review
#65 opened Mar 18, 2015 by apastsya
JSR358-93: Create a standard Spec license New Feature
#64 opened Mar 7, 2015 by apastsya
JSR358-92: Create a standard Community TCK License New Feature
#63 opened Mar 7, 2015 by apastsya
3
JSR358-91: Remove from licenses any barriers to full compliance with JCP 2.8's transparency requirements bug
#62 opened Mar 6, 2015 by apastsya
JSR358-89: Mike Milinkovich: review JSPA for language preventing release of interim implementations prior to Final Release
#60 opened Mar 6, 2015 by apastsya
1
JSR358-88: Provide non-normative guidelines on RI license selection bug
#59 opened Feb 27, 2015 by apastsya
2
JSR358-87: Define a standard list of open-source RI licenses bug
#58 opened Feb 27, 2015 by apastsya
2
JSR358-85: IP should vest as soon as granted rather than when the JSR goes final bug
#57 opened Feb 24, 2015 by apastsya
2
JSR358-84: Need a complete answer on the ASLv2 incompatibility issue bug
#56 opened Oct 2, 2014 by apastsya
JSR358-82: Suggested language to help track changes in employment status bug
#55 opened Jun 26, 2014 by apastsya
1
JSR358-66: Modify Process Document to simplify the transition of a JSR from one Spec Lead (or Maintenance Lead) to another bug
#47 opened Apr 8, 2014 by apastsya
5
JSR358-64: Mandate collaborative development process for RIs bug
#45 opened Apr 8, 2014 by apastsya
JSR358-49: Ambiguity of Specification, Content and License causes Spec Leads to ignore it or use other licenses bug
#42 opened Jan 30, 2013 by apastsya
4
JSR358-48: A goal of RI/TCK IP working group should be access to the RI/TCK by community Improvement
#41 opened Jan 11, 2013 by apastsya
3
JSR358-47: Can/Should we strengthen reciprocity to apply across JSRs? New Feature
#40 opened Dec 21, 2012 by apastsya
JSR358-45: Reciprocity should be mandated bug
#39 opened Dec 7, 2012 by apastsya
JSR358-44: Ensure that implementers are granted the right to incorporate IP into future as well as current implementations of a JSR bug
#38 opened Dec 7, 2012 by apastsya
JSR358-42: Language in the JSR 336 TCK license appears to prohibit implementations of the Spec bug
#37 opened Oct 13, 2012 by apastsya
2
JSR358-41: Flatten the current "hub and spoke" IP model bug
#36 opened Oct 13, 2012 by apastsya
ProTip! Exclude everything labeled bug with -label:bug.