What the board has decided about this committee or office, and the reports it filed, most recent first. Generated from the published minutes.
These categorised views are best effort. They are read from the published minutes by a program, and what it can attribute to a committee depends on how each resolution happens to be worded — so a page may be incomplete, and nothing here overrides the minutes themselves. The raw minutes are the source of truth.
Please note. The board approves the minutes of a meeting at the meeting after it, and they are published then - so the most recent meeting is not usually here. ASF Members can read the draft in the board's own repository until it is.
[raw] the published minutes, which are the record. [main index]
(Report by the Shepherd) Sadly, this podling seems to have expired. There has been no traffic on any mailing lists since last report, and the last words were to the effect that no one is left with time to spend. The IPMC will most likely wind this up and store it into the attic before the next report. Signed off by mentor: Shepherd: Benson Margulies
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: - Oracle finally stated its position on JSR 326 and the Kato project. In short, other technologies are a higher priority, and there is a limited audience for the API. - There was a lot of discussion on the status of this project and the reporting of that status. - Robert Burrell Donkin announced his resignation from the IPMC and as mentor for this project. - There was some discussion about the future of the project, but nothing concrete. The following is planned for next reporting period: - Decide in what form the podling should continue, if at all. Before this project can graduate we need to encourage more participation in the project and grow the community. Signed off by mentor: ant
*** DID NOT REPORT! ***
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: * Some JIRA items have been raised regarding the command-line tomcat commands. * Discussions with Oracle have been continuing. An individual from Oracle has been identified, but no discussions have come from this yet. The following is planned for next reporting period: * Decide in what form the podling should continue, if at all. Before this project can graduate we need to encourage more participation in the project and grow the community.
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: * Some JIRA items have been raised regarding the commandline tomcat commands. * Discussions with Oracle have been continuing. An individual from Oracle has been identified, but no discussions have come from this yet. The following is planned for next reporting period: * Decide in what form the podling should continue, if at all. Before this project can graduate we need to encourage more participation in the project and grow the community.
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: * There had been some discussion with Oracle regarding the future of JSR-326 in May this year, a definitive statement is expected from them in July. * The question has been raised as to the future of JSR-326 and the Apache Kato podling, the options being to keep both or continue only with one of them. The following is planned for next reporting period: * Decide in what form the podling should continue, if at all. Before this project can graduate we need to encourage more participation in the project and grow the community. Sadly Kato seems still to be set on a holding pattern
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.
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: * A JVMTI agent has been contributed by Paul Sobek along with an implementation of the API. * The JSR specification document has been written and is building. * The JSR specification has been submitted to the JCP as an EDR. * The project is being built on the ASF's hudson server. The following is planned for next reporting period: * Our first release of the RI, demos and TCK. Before this project can be graduated we need to produce a usable implementation of the API and more useful tools to encourage adoption and participation of a much needed community.
