Update Center 2

Bug Reports and RFEs

Reports

Report
UC2 Toolkit Bugs and RFEs
Stopper bugs
By Priority and Target Milestone
All Open Bugs and RFEs
Open Issues
Unassigned Bugs and RFEs
All issues targeted after 2.0
Open Accessibility Bugs
IPS Bugs and RFEs
IPS Bugs and RFEs of Interest to UC
All unresolved IPS issues
All IPS Bugs and RFEs
Adoption-related Bugs and RFEs
GlassFish V3-related UC2 Toolkit Usage Bugs and RFEs List of outstanding GF V3 issues to be reviewed and potentially filed

Where to File?

Feeling Lazy, Don't Have Time?

Just send a report to dev@updatecenter.dev.java.net

We're happy to receive your feedback any way we can get it!

Update Center Toolkit Bugs and RFEs

All issues concerning Update Center 2 should be filed here in the UC2 issue tracking system.

In what release is a bug fixed?

The UC2 project uses the target-milestone field of an issue to indicate the build where a issue is resolved on the trunk. If a bug is back ported to a branch for older release such as a sustaining release, then a keyword is used to indicate that the bug is also fixed in the older release. This means that reports for issues resolved in sustaining releases must be based on keywords instead of the target-milestone field. (Decision from Oct 30, 2008 iteam meeting.)

Image Packaging System Bugs and RFEs

Issues concerning the IPS port delivered by the UC2 project should first be filed against the UC2 project using the ipsenhancements subcategory. A member of the UC2 team will then determine whether the bug is actually in the IPS project code or if it is in the modifications made by the UC2 team. At this point a bug may also be filed by the UC2 team on the IPS project on opensolaris.org.

The original bug against the UC2 project is used to track when the fix is made to the version of IPS delivered by UC2. The OpenSolaris bug is used to track when the fix is made to the IPS project code. For project scheduling reasons, the UC2 project maintains a separate repository of IPS code. A particular bug may be fixed in the IPS project code or the UC2 copy in either order.

UC2 issues that are tracking an IPS project issue are marked with the IPSTRACKING keyword. IPS project issues that are of interest to the UC2 project are marked with the string "UC2" in the "whiteboard" field of the bug. (You may have to edit the bug/RFE again to be able to modify this field). Adding this string enables our UC2 project to easily report on issues and RFEs that are relevant to our project.

Adoption-related Bugs and RFEs

The Toolkit team is keen on ensuring that the toolkit it properly represented in binary distros. As such the toolkit team should file issues and RFEs with distro owners and provide advice on incorporating the toolkit.

GlassFish Issue Tracker Ensure that you add "UC2" to the whiteboard of all UC2-related issues and RFEs such that our report lists these issues and RFEs.

Issue Assignment

People filing UC2 bugs are not expected to assign the bugs to engineers.

Engineers are expected to:

• sign up to the "issues" alias such that they see all bug reports.
• self-assign themselves to relevant issues

During the Thursday I-team meeting each week, the team will review the currently unassigned bugs and dole out assignments that haven't already been made.

This page (revision-38) was last changed on 12-Aug-09 16:41 PM, -0700 by Chris Kasso.
This page was created on 07-Mar-08 13:11 PM, -0800 by Ckamps.

More info...