OpenJDK bug tracker goes public

Hi, Habr!

I have great news for you: OpenJDK-shnaya JIRA has become open to all! Address:
In the old Sanovo bugtracker, the numbering of bugs was cross-cutting, independent of the project. In JIRA, everything is arranged a little differently: each project, as you know, has a certain prefix (in our case it is “JDK”), followed by a hyphen and a bug number. Accordingly, what was earlier in was a bug 4459438 in JBS received the number JDK-4459438 .

This event has long been expected in the Java community. Inside Oracle, it was not a secret for a long time, but it was expected that the new error tracking system would be officially announced next week at the JavaOne conference . Looks like they were impatient! For the first time, the news slipped into public on a Twitter
night by Bernard
JIRA with the proud name of Java Bug System (JBS) appeared about a year ago and replaced the old dignitary bug tracker, the Java part of which is known to the general user as . What contributed to the transition?

Switching to JIRA, in my opinion, was necessary for many reasons, including:
  • The old bug tracker was not perfect, and besides, it had to be supported.
  • Access to the old bugtrack could only be done from the internal Sun / Oracle network.
  • Access to the Java part of the old bugtracker for people who were not Sun / Oracle employees could only be achieved through the mug , which was also not ideal. For example, there are some problems with finding bugs.
  • Since 2006, as part of the OpenJDK project, the community has been actively involved in the development of the Java platform. New tools were needed.
  • Mailing lists have become such tools. But now they look like greetings from the 20th century, don't they?
  • Finally, JIRA is the coolest common platform for tracking bugs today.

What gives the transition to JIRA Java organizations, the Java community and Oracle? Firstly, life will simply become more convenient and more familiar. This is really a step towards! Secondly, public mailing lists will be slightly offloaded and in the next year or two, many things from the mailing lists will go to JBS JIRA. Well, and as a result, thirdly, I believe that the number of communications between Java platform developers inside Oracle and other developers will increase, which should positively affect the quality of the final product (Java SE 7 updates, Java SE 8, Java SE 9 and. etc.)
A detailed description of the new bugtracker is here .

So you are welcome to file bugs. And of course, fix it!