Author: buildbot
Date: Tue Apr 12 17:59:40 2011
New Revision: 788250

Log:
Staging update by buildbot

Modified:
    
websites/staging/celix/trunk/content/celix/community/boardreports/boardreports.html

Modified: 
websites/staging/celix/trunk/content/celix/community/boardreports/boardreports.html
==============================================================================
--- 
websites/staging/celix/trunk/content/celix/community/boardreports/boardreports.html
 (original)
+++ 
websites/staging/celix/trunk/content/celix/community/boardreports/boardreports.html
 Tue Apr 12 17:59:40 2011
@@ -105,6 +105,22 @@
                         <p>To monitor incubator project, the Apache Software 
Foundation board holds monthly meetings.
 For these meetings a board report must be delivered to the Incubator PMC.</p>
 <p>On this page the reports for Celix are shown.</p>
+<h2 id="2011-04httpwikiapacheorgincubatorapril2011"><a 
href="http://wiki.apache.org/incubator/April2011";>2011-04</a></h2>
+<p>= Celix =</p>
+<p>Celix is an implementation of the OSGi Specification in C.</p>
+<p>Celix entered incubation on November 2, 2010.</p>
+<p>During the EclipseCon a talk was given over Celix, also spoke with several 
OSGi 
+people who are interested in the progress, especially related to Universal 
OSGi 
+(which details specification and requirements for OSGi in other languages).
+During the last few weeks work has been done to get rid of memory leaks and 
null 
+pointers.
+Currently we are looking at the requirements/details for bundle deployment and 
+updating, possibly in combination with Apache Ace.</p>
+<p>Most important issues are:</p>
+<p>Define a status overview of what is and isn't working.
+Move all "sub" project to the new structure.
+Use APR for all file handling, threading etc.</p>
+<p>Signed off by mentor:</p>
 <h2 id="2011-02httpwikiapacheorgincubatorfebruary2011"><a 
href="http://wiki.apache.org/incubator/February2011";>2011-02</a></h2>
 <p>= Celix =</p>
 <p>Celix is an implementation of the OSGi Specification in C.</p>


Reply via email to