incubator-kato-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steve Poole <>
Subject Re: June 2011 incubator report
Date Tue, 07 Jun 2011 11:45:24 GMT
On Thu, Jun 2, 2011 at 10:37 AM, Stuart Monteith <> wrote:

> Hello,
>        It is that time for our quarterly status report. In the past quarter
> Steve posted that there had been discussions with Oracle regarding JSR-326
> and this project, but so far nothing conclusive has occurred. There was an
> indication that Oracle was going to say something, but nothing came of that
> within this reporting period.
> Steve - can you update us with the current situation with Oracle - have you
> gotten any conclusions from them? And your views on the continuation of this
> project?

Status is :

10:   Bug Oracle execs
20:   They say "please wait"
30:    sleep (n days)
40:   goto 10

To be fair "n" is falling and It's not like Oracle have said no. Currently
the loop doesn't seem to have an exit though.   My best guess is that "n" is
now looking to be about 60 days before we get a definite answer.

I say we make this the last go round.   I will talk within IBM about the
future of JSR 326 without Oracle's support.  If IBM still wants to continue
the JSR then great - otherwise, assuming that they want to continue funding
developers, we work out a smaller development plan that takes Kato to
graduation.  ( We've got some great stuff but its all alpha level.)

> I've not written a status report yet, but I'll do so in time for next
> Wednesday.
> Regards,
>        Stuart
> P.S. The previous report said:
> Kato
> Kato was accepted into the Incubator on 6 November 2008.
> Kato is a project to develop the Specification, Reference Implementation,
> and TCK for JSR 326: the JVM Post-mortem Diagnostics API.
> Recent Activity:
> * While Oracle has expressed a continued interest in the JSR-326, there has
> been no change in the podling's status since the last report in June.
> * As in June, the project is effectively paused until Oracle's involvement
> in the Kato podling has been clarified. The credibility of the standard
> relies on there being more than one major Java VM vendor involved.
> The following is planned for next reporting period:
> * To be determined once Oracle's involvement has been established.
> Before this project can graduate we need to encourage more participation in
> the project and grow the community.
> Signed off by mentor:


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message