Differences between revisions 14 and 15
Revision 14 as of 2007-09-12 08:28:24
Size: 2354
Editor: marbro
Comment:
Revision 15 as of 2007-09-12 18:57:51
Size: 2885
Editor: c-76-31-215-166
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:

log4php incubation was restarted in July. Three new committers have been added and a JIRA project has been set up for bug tracking. A maven 2 generated web site has been published to http://incubator.apache.org/log4php. The source tree was reorganized and an initial pass at migration to PHP 5 was committed in July, but there has been little recent activity (possibly due to vacations) and no published development plan. In the next period, the development team needs to establish development plan for an initial snapshot.

September 2007 Reports (see ReportingSchedule)

These reports are due to the Incubator PMC by 12 September 2007


log4php

log4php incubation was restarted in July. Three new committers have been added and a JIRA project has been set up for bug tracking. A maven 2 generated web site has been published to http://incubator.apache.org/log4php. The source tree was reorganized and an initial pass at migration to PHP 5 was committed in July, but there has been little recent activity (possibly due to vacations) and no published development plan. In the next period, the development team needs to establish development plan for an initial snapshot.


Sling


Sanselan


River

River is aimed at the development and advancement of the Jini technology core infrastructure. Jini technology is a service oriented architecture that defines a programming model which both exploits and extends Java technology to enable the construction of secure, distributed systems which are adaptive to change.

The last artifact, the QA framework, has been voted in and landed in SVN. An automated build environment has been put in place and finally all outstanding issues from the Sun issue tracking system have been manually migrated in a large group effort to JIRA.

The River community agreed to do a first release to show the larger Jini community it is serious in its efforts. It ain't a very ambitious release and will be almost an equivalent of the last release done by Sun but includes the ServiceUI code. This release also allows the River community to get acquainted and find out about many of the ASF procedures. No transformation of the com.sun.jini namespace to org.apache.river will take place, but the River community is aware it has to do that and will find an opportune moment for that during incubation.

Perhaps as a side effect of the ambitions for the first release discussions on new functionality don't seem to take off very well, but that time is used to discuss the process the River project believes it needs to establish. Although most committers have expressed their desire to have code-review before code is committed, due to complexity of the codebase and the difficulty to test many aspects properly, it seemed hard to decide to what extent to enforce that. A proposal for the initial process guidelines is up for a vote now that combines RTC for public API and CTR for implementation details.

US export regulations apply to the River codebase and although discussed in the very early days we were living under the (wrong) impression that complying with them only applied when we were about to release. We are aware now that we should have taken care of it even before the code landed in SVN and we are going to comply as soon as possible.


TripleSoup


September2007 (last edited 2009-09-20 23:07:06 by localhost)