Hi all,

Thanks for your votes (and checks) so far.

I am afraid, that I have to cancel the Apache Felix Configuration Admin
Service 1.2.2 release:

Further tests of the 1.2.2 release candidate with highly concurrent test
suites have shown that there is a slight but real chance for a reace
condition (FELIX-1542 [1], already described earlier in FELIX-1146 but
not really fixed then).

In addition the OSGi Alliance asked me to use more recent
org.osgi.service.cm classes for export (FELIX-1541 [2]).

Since the OSGi Alliance is planning to include the Felix Configuration
Admin Service implementation as the Configuration Admin Service
reference implementation of the upcoming Release 4.2 specification it is
very important to have an official release passing all tests flawlessly.

Thus, I consider the 1.2.2 release failed, cancel the vote and will
prepare a new release candidate for an 1.2.4 release soon.

The issues currently fixed for 1.2.2 are moved to be fixed in 1.2.4. The
1.2.2 tag will be removed.

Regards
Felix

[1] https://issues.apache.org/jira/browse/FELIX-1542
[2] https://issues.apache.org/jira/browse/FELIX-1541

Felix Meschberger schrieb:
> Hi,
> 
> Testing the Configuration Admin 1.2.0 revealed a bug in the permission
> checking code causing the bundle to fail the OSGi TCK tests. For this
> reason, I come up with yet another release...
> 
> We solved 1 issues in this release:
> https://issues.apache.org/jira/secure/BrowseVersion.jspa?versionId=12314169
> 
> There are no outstanding issues.
> 
> Staging repository:
> https://repository.apache.org/content/repositories/felix-staging-038/
> 
> You can use this UNIX script to download the release and verify the
> signatures:
> http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
> 
> Usage:
> sh check_staged_release.sh 038 /tmp/felix-staging
> 
> Please vote to approve this release:
> 
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
> 
> This vote will be open for 72 hours.
> 
> Thanks and Regards
> Felix
> 
> 

Reply via email to