- Loading...
The first Quality Report was published in September 2015 here, our initial intention was to provide a report every six months. We now release
a Feature Release every 6 months so we have decided to publish a Quality Outreach Report every three months.
The previous report was issued in March 2020 here
We now have 135 FOSS Projects and their developers listed on the Quality Outreach Wiki page.
There have been 16 new FOSS Projects added since the last report in March 2020. Welcome!
New Projects added :
Eo-yaml
Note, we have a further 15 Projects that we communicate with that are not listed on the wiki i.e 150 projects in total.
All FOSS Projects receive regular updates when Early Access (EA) builds become available, they are encouraged to
test and report back any issues they find during their testing.
Developers from 8 of the 150 participating projects filed 14 new issues in the JDK Bug System in the last three months, thank you !
Priority | Fixed | Open | Duplicate | Not an Issue | Total |
---|---|---|---|---|---|
P1 | 0 | 0 | 0 | 0 | 0 |
P2 | 2 | 0 | 0 | 0 | 2 |
P3 | 1 | 3 | 0 | 0 | 4 |
P4 | 1 | 5 | 2 | 0 | 8 |
Total Unique Issues | 4 | 8 | 2 | 0 | 14 |
The Table above lists the number of bugs logged in total - 14, of which 2 were P2 bugs, with 4 P3 bugs & 8 P4 bugs.
Component | P1 | P2 | P3 | P4 | Total |
---|---|---|---|---|---|
core-libs | 0 | 0 | 1 | 2 | 3 |
client-libs | 0 | 0 | 0 | 1 | 1 |
hotspot | 0 | 1 | 0 | 1 | 2 |
infrastructure | 0 | 1 | 0 | 0 | 1 |
security-libs | 0 | 0 | 1 | 2 | 3 |
tools | 0 | 0 | 2 | 2 | 4 |
Total Unique Issues | 0 | 2 | 4 | 8 | 14 |
The table above lists the number of bugs logged by Component. The 14 Bugs were found in 6 component areas .
The following Projects have submitted bug reports in the last three months and deserve special mention:
Priority | Fixed | Open | Duplicate | Not an Issue | Incomplete | Won't fix | Can't Reproduce | Other | Total |
---|---|---|---|---|---|---|---|---|---|
P1 | 13 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 13 |
P2 | 57 | 0 | 10 | 6 | 0 | 0 | 4 | 2 | 79 |
P3 | 95 | 16 | 27 | 21 | 3 | 7 | 6 | 0 | 175 |
P4 | 25 | 36 | 12 | 8 | 4 | 5 | 5 | 0 | 95 |
P5 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 2 |
Total Unique Issues | 191 | 52 | 50 | 35 | 7 | 12 | 15 | 2 | 364 |
Priority | Fixed | Open | Duplicate | Not an Issue | Total |
---|---|---|---|---|---|
P1 | 0 | 0 | 0 | 0 | 0 |
P2 | 2 | 0 | 0 | 0 | 2 |
P3 | 3 | 1 | 0 | 0 | 4 |
P4 | 1 | 2 | 0 | 0 | 3 |
Total Unique Issues | 6 | 3 | 0 | 0 | 9 |
The following Projects have submitted bug reports against JDK 15 Early Access builds :
FOSS Project | JDK 15 EA | Comments | |
---|---|---|---|
1 | Apache Ant | No issues found against our Ant testsuite on a Linux setup using JDK 15 EA build 15-ea+24-1168. | |
2 | Apache CXF | Testing JDK15 EA builds ,we have to address is removal of SSLv3 support (this is good thing) | |
3 | Apache Lucene | JDK15 build 14 was installed, and first build succeeded. | |
4 | Apache Maven | We're testing with Java 15-ea for a couple of weeks now, no issues found | |
5 | Apache Tomcat | All looking OK at the moment for Java 15 as far as Tomcat is concerned. | |
6 | Apache Wicket | I've just tested JDK 15 b24 with Apache Wicket. Except the issue with aQute library everything else is rock solid for us! | |
7 | Apache Zookeeper | I have tested a bunch of other applications that use ZooKeeper and all works as expected | |
8 | Eclipse Collections | building on JDK14 GA and JDK15 EA-Build-25. | |
9 | Eo-yaml | All tests passed with JDK 15 EA b28 | |
9 | JaCoCo | Java 15 repo is green for us (including tag jdk-15+24) - confirmed JDK-8245070 fixed in b24 | |
10 | JobRunr | FYI - all is also working on openjdk:15-ea-27-jdk | |
11 | JOSM | Logged bug testing JDK 15 EA b6 – confirmed fix in b19 | |
12 | JUnit5 | JDK 15+ea-24 shows "#TestsAreStillGreenOnJDK15" | |
13 | FXGL | Tests are green with b24 | |
14 | MyBatis | All test pass b27 | |
15 | PDFsam | All tests are green with b24 | |
16 | RxJava | All targets - Compile: OK Tests: OK with JDK 15b24 | |
17 | Sejda | All tests are green with b24 |
Oracle is considering deprecation and (eventual) removal of the jinfo, jmap, jstack - (aka “j* tools”) and building out a future foundation for some aspect of serviceability on jcmd. For this, a Survey has been created to gather more information on how these tools are used in practice, especially outside of Oracle. The survey(link below) will remain open through July 15 2020.
Survey : On the jinfo, jmap, jstack serviceability tools