celix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gerrit Binnenmars <gerritbinnenm...@gmail.com>
Subject Re: report & releases
Date Wed, 13 May 2015 19:51:38 GMT
Hello all,

Good to hear that a release is planned. Just some questions for the release
- Will the dependency manager be included in the release?
- What about the config manager and the event admin?
- Will remote service discovery with ETCD be included?
- How mature is Celix without APR, how well is it tested?
- Where can we help with the above points

Greetings Gerrit

> Hi Konstantin,
> 2015-05-07 19:48 GMT+02:00 Konstantin Boudnik <cos@apache.org>:
>> I have suggested this before, I think, but just in case: it might make
>> sense
>> to consider the use of http://reporter.apache.org/ for the initial draft
>> of
>> the report info...
> I've somehow missed your other mail, thanks for the list, looks really
> useful!
>> +1 on adding the points from below.
> +1 from me as well.
> I'd like to mention a timeframe for it as well, both for the report, and
> for our self.
> I don't have any major issues atm for the new release, I'd like to have all
> components free of APR.
> @Pepijn: Could you fasttrack your other request for "cog" as well, so that
> we can mention it as well?
>    Cos
>> On Thu, May 07, 2015 at 11:17AM, Pepijn Noltes wrote:
>>> Hi All,
>>> The board has requested an additional report from Celix, because the
>>> previous one was to simplistic.
>>> If you think there are any items we should mentioned for the upcoming,
>>> please reply. For now I have the following items:
>>> * Preparing for a new release (see below)
>>> * Presentation @ Luminis devcon
>>> Given that an additional report has een requested and that some of us
>>> discussed a new release f2f I want to propose to start working for a new
>>> release (2.0.0).
>>> Primary goal IMO is to remove APR and because we already did this for the
>>> most bundles I do not see any major issues preventing a new release.
>>> Please reply with any issues you think should be addressed in up coming
>>> release. If no major issues are mentioned I will create a release branch
>> to
>>> work on.
>>> Greetings,
>>> Pepijn

View raw message