Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Message-ID: <455E74EB.5070309@apache.org>
Date: Fri, 17 Nov 2006 18:50:19 -0800
From: Stefano Mazzocchi <stefano@apache.org>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: harmony-dev@incubator.apache.org
Subject: [heads up] the importance of 'reversed' API completion
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

As shown in the graphical history of harmony at

 http://67.86.14.213:10000/harmony.png

we are currently at 96.39% of API completion (if we don't count the
SerialID differences and the final static values), and we are
continuously growing there.

But there is also another index, the "reversed" API completion that
measures how much code the RI didn't implement that we did.

Here, a 100% means that all that code that we have implemented in those
public packages is available in the RI.

In order to achieve WORA, the TCK mandates that both direct and reverse
completion be 100%.

I suggest we start to pay attention to both.

Here is a reverse-japi report:

 http://67.86.14.213:10000/results/latest/reverse-japi.html

-- 
Stefano.