Mailing-List: contact dev-help@ace.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ace.apache.org
Received-SPF: error (athena.apache.org: local policy)
Message-ID: <5170104E.8000108@nanthrax.net>
Date: Thu, 18 Apr 2013 17:25:02 +0200
From: =?ISO-8859-1?Q?Jean-Baptiste_Onofr=E9?= <jb@nanthrax.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: dev@ace.apache.org
Subject: Re: Working towards a new release...
References: <12E91885-5E01-4BAC-812F-436FDD002319@luminis.nl>
In-Reply-To: <12E91885-5E01-4BAC-812F-436FDD002319@luminis.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

It sounds good to me.

I postpone the Karaf and Kalumet support to the next ACE release.

Regarding BouncyCastle, I would remove BC from the release. We can=20
document how to enable support of jclouds.

Regards
JB

On 04/18/2013 04:17 PM, Marcel Offermans wrote:
> Hi all,
>
> As we promised in our last board report, we are working towards a relea=
se of ACE (I propose to call that 1.0). To start working towards that, I =
would like to start by asking everybody if there are blocking issues that=
, according to them, have to be fixed before we can cut a release? If so,=
 this is the time to discuss them!
>
> Also, there are a couple of things we still need to address. I tried to=
 make a list, and as soon as we agree on them I will convert that to issu=
es, link them to a version in Jira so we have a goal to work towards.
>
> My list:
>
> * Make sure all bundles are versioned as 1.0
> * Make sure all exported packages are versioned as 1.0
> * Complete all relevant bundle headers / metadata
> * Ensure that src-build.xml and bin-build.xml work and that we can do a=
 "source only" release.
> * Finish release guide (ACE-106)
> * Review and improve NOTICE and LICENSE (ACE-211)
> * Release autoconf, deploymentadmin in Apache Felix and use these new r=
eleases instead of the SNAPSHOTs we use now.
> * Update our website: everything under user, some dev pages and (see ab=
ove) release guide
>
> An issue to discuss:
>
> We currently have a dependency on BouncyCastle: directly because we hav=
e one unit test that uses it, and indirectly, because jclouds uses it. Ja=
n Willem looked into this and what it would mean to release this a while =
ago, but I believe our question to legal regarding this is still open. We=
 have two options: a) remove BouncyCastle from the release, meaning we ca=
n't release one test and our jclouds support, or b) make sure we get a go=
od answer from legal and a way forward so we can release this. Any though=
ts?
>
> Greetings, Marcel
>

--=20
Jean-Baptiste Onofr=E9
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com