You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by Simon Chemouil <sc...@gmail.com> on 2015/04/15 12:17:40 UTC
[DISCUSS] Release config admin 1.8.3
Hi,
Since I've seen a bunch of these discuss / release threads lately, I
thought I'd propose one as well ;).
Jens Offenbach reported FELIX-4851[1] a few days ago which has been a
blocker for us both (separately) to use Felix SCR + Config Admin in
production.
It is a critical bug that prevents using Felix ConfigAdmin
implementation to create DS components safely. It's a tricky problem to
debug so who knows how many more experienced it? The same program can
work on some machines or OSes and not on others, depending on how much
time a bundle needs to go from states STARTING to ACTIVE (e.g, a recent
mail "ConfigAdmin 1.8.2 does not call ManagedServiceFactory updates
method" by Balazs Zsoldos in which he states his code doesn't work on
Windows but works on Linux; and works when the configuration is updated
again; that might be the cause?).
As far as I know there have been a few other fixes that would be nice to
see released, but this is the main blocker that imo justifies a release.
I'm not a committer on Felix so I can't propose to apply the patch and
cut the release, but maybe someone will step up? :-)
What do you think?
Thanks,
[1] https://issues.apache.org/jira/browse/FELIX-4851
--
Simon Chemouil
Re: [DISCUSS] Release config admin 1.8.3
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Ah yeah, that's it. Thanks for the reminder Guillaume ;)
Regards
JB
On 04/15/2015 03:15 PM, Guillaume Nodet wrote:
> Ftr, the reason is that with OSGi versions,
> 1.8.3 < 1.8.3.SNAPSHOT
> so in order to have the snapshot version being actually lower that the
> release, we need to bump the version to 1.8.4.
>
> 2015-04-15 14:19 GMT+02:00 Jean-Baptiste Onofré <jb...@nanthrax.net>:
>
>> Hi Christian,
>>
>> as a reminder, Simon is right and follow the Felix release policy.
>>
>> The SNAPSHOT is x.x.x-SNAPSHOT and the release will be x.x.x+1.
>>
>> So 1.8.3-SNAPSHOT will result to 1.8.4 release.
>>
>> I don't remember the reason why, but it's the current policy ;)
>>
>> Regards
>> JB
>>
>>
>> On 04/15/2015 02:03 PM, Christian Schneider wrote:
>>
>>> Hi Simon,
>>>
>>> your mail subject is a bit confusing. I guess you want config admin
>>> 1.8.4 released but the subject mentions 1.8.3.
>>> Do you think this is related to a bug I just created today for karaf
>>> https://issues.apache.org/jira/browse/KARAF-3668 ?
>>> It seems to be quite similar.
>>>
>>> I also consider this a very important issue as it would delay the karaf
>>> 4 release.
>>>
>>> I will try to apply your change and test if it also solves my problem.
>>>
>>> Christian
>>>
>>> On 15.04.2015 12:17, Simon Chemouil wrote:
>>>
>>>> Hi,
>>>>
>>>> Since I've seen a bunch of these discuss / release threads lately, I
>>>> thought I'd propose one as well ;).
>>>>
>>>> Jens Offenbach reported FELIX-4851[1] a few days ago which has been a
>>>> blocker for us both (separately) to use Felix SCR + Config Admin in
>>>> production.
>>>>
>>>> It is a critical bug that prevents using Felix ConfigAdmin
>>>> implementation to create DS components safely. It's a tricky problem to
>>>> debug so who knows how many more experienced it? The same program can
>>>> work on some machines or OSes and not on others, depending on how much
>>>> time a bundle needs to go from states STARTING to ACTIVE (e.g, a recent
>>>> mail "ConfigAdmin 1.8.2 does not call ManagedServiceFactory updates
>>>> method" by Balazs Zsoldos in which he states his code doesn't work on
>>>> Windows but works on Linux; and works when the configuration is updated
>>>> again; that might be the cause?).
>>>>
>>>> As far as I know there have been a few other fixes that would be nice to
>>>> see released, but this is the main blocker that imo justifies a release.
>>>>
>>>> I'm not a committer on Felix so I can't propose to apply the patch and
>>>> cut the release, but maybe someone will step up? :-)
>>>>
>>>> What do you think?
>>>>
>>>> Thanks,
>>>>
>>>> [1] https://issues.apache.org/jira/browse/FELIX-4851
>>>>
>>>
>>>
>>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [DISCUSS] Release config admin 1.8.3
Posted by Guillaume Nodet <gn...@apache.org>.
Ftr, the reason is that with OSGi versions,
1.8.3 < 1.8.3.SNAPSHOT
so in order to have the snapshot version being actually lower that the
release, we need to bump the version to 1.8.4.
2015-04-15 14:19 GMT+02:00 Jean-Baptiste Onofré <jb...@nanthrax.net>:
> Hi Christian,
>
> as a reminder, Simon is right and follow the Felix release policy.
>
> The SNAPSHOT is x.x.x-SNAPSHOT and the release will be x.x.x+1.
>
> So 1.8.3-SNAPSHOT will result to 1.8.4 release.
>
> I don't remember the reason why, but it's the current policy ;)
>
> Regards
> JB
>
>
> On 04/15/2015 02:03 PM, Christian Schneider wrote:
>
>> Hi Simon,
>>
>> your mail subject is a bit confusing. I guess you want config admin
>> 1.8.4 released but the subject mentions 1.8.3.
>> Do you think this is related to a bug I just created today for karaf
>> https://issues.apache.org/jira/browse/KARAF-3668 ?
>> It seems to be quite similar.
>>
>> I also consider this a very important issue as it would delay the karaf
>> 4 release.
>>
>> I will try to apply your change and test if it also solves my problem.
>>
>> Christian
>>
>> On 15.04.2015 12:17, Simon Chemouil wrote:
>>
>>> Hi,
>>>
>>> Since I've seen a bunch of these discuss / release threads lately, I
>>> thought I'd propose one as well ;).
>>>
>>> Jens Offenbach reported FELIX-4851[1] a few days ago which has been a
>>> blocker for us both (separately) to use Felix SCR + Config Admin in
>>> production.
>>>
>>> It is a critical bug that prevents using Felix ConfigAdmin
>>> implementation to create DS components safely. It's a tricky problem to
>>> debug so who knows how many more experienced it? The same program can
>>> work on some machines or OSes and not on others, depending on how much
>>> time a bundle needs to go from states STARTING to ACTIVE (e.g, a recent
>>> mail "ConfigAdmin 1.8.2 does not call ManagedServiceFactory updates
>>> method" by Balazs Zsoldos in which he states his code doesn't work on
>>> Windows but works on Linux; and works when the configuration is updated
>>> again; that might be the cause?).
>>>
>>> As far as I know there have been a few other fixes that would be nice to
>>> see released, but this is the main blocker that imo justifies a release.
>>>
>>> I'm not a committer on Felix so I can't propose to apply the patch and
>>> cut the release, but maybe someone will step up? :-)
>>>
>>> What do you think?
>>>
>>> Thanks,
>>>
>>> [1] https://issues.apache.org/jira/browse/FELIX-4851
>>>
>>
>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: [DISCUSS] Release config admin 1.8.3
Posted by Christian Schneider <ch...@die-schneider.net>.
Hi JB,
in fact I thought 1.8.3 was already out but we are at 1.8.2 at the
moment. So Simon was simply right :-)
I just tested the change to remove the check for the bundlle status with
the karaf issue for config admin I opened. Unfortunately
it did not help. So I think we are talking about two different problems
here.
Christian
On 15.04.2015 14:19, Jean-Baptiste Onofré wrote:
> Hi Christian,
>
> as a reminder, Simon is right and follow the Felix release policy.
>
> The SNAPSHOT is x.x.x-SNAPSHOT and the release will be x.x.x+1.
>
> So 1.8.3-SNAPSHOT will result to 1.8.4 release.
>
> I don't remember the reason why, but it's the current policy ;)
>
> Regards
> JB
>
> On 04/15/2015 02:03 PM, Christian Schneider wrote:
>> Hi Simon,
>>
>> your mail subject is a bit confusing. I guess you want config admin
>> 1.8.4 released but the subject mentions 1.8.3.
>> Do you think this is related to a bug I just created today for karaf
>> https://issues.apache.org/jira/browse/KARAF-3668 ?
>> It seems to be quite similar.
>>
>> I also consider this a very important issue as it would delay the karaf
>> 4 release.
>>
>> I will try to apply your change and test if it also solves my problem.
>>
>> Christian
>>
>> On 15.04.2015 12:17, Simon Chemouil wrote:
>>> Hi,
>>>
>>> Since I've seen a bunch of these discuss / release threads lately, I
>>> thought I'd propose one as well ;).
>>>
>>> Jens Offenbach reported FELIX-4851[1] a few days ago which has been a
>>> blocker for us both (separately) to use Felix SCR + Config Admin in
>>> production.
>>>
>>> It is a critical bug that prevents using Felix ConfigAdmin
>>> implementation to create DS components safely. It's a tricky problem to
>>> debug so who knows how many more experienced it? The same program can
>>> work on some machines or OSes and not on others, depending on how much
>>> time a bundle needs to go from states STARTING to ACTIVE (e.g, a recent
>>> mail "ConfigAdmin 1.8.2 does not call ManagedServiceFactory updates
>>> method" by Balazs Zsoldos in which he states his code doesn't work on
>>> Windows but works on Linux; and works when the configuration is updated
>>> again; that might be the cause?).
>>>
>>> As far as I know there have been a few other fixes that would be
>>> nice to
>>> see released, but this is the main blocker that imo justifies a
>>> release.
>>>
>>> I'm not a committer on Felix so I can't propose to apply the patch and
>>> cut the release, but maybe someone will step up? :-)
>>>
>>> What do you think?
>>>
>>> Thanks,
>>>
>>> [1] https://issues.apache.org/jira/browse/FELIX-4851
>>
>>
>
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
Re: [DISCUSS] Release config admin 1.8.3
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Christian,
as a reminder, Simon is right and follow the Felix release policy.
The SNAPSHOT is x.x.x-SNAPSHOT and the release will be x.x.x+1.
So 1.8.3-SNAPSHOT will result to 1.8.4 release.
I don't remember the reason why, but it's the current policy ;)
Regards
JB
On 04/15/2015 02:03 PM, Christian Schneider wrote:
> Hi Simon,
>
> your mail subject is a bit confusing. I guess you want config admin
> 1.8.4 released but the subject mentions 1.8.3.
> Do you think this is related to a bug I just created today for karaf
> https://issues.apache.org/jira/browse/KARAF-3668 ?
> It seems to be quite similar.
>
> I also consider this a very important issue as it would delay the karaf
> 4 release.
>
> I will try to apply your change and test if it also solves my problem.
>
> Christian
>
> On 15.04.2015 12:17, Simon Chemouil wrote:
>> Hi,
>>
>> Since I've seen a bunch of these discuss / release threads lately, I
>> thought I'd propose one as well ;).
>>
>> Jens Offenbach reported FELIX-4851[1] a few days ago which has been a
>> blocker for us both (separately) to use Felix SCR + Config Admin in
>> production.
>>
>> It is a critical bug that prevents using Felix ConfigAdmin
>> implementation to create DS components safely. It's a tricky problem to
>> debug so who knows how many more experienced it? The same program can
>> work on some machines or OSes and not on others, depending on how much
>> time a bundle needs to go from states STARTING to ACTIVE (e.g, a recent
>> mail "ConfigAdmin 1.8.2 does not call ManagedServiceFactory updates
>> method" by Balazs Zsoldos in which he states his code doesn't work on
>> Windows but works on Linux; and works when the configuration is updated
>> again; that might be the cause?).
>>
>> As far as I know there have been a few other fixes that would be nice to
>> see released, but this is the main blocker that imo justifies a release.
>>
>> I'm not a committer on Felix so I can't propose to apply the patch and
>> cut the release, but maybe someone will step up? :-)
>>
>> What do you think?
>>
>> Thanks,
>>
>> [1] https://issues.apache.org/jira/browse/FELIX-4851
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [DISCUSS] Release config admin 1.8.3
Posted by Christian Schneider <ch...@die-schneider.net>.
Hi Simon,
your mail subject is a bit confusing. I guess you want config admin
1.8.4 released but the subject mentions 1.8.3.
Do you think this is related to a bug I just created today for karaf
https://issues.apache.org/jira/browse/KARAF-3668 ?
It seems to be quite similar.
I also consider this a very important issue as it would delay the karaf
4 release.
I will try to apply your change and test if it also solves my problem.
Christian
On 15.04.2015 12:17, Simon Chemouil wrote:
> Hi,
>
> Since I've seen a bunch of these discuss / release threads lately, I
> thought I'd propose one as well ;).
>
> Jens Offenbach reported FELIX-4851[1] a few days ago which has been a
> blocker for us both (separately) to use Felix SCR + Config Admin in
> production.
>
> It is a critical bug that prevents using Felix ConfigAdmin
> implementation to create DS components safely. It's a tricky problem to
> debug so who knows how many more experienced it? The same program can
> work on some machines or OSes and not on others, depending on how much
> time a bundle needs to go from states STARTING to ACTIVE (e.g, a recent
> mail "ConfigAdmin 1.8.2 does not call ManagedServiceFactory updates
> method" by Balazs Zsoldos in which he states his code doesn't work on
> Windows but works on Linux; and works when the configuration is updated
> again; that might be the cause?).
>
> As far as I know there have been a few other fixes that would be nice to
> see released, but this is the main blocker that imo justifies a release.
>
> I'm not a committer on Felix so I can't propose to apply the patch and
> cut the release, but maybe someone will step up? :-)
>
> What do you think?
>
> Thanks,
>
> [1] https://issues.apache.org/jira/browse/FELIX-4851
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com