You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ace.apache.org by Marcel Offermans <ma...@luminis.nl> on 2013/04/18 16:17:48 UTC
Working towards a new release...
Hi all,
As we promised in our last board report, we are working towards a release 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 issues, 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 releases instead of the SNAPSHOTs we use now.
* Update our website: everything under user, some dev pages and (see above) release guide
An issue to discuss:
We currently have a dependency on BouncyCastle: directly because we have one unit test that uses it, and indirectly, because jclouds uses it. Jan 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 can't release one test and our jclouds support, or b) make sure we get a good answer from legal and a way forward so we can release this. Any thoughts?
Greetings, Marcel
Re: Working towards a new release...
Posted by Bram de Kruijff <bd...@gmail.com>.
On Fri, Apr 19, 2013 at 12:29 PM, Bram de Kruijff <bd...@gmail.com> wrote:
> Have we reached consensus on this matter? As I am working on LICENSE
> and NOTICE I would like to know if I need to drag in all BC/Jclouds
> notices.
>
*ping*
Nvm.. as the packaged artifacts now bundle these artifacts I went
ahead and added the (hopefully) appropriate notices. See ACE-211 for
more details.
grz
Bram
> grz
> Bram
>
> On Thu, Apr 18, 2013 at 8:03 PM, Marcel Offermans
> <ma...@luminis.nl> wrote:
>> On Apr 18, 2013, at 18:56 , Christian Vogel <ch...@cvogel.com> wrote:
>>> On 18.04.2013 16:17, Marcel Offermans wrote:
>>>> Hi all,
>>>>
>>>> As we promised in our last board report, we are working towards a release 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 issues, 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 releases instead of the SNAPSHOTs we use now.
>>>> * Update our website: everything under user, some dev pages and (see above) release guide
>>>
>>> I'll browse the open issues as well during the weekend. Could check all bundles being versioned as 1.0 during that time as well.
>>
>> Thanks Christian!
>>
>> Greetings, Marcel
>>
Re: Working towards a new release...
Posted by Bram de Kruijff <bd...@gmail.com>.
Have we reached consensus on this matter? As I am working on LICENSE
and NOTICE I would like to know if I need to drag in all BC/Jclouds
notices.
grz
Bram
On Thu, Apr 18, 2013 at 8:03 PM, Marcel Offermans
<ma...@luminis.nl> wrote:
> On Apr 18, 2013, at 18:56 , Christian Vogel <ch...@cvogel.com> wrote:
>> On 18.04.2013 16:17, Marcel Offermans wrote:
>>> Hi all,
>>>
>>> As we promised in our last board report, we are working towards a release 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 issues, 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 releases instead of the SNAPSHOTs we use now.
>>> * Update our website: everything under user, some dev pages and (see above) release guide
>>
>> I'll browse the open issues as well during the weekend. Could check all bundles being versioned as 1.0 during that time as well.
>
> Thanks Christian!
>
> Greetings, Marcel
>
Re: Working towards a new release...
Posted by Marcel Offermans <ma...@luminis.nl>.
On Apr 18, 2013, at 18:56 , Christian Vogel <ch...@cvogel.com> wrote:
> On 18.04.2013 16:17, Marcel Offermans wrote:
>> Hi all,
>>
>> As we promised in our last board report, we are working towards a release 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 issues, 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 releases instead of the SNAPSHOTs we use now.
>> * Update our website: everything under user, some dev pages and (see above) release guide
>
> I'll browse the open issues as well during the weekend. Could check all bundles being versioned as 1.0 during that time as well.
Thanks Christian!
Greetings, Marcel
Re: Working towards a new release...
Posted by Christian Vogel <ch...@cvogel.com>.
On 18.04.2013 16:17, Marcel Offermans wrote:
> Hi all,
>
> As we promised in our last board report, we are working towards a release 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 issues, 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 releases instead of the SNAPSHOTs we use now.
> * Update our website: everything under user, some dev pages and (see above) release guide
I'll browse the open issues as well during the weekend. Could check all
bundles being versioned as 1.0 during that time as well.
>
> An issue to discuss:
>
> We currently have a dependency on BouncyCastle: directly because we have one unit test that uses it, and indirectly, because jclouds uses it. Jan 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 can't release one test and our jclouds support, or b) make sure we get a good answer from legal and a way forward so we can release this. Any thoughts?
Same opinion like others already mentioned, keeping it out for this
release make sense.
>
> Greetings, Marcel
Re: Working towards a new release...
Posted by Bram de Kruijff <bd...@gmail.com>.
On Thu, Apr 18, 2013 at 4:17 PM, Marcel Offermans
<ma...@luminis.nl> wrote:
> Hi all,
>
> As we promised in our last board report, we are working towards a release 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 issues, 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 releases instead of the SNAPSHOTs we use now.
> * Update our website: everything under user, some dev pages and (see above) release guide
>
Great! I will start by taking a crack at ACE-211 and browsing the open
issues for potential show stoppers.
> An issue to discuss:
>
> We currently have a dependency on BouncyCastle: directly because we have one unit test that uses it, and indirectly, because jclouds uses it. Jan 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 can't release one test and our jclouds support, or b) make sure we get a good answer from legal and a way forward so we can release this. Any thoughts?
>
If feel the jclouds nodelauncher stuff is not really at the core of
what ACE is about (yet). For that reason I propose to simply keep it
out of the release at this point.
Regards,
Bram
> Greetings, Marcel
>
Re: Working towards a new release...
Posted by Jan Willem Janssen <ja...@luminis.eu>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 4/18/13 4:17 PM, Marcel Offermans wrote:
> An issue to discuss:
>
> We currently have a dependency on BouncyCastle: directly because
> we have one unit test that uses it, and indirectly, because jclouds
> uses it. Jan 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 can't release one test
> and our jclouds support, or b) make sure we get a good answer from
> legal and a way forward so we can release this. Any thoughts?
If it would only be used for (unit)tests, then I would propose to move
it out of the trunk into a sandbox. However, as it is also used for
the cloud-support in ACE, I'm not in favor of removing all
crypto-related code. We do want to have jclouds support built into ACE
sooner or later, so we might well take the "pain" now.
There has been some discussion on the legal-discuss ML about how to
proceed, see
<http://comments.gmane.org/gmane.comp.apache.legal.discuss/2254> and
<http://comments.gmane.org/gmane.comp.apache.legal.discuss/2349> for
an overview. There is also a JIRA issue about this as well:
<https://issues.apache.org/jira/browse/LEGAL-145>.
IIRC, the situation is that adding a clause for Apache ACE on the
legal exports-page *should* be sufficient. However, I still haven't
had confirmation about this, perhaps any of the PMCs can ping legal again?
- --
Met vriendelijke groeten | Kind regards
Jan Willem Janssen | Software Architect
+31 631 765 814
/My world is revolving around PulseOn and Amdatu/
Luminis Technologies B.V.
J.C. Wilslaan 29
7313 HK Apeldoorn
+31 88 586 46 30
http://www.luminis-technologies.com
http://www.luminis.eu
KvK (CoC) 09 16 28 93
BTW (VAT) NL8169.78.566.B.01
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRcA52AAoJEKF/mP2eHDc4a6gP/3wZSzZshHmqP3q2RuCSkuSy
yQWEkxFlrGCviCoGoe7jL680s+1sp0YG3Xae2RCpBoYHNn+7X83rA8Tr/U5bdvl9
9av+VwkcdZgON4XioR9qY+okH/tf+dWtMjLoktbHPJG/VGaw4OKnmzifmHdXm70R
YZT/43CVxHuuy58baAVKTDvp6RUmQk4rbZRAU6mq4SUHUKHevLF0uC81Sgxg2Gn2
X8btksjo1SFDtp3ROnOY2wJA5Hvcf6Iwo0GJ7Jh3geXrp2E9/7rFQMG7GwxxE/4G
ethVu2U8JYijh1gmk06+S8nRDVWzzTC2L6DTI4EiHF97fCAdMojp8rg3Mi2DQCkF
8cKww6NTb8MZWLmzW+dBkfW0pszW6mWu/vpoLsQVVduziG12IRmDEa5CEAaZEP6Y
XAZMuqErlL+Lt+M+YydXvBh2470R7IAQdZ1+1FaA5KU/hLgCs3+Y8gBgrlkWoQcw
y/FmkzN0i5kZKHx4ExTquffLJEy5stWu9x0hPW2+5RlSJjSAZiv/3bCc7/RLdfQr
gLf3mFFO+bdej//KlFbRybHbRiPivrrD34WKXb1bKTU2jqrBZf4D8JUnGsx4/v5o
tF/yjQa33Xls9EzcuasyZ1nLVjwZTL0Uyhba7i+xjti99vBVYg38ow4E2euoI6+l
hvQ8u8hJxj9IEIb6Kn9l
=jk9r
-----END PGP SIGNATURE-----
Re: Working towards a new release...
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
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
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 release 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 issues, 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 releases instead of the SNAPSHOTs we use now.
> * Update our website: everything under user, some dev pages and (see above) release guide
>
> An issue to discuss:
>
> We currently have a dependency on BouncyCastle: directly because we have one unit test that uses it, and indirectly, because jclouds uses it. Jan 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 can't release one test and our jclouds support, or b) make sure we get a good answer from legal and a way forward so we can release this. Any thoughts?
>
> Greetings, Marcel
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com