Mailing-List: contact celix-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: celix-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of a.broekhuis@gmail.com
 designates 209.85.214.47 as permitted sender)
MIME-Version: 1.0
Date: Thu, 15 Nov 2012 15:49:04 +0100
Message-ID: 
 <CA+T-u8cZ6hdg2UMSJZ8gt6kj3jO1hXg7WFLm88xryhLZfYGx1w@mail.gmail.com>
Subject: Working towards a next release
From: Alexander Broekhuis <a.broekhuis@gmail.com>
To: celix-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=0015174a05d0aa3a2e04ce89c087

--0015174a05d0aa3a2e04ce89c087
Content-Type: text/plain; charset=ISO-8859-1

Hi all,

Even though the first release hasn't been accepted, I do like to know what
a next release should fix or implement.

The first release was done mostly for creating a release. This is important
for the incubator, but maybe even more to get peoples attention. Having a
release makes it easier to try/test Celix.
But for the next release I think we can focus more on the content of the
release. Some topics I can think of:

* Finish APR usage in the framework. APR is already being used for the most
part of the framework, but still not all code has been updated.
* APR usage in bundle can also be updated. Some bundles do use it, but most
not yet.
* Remote Services implementation needs work. Things like protocol usage,
pluggable solution for different protocols, tests etc.

Besides technical stuff, there are also some other things we should start
doing:
* Track issues in Jira
  In the past we did use Jira for some bugs/issues, but mostly ignored it
when working on the source. For a next release I think we should start
using Jira to keep track of progress and a changelog.
* Update documentation
  We need more documentation, on building and using Celix, but also on the
design/implementation as well ass release guides etc.

Any/All ideas are welcome! Nothing has been decided, so all options are
open.

Just a reminder, if the first release needs to be redone, a new release
will be made with the current state of the code. So "next release"
doesn't necessarily mean 0.0.2 or even 0.0.3...

-- 
Met vriendelijke groet,

Alexander Broekhuis

--0015174a05d0aa3a2e04ce89c087--