[News.eclipse.foundation] [GOVERNANCE] - Mr. Kent Johnson (IBM) Obfuscat

[ilias <ilias@xxxxxxxxxxxxx>]

I ask the relevant organs within the eclipse foundation to intervent.

Mr. Kent Johnson (IBM) manipulates filed issues within JDT.Core in a way 
which results in a false reflection of the current status of the issues 
and their dependencies.

-

Reviewing the J2SE 5.0 implementation status, i've found information 
that was out of synch:

this huge "Issue":
https://bugs.eclipse.org/bugs/show_bug.cgi?id=36938

an outdated and inprecise plan, mostly without links to filed known 
issues within bugzilla:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=81471#c3

https://bugs.eclipse.org/bugs/show_bug.cgi?id=50443#c13

-

This "out-of-synch" problem would be reduced, if the plan was created 
out of the bugzilla database, as suggested in this thread:

[PROJECT] [BUGZILLA] - Dependency Feature
http://www.eclipse.org/newsportal/article.php?id=217&group=eclipse.foundation

-

I've entered within Buzilla (the eclipse Issue Tracking System) the 
following Issue [using current title, initial title was different]:

[Bug 80775] JSR-176 J2SE 5.0 (Tiger) Release Contents
https://bugs.eclipse.org/bugs/show_bug.cgi?id=80775

-

this Issue depends on the implementation (within JDT.Core) of the 
following JSR's:

JSR-201 (contains several parts), JSR-175, JSR-014

Whilst using the dependency-feature of Bugzilla, I've filed (after 
looking for duplicates) the further top-level Issues:

JSR-014 Generics
https://bugs.eclipse.org/bugs/show_bug.cgi?id=80777

Implement JSR-175 Metadata Facility (Annotations)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=80776

Implement JSR-201 (enumerations, autoboxing, varargs, enhanced loops, 
static imports)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=81470

Implement JSR-201, part "static imports"
https://bugs.eclipse.org/bugs/show_bug.cgi?id=81593

-

I've interlinked existing issues (and the newly filed documented known 
issues) with use of the dependency feature.

-

You will see within the issues, that Mr. Kent Johnson (IBM) _closes_ the 
issues as INVALID - and as the last action, removing dependencies 
without any justifying comments.

What happens when a users searches for JSR-175 within Bugzilla?

Or JSR-176?

He finds obfuscated data.

-

It looks to me that the team is not intrested in real transparency, but 
just in keeping the open issues as low as possible.

Until the JSR's were fully implemented within JDT.Core, the filed Issues 
remain _open_.

This is a _fact_ - and I ask you to keep the Issue tracking transparent 
and honest, whilst reflecting the _real_ status.

I've not the time to continue those close/open games from Mr. Kent 
Johnson (IBM).

-

"JSR-176 J2SE 5.0 (Tiger) Release Contents" are far away from beeing 
implemented fully within eclipse JDT.Core - and Bugzilla should reflect 
the correct status.

Any JSR is worth a dedicated Issue within Buzilla, thus users hit on 
this information after a search.

.

--
http://lazaridis.com