[modules-discuss] How to raise sunbugs?
hal.hildebrand at oracle.com
Thu Jan 10 14:27:21 PST 2008
On Jan 10, 2008, at 2:41 PM, Glyn Normington wrote:
> On Jan 10, 2008, at 12:09 PM, Andreas Sterbenz wrote:
>> Glyn Normington wrote:
>>> What value of the product/category field should be used when
>>> raising a bug against the modules project?
>> For now it would be easiest to report any bugs or other
>> implementation issues here. The bugs.sun.com mechanism was designed
>> for released products and does not work well for OpenJDK.
>> Eventually we will have a bug database that all community members
>> have full access to, but we are not there yet.
>> Is there something you would like to report?
>> For spec bugs and other issues with the JSR 277 and JSR 294 specs,
>> please continue to use the the JCP feedback channels such as
>> jsr-277-comments at jcp.org and jsr-294-comments at jcp.org .
> Hi Andreas
> I can no longer commit time to tracking the JSR 277 mailing list so
> I'd like to formally log the requirement for JSR 277 to interoperate
> with JSR 291 as an enhancement request. There are a number of
> benefits of using a bug to do this:
> 1. I can subscribe to the bug and know I will be notified if and when
> it is fixed (I will very likely remain interested in the outcome of
> the bug but not in the detailed process in deriving a solution)
> 2. a bug will not float off into obscurity unlike archived mailing
> list threads
> 3. a bug is a good way of tracking the status of "to do" items for
> any project.
> This mailing list and the JCP feedback aliases do not provide these
> benefits plus I've already mentioned the interop. issue many times on
> the JSR 277 mailing list and there is still no formal way of tracking
> the progress of the item.
> modules-discuss mailing list
> modules-discuss at openjdk.java.net
More information about the modules-discuss