Skip to main content

Updated priorities of java3d Issues (bugs)

1 reply [Last post]
kcr
Offline
Joined: 2004-03-17

As part of our planning for the 1.3.2 release, we have updated the priorities of many of the Java 3D Issues. You can query the list of issues at:

https://java3d.dev.java.net/servlets/ProjectIssues

We plan to fix all P1-P3 bugs before the final release of 1.3.2, we may fix some P4 bugs (no guarantees), and we do not plan to fix any P5 bugs. While we would like to fix more bugs, we realize that the most important thing for moving Java 3D forward is to get the 1.4 release started with programmable shaders (more on this front later this week or early next week).

If there are P4 or P5 bugs that any of you would like to see fixed, especially those bugs that are unassigned (i.e., their owner is issues@java3d), you are encouraged to help by analyzing your favorite bug, and updating the bug report with a suggested fix, or better yet, by fixing the bug and sending us a patch. Note that in either case you will need to send us a signed Joint Copyright Assignment (JCA). We regret that we are unable to integrate patches or even look at suggested fixes containing source code from anyone who has not signed the JCA. Please see the "Contributing to Java 3D Projects" page on the java3d web site at:

https://java3d.dev.java.net/contribute.html

Thanks!

-- Kevin

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
kcr
Offline
Joined: 2004-03-17

Those of you who are subscribed to issues@java3d (or who have checked the Issue Tracker in the last 3 hours or so) will have noticed that Chien has been busy submitting several new Issues today.

These represent the 16 bugs out of the roughly 140 open bugs/RFEs filed over the past 6 years in Bug Parade (aka BugTraq) that we have decided to transfer over to java.net for tracking. There are 4 bugs that we are still evaluating (to see whether they are already fixed and/or whether they are real bugs) so a couple more may show up in the next week or so. Most of these are being filed as P4 or P5 meaning that they may or may not make the 1.3.2 release, depending on how much time / help we get.

We have no plans at this time to look at any of the remaining 120 or so bugs in Bug Parade. If we've left off a favorite bug of yours, please feel free to dig it up from Bug Parade and resubmit it on java.net. :)

The odds of any P4 or P5 bug being fixed will be greatly increased if we get help from the community in narrowing down the root cause of the bug. Better still, a suggested fix or patch would be appreciated for bugs whose fix is localized, but often tracking down the exact cause is the most time consuming part. We will appreciate any help we get.

-- Kevin