Format for JDK 6/7 changeset comments?
Kelly.Ohair at Sun.COM
Tue Nov 6 10:22:39 PST 2007
I agree that we need a completely open bug database, and I do think that
will happen. For the time being I have been trying to get people to use
the more open parts of the existing bug database, parts that are at least
visible to the outside world (Description/Evaluation etc.).
But let's not make a decision on the changeset comment based on the existing
bug database situation, one that will be changing in the future.
At least that's my thinking.
Neal Gafter wrote:
> On Nov 6, 2007 9:03 AM, Kelly O'Hair <Kelly.Ohair at sun.com
> <mailto:Kelly.Ohair at sun.com>> wrote:
> I favor keeping it short and sweet, and use the bug database for all
> other information.
> A place that can be corrected and added to over time.
> Agreed. This assumes the bug database is open for writing by committers
> and reading by the larger community.
> Sun is in a position to control the bug database to hide bugs that
> describe security problems. That is fine and I expect it to continue,
> but I have seen a number of cases of bugs being hidden because the
> problems they describe are embarrasing. Unfortunately (1) such problems
> then don't get fixed, and (2) even if it is too late to fix the issues,
> by sweeping them under the rug we don't learn from past mistakes.
> My point is that in order for committers to have confidence in this
> approach, Sun should give up some of their editorial/censorship role
> over the bug database.
More information about the discuss