Check that OSGi spec implementation bundles pass CT before release

[Thomas Watson <tj...@gmail.com>]

It has come to my attention that the latest SCR release 2.1.14 does not
pass the latest OSGi R7 CT.  Do we have a policy to run the proposed
release against the OSGi CT it is trying to implement before finalizing a
release?  If not, should it be required to pass or at least provide an
explanation if it doesn't before allowing the release?

Tom

Re: Check that OSGi spec implementation bundles pass CT before release

[Raymond Auge <ra...@liferay.com>]

+1

- Ray

On Sun, Feb 3, 2019 at 7:37 AM Carsten Ziegeler <cz...@apache.org>
wrote:

> I think our policy should really be that SCR and all our other spec
> implementations pass the CT - and if not, there should be a good reason
> for not doing it and this should be documented
>
> Regards
>
> Carsten
>
>
> Thomas Watson wrote
> > It has come to my attention that the latest SCR release 2.1.14 does not
> > pass the latest OSGi R7 CT.  Do we have a policy to run the proposed
> > release against the OSGi CT it is trying to implement before finalizing a
> > release?  If not, should it be required to pass or at least provide an
> > explanation if it doesn't before allowing the release?
> >
> > Tom
> >
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziegeler@apache.org
>


-- 
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)

Re: Check that OSGi spec implementation bundles pass CT before release

[Carsten Ziegeler <cz...@apache.org>]

I think our policy should really be that SCR and all our other spec 
implementations pass the CT - and if not, there should be a good reason 
for not doing it and this should be documented

Regards

Carsten


Thomas Watson wrote
> It has come to my attention that the latest SCR release 2.1.14 does not
> pass the latest OSGi R7 CT.  Do we have a policy to run the proposed
> release against the OSGi CT it is trying to implement before finalizing a
> release?  If not, should it be required to pass or at least provide an
> explanation if it doesn't before allowing the release?
> 
> Tom
> 
--
Carsten Ziegeler
Adobe Research Switzerland
cziegeler@apache.org

Re: Check that OSGi spec implementation bundles pass CT before release

[Thomas Watson <tj...@gmail.com>]

It is related to https://issues.apache.org/jira/browse/FELIX-6044 which I
am working on a fix for (don't pay attention to the PR there just yet).
But even with my fix to make sure service references are ungotten the tests
do not pass.  On the other hand if I revert the fix to
https://issues.apache.org/jira/browse/FELIX-5974 (fixed in version 2.1.14)
the CT will pass again.  We need to evaluate the CT tests because it is
possible it is a bug in the CT for testing prototype scope.

Tom.

On Sun, Feb 3, 2019 at 9:49 AM Carsten Ziegeler <cz...@apache.org>
wrote:

> Tom, can you please file an issue with what is failing?
>
> Do you know if 2.1.14 is the first release failing?
>
> Thanks
>
> Carsten
>
>
> Thomas Watson wrote
> > It has come to my attention that the latest SCR release 2.1.14 does not
> > pass the latest OSGi R7 CT.  Do we have a policy to run the proposed
> > release against the OSGi CT it is trying to implement before finalizing a
> > release?  If not, should it be required to pass or at least provide an
> > explanation if it doesn't before allowing the release?
> >
> > Tom
> >
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziegeler@apache.org
>

Re: Check that OSGi spec implementation bundles pass CT before release

[Carsten Ziegeler <cz...@apache.org>]

Tom, can you please file an issue with what is failing?

Do you know if 2.1.14 is the first release failing?

Thanks

Carsten


Thomas Watson wrote
> It has come to my attention that the latest SCR release 2.1.14 does not
> pass the latest OSGi R7 CT.  Do we have a policy to run the proposed
> release against the OSGi CT it is trying to implement before finalizing a
> release?  If not, should it be required to pass or at least provide an
> explanation if it doesn't before allowing the release?
> 
> Tom
> 
--
Carsten Ziegeler
Adobe Research Switzerland
cziegeler@apache.org