Interim Bug Submission Process

Issue Tracker

As with most of the projects hosted on the java.net web site, the bug submission tool for the cqME project will be the familiar JIRA environment. Issue Tracker is based on IssueZilla, which is the CollabNet Enterprise Edition variant of the popular open source bug tracking system known as BugZilla. Issue Tracker is a mature bug tracking system that is effectively used in many other open source communities on java.net.

Excellent and extensive online help is available on the use of JIRA. Visit http://confluence.atlassian.com/display/JIRA040/JIRA+User%27s+Guide?clicked=jirahelp for more information about JIRA.

However, the best long-term solution for bug tracking for this community will be determined by a number of factors, including these: Ease of use Extensibility of the user interface to support evolving community and release process needs Richness of interface mechanisms to external defect tracking systems

JIRA might not meet all of these needs, so other bug tracking systems are being evaluated. Any changes to the issue tracking tool will preserve community contributions to date and maintain ease of use for the community.

Preventing Duplicate Bug Reports

Due to the efforts to make Java Platform, Micro Edition (Java ME platform) source code components available to the open source community as quickly as possible, the internal database of existing Java ME technology bugs has not yet been migrated from the Oracle internal bug tracking systems into Issue Tracker. For this reason, Issue Tracker will not show bugs contained in our internal defect tracking system. After the evaluation of bug tracking tools is complete, internal bugs and bugs submitted by the community up to that point might be migrated into a new defect tracking system.

As a result, the cqME project bugs currently in the Oracle internal bug tracking system will not be available for viewing. However, at the launch of the cqME project, a number of active cqME project bugs in open states that are thought to be of interest to the community will be identified. These bugs will be manually migrated into the Issue Tracker environment for community benefit.

Because it's important to avoid duplicate bugs whenever possible, members of the Java ME technology open source community are urged to browse the Issue Tracker for duplicate bugs before submitting bug reports.

In the event that duplicates of Issue Tracker bug submissions are discovered in Oracle's internal defect tracking database, module owners will evaluate progress of the duplicate bug in Oracle's internal bug database. If the bug is not in advanced stages of processing, its information will be moved by a module owner to Issue Tracker to cultivate community participation in resolving it and the Oracle internal bug report will be closed. Duplicate bugs that are very close to resolution in Oracle's internal bug database will be left there and the duplicate Issue Tracker submissions closed and marked as duplicates.

Tracking Community-Submitted Bugs

Despite these interim measures for issue management, community contributions of bugs using Issue Tracker are welcomed and encouraged.

JIRA will be the focus of community contributions of issues related to Java ME platform open source software components. Oracle engineers, contributors, and community members will collaborate using JIRA to develop and explore community interests and the evolution of the software and generation of community releases.

Bugs submitted using the JIRA tool are very important to developing community knowledge and involvement. The issues submitted there will be processed start to finish in the open source community and not in Oracle's internal systems. Please log bugs at JIRA. It's the key to working as a community on concerns, problems, suggestions, and contributions to open source Java ME technologies.