Hi Carsten, On 13 July 2015 at 15:50, Carsten Ziegeler <[email protected]> wrote: >> However you are right that no Apache release should contain >> provisional OSGi API. Currently the Enterprise R6 release is available >> as Proposed Final Draft [1]. It is highly unlikely that the >> specification will change while it's being voted on by the OSGi >> members so personally I don't see a big issue releasing Aries Async at >> this stage, but if others think we should wait until the OSGi release >> voting has concluded then we can do that. In that case we'll have to >> delay this release to early August... >> > Sorry for not checking, so the release does not contain the OSGi API ? I > guess then you're fine in any case.
No, you were right, this code does contain a copy of the OSGi Promises and Async services APIs. So if we were to play exactly by the Felix rules, then this release would be premature. I'm fine either way. I thought it would be nice to have an Async release that people could start using, the risk of change in the OSGi spec being really very low. But, it's not yet released. The OSGi member voting period takes quite a while. Given that this concern has brought up I think I'll better wait. People can still use Async from trunk after building it themselves. Cheers, David
