GlassFish - World's first Java EE 7 Application Server


Two Way BugBridge between Bugtraq and Issuetracker

Data contained in this page are for historical purposes only. Oracle customers can access defect information through support.oracle.com. GlassFish project members can access defect information at the GlassFish JIRA: http://java.net/jira/browse/GLASSFISH

Sun has internal Bugtracking system called BugTraq and external bugtraq system called "Issuetracker"
Currently , Bugtraq system is not exposed outside, and until that happens , a temporary two way bridge solution has been put into place which synchs up bugs in these two systems on periodic basis.
This two way bridge will transfer internal bugs outside to Issuetracker and import issues from IssueTracker to it's internal BugTraq system.
Why is BugBridge required?
Some bugs are still filed in internal tool and we want external community to be engaged in GlassFish project.Hence, it is mandatory that internal bugs should be exposed outside.Ideally,everyone should be using only one tool i.e Issuetracker,but until that happens,we will continue to bugbridge.
Bugs are not synchronized.Which system should I follow?
Please lookup both bugtraq and Issuetracker to get latest assigned bugs.BugBridge is required so that bug trends,bug metrics can be obtained from one consolidated database.As a responsible engineer for a Issue/Bug, make sure that originally filed Bug/Issue gets updated properly.Synchronization will be handled by management/Quality Team.

I am Quality Engineer,external developer. I found a bug.Where should I file it?
Please file bugs in external Issuetracker as much as possible unless bug information contains customer sensitive proprietary sensitive data.In that case, bug should be filed at BugTraq.

What subcategories are online for GlassFish?
Two way bugbridge tool is going to be online for following subcategories of GlassFish

  • web_container,deployment,web_services,jbi,admin,admin_gui,command_line_interface,ejb_container

,group_management_service,jca,orb,web_services_mgmt,amx,jms,jts,verifier,jdbc,sample_apps,packaging,
logging,standalone_client,build_system,configuration,hadb_admin,i18n,lifecycle_modules,load_balancer
rmi_iiop_load_balancer,upgrade_tool

is already online for past couple of weeks..
Note: Two way bugbridge is deployed only for Glassfish project.

What does this mean for internal & external developers and Quality Team?
Bugs Transferred from Bugtraq to Issuetracker

  • Bugs filed under 9.1 PE are going to be visible outside as "mirrored bugs". Bugs exposed outside in Issuetracker will have a comments beginning with <BTXXXXXXX> where XXXX reflects bugtraq state number
  • BugBridge tool will take care of synching up of bug states and update between originally filed bug and mirrored bug.
  • It is expected that bugs will be filed in Issuetracker as much as possible, and internal BugTraq will be used for only customer specific bugs
  • BugBridge tool is to be used for easy management of bugs for BugSWAT meetings and enable external community to access internal bugs.
  • Note:Internal bugs can also be seen at following link

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=<bug-id>

  • This link is available in mirrored bugs in Issuetracker also for easy browsing.

What bugs are exposed outside

  • BugTraq product "sunone_application_server"
  • Release 9.1PE
  • Issues are transferred inside bugtraq system under product "sunone_application_server" and release "9.1PE"
  • Internal Bugs are transferred outside to component "glassfish" and release "9.1PE"
  • Engineering Notes of type "Comments" are not shared to the community.

How to exclude a customer sensitive internal bug from being visible outside

  • put hook6 field as "nojdc".
  • File BugTraq request under 9.1EE
  • All security bugs are not transferred outside.
  • "Comments" Eng Notes in BugTraq are not shared with the community.

How to setup a e-mail filter

  • Bugbridge username on Issuetracker is gfbugbridge@dev.java.net.
  • Submitting engineers won't get a confirmation e-mail about "mirrored" bugs.However,original bugs will have a corresponding mirrored bug information at end of engineering note or Description section.
  • Every time originally filed bug changes,there will be update to mirrored bug/issue and email sent out issues@glassfish.java.net.Cumulative changes in last 24 hour period are taken.
  • To keep inbox happy and clean, it is advisable that an email filter is setup for gfbugbridge@dev.java.net for both internal and external users, and one for glassfish-bugbridge@sun.com for internal users.

Mirrored Bugs Characteristics

  • Bugs are submitted by gfbugbridge@dev.java.net in Issuetracker and by glassfish-bugbridge@sun.com in BugTraq
  • Mirrored bugs/Issue are read-only.Any change to them are not propagated back.
  • Mirrored Issue begins with <BTXXXXXXX> where XXXX.. is originally filed bugtraq request
  • Mirrored Bug beings with <IT :XXXX..] where XXXX.. is originally filed Issuetracker Issue.
  • Mirrored bugs synch up state with originally filed Issue/ChangeRequest once in 24 hour
  • Submitting engineers won't get a confirmation e-mail about "mirrored" bugs.However,original bugs will have a corresponding mirrored bug information at end of engineering note or Description section.

BugSWAT Query Change: How to exclude mirrored bugs from Issuetracker or BugTraq from Query

  1. From Issuetracker-put additional clause "not reported by gfbugbridge@dev.java.net i.e

https://glassfish.java.net/issues/query.cgi

  1. From BugTraq-exclude bugs with hook1="issue-tracker" OR
    1. exclude bugs filed by glassfish-bugbridge@sun.com

What is corresponding Evaluated State in Issuetracker

  • Target_milestone in Issuetracker should not be empty to mark an issue as "evaluated".

Thanks,
Bugbridge Team
quality@glassfish.java.net