Re: [VOTE] Release Apache Felix cm.json 1.0.6

[Raymond Auge]

+1

- Ray

On Sun, Jan 31, 2021 at 7:17 AM Carsten Ziegeler 
wrote:

> I would like to call a vote on the cm.json 1.0.6 release
>
> We solved one regression:
>
> https://issues.apache.org/jira/browse/FELIX-6383
>
>
> Staging repositories:
> https://repository.apache.org/content/repositories/orgapachefelix-1368
>
> You can use this UNIX script to download the release and verify the
> signatures:
> https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
>
> Usage:
> sh check_staged_release.sh 1368 /tmp/felix-staging
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>
> Regards
> Carsten
>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>


-- 
*Raymond Augé* (@rotty3000)
Senior Software Architect *Liferay, Inc.* (@Liferay)
OSGi Fellow

Re: [VOTE] Release Apache Felix cm.json 1.0.4

[Raymond Auge]

+1

- Ray

On Tue., Jan. 26, 2021, 7:56 a.m. Jean-Baptiste Onofre, 
wrote:

> +1 (binding)
>
> Regards
> JB
>
> > Le 26 janv. 2021 à 12:18, Carsten Ziegeler  a
> écrit :
> >
> >
> > I would like to call a vote on the cm.json 1.0.4 release
> >
> > We solved one issue:
> >
> > https://issues.apache.org/jira/browse/FELIX-6380
> >
> >
> > Staging repositories:
> > https://repository.apache.org/content/repositories/orgapachefelix-1367
> >
> > You can use this UNIX script to download the release and verify the
> signatures:
> > https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh 1367 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > Regards
> > Carsten
> > --
> > Carsten Ziegeler
> > Adobe Research Switzerland
> > cziege...@apache.org
>
>

Re: [VOTE] Apache Felix Dependency Manager Release r16

[Raymond Auge]

+1

- Ray

On Thu., Jan. 21, 2021, 1:54 a.m. Carsten Ziegeler, 
wrote:

> +1
>
> Carsten
>
> Am 20.01.2021 um 16:16 schrieb Pierre De Rop:
> > Hello everyone;
> >
> > I would like to call for a vote on the Dependency Manager top level
> release
> > r16.
> >
> > Release notes:
> >
> > ** Bug
> > * [FELIX-6180] - Component initialization error message get's
> printed to
> > sysout instead of logged to LogService
> >
> > ** Improvement
> > * [FELIX-6278] - Update Dependency Manager with latest bndtools
> version
> >
> > You can use this UNIX script to download the release and verify the
> > signatures:
> >
> >
> https://github.com/apache/felix-dev/blob/master/dependencymanager/release/check_staged_release.sh
> >
> > Usage:
> >
> >sh check_staged_release.sh r16 /tmp/felix-staging
> >
> > This script, unlike the original Felix check_stage_release.sh, is
> specific
> > to the Dependency Manager release process (see FELIX-4818) and will
> > download staging from https://dist.apache.org/repos/dist/dev/felix
> instead
> > of http://repository.apache.org/content/repositories.
> >
> > To rebuild the DM binaries from the source, jdk8 must be used, and you
> can
> > refer to:
> >
> >
> https://github.com/apache/felix-dev/blob/master/dependencymanager/release/resources/src/README.src
> >
> > Please cast your votes 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 & regards;
> > /Pierre
> >
>
> --
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>

Re: [VOTE] Release Apache Felix Metatype 1.2.4

[Raymond Auge]

+1

- Ray

On Fri, Jan 15, 2021 at 1:49 PM Karl Pauls  wrote:

> +1
>
> regards,
>
> Karl
>
> On Friday, January 15, 2021, JB Onofré  wrote:
>
> > +1 (binding)
> >
> > Regards
> > JB
> >
> > > Le 15 janv. 2021 à 18:00, Carsten Ziegeler  a
> > écrit :
> > >
> > > Hi,
> > > we solved one issue in this release:
> > > https://issues.apache.org/jira/browse/FELIX-6009
> > >
> > > Staging repositories:
> > > https://repository.apache.org/content/repositories/orgapachefelix-1362
> > >
> > > You can use this UNIX script to download the release and verify the
> > > signatures:
> > >
> https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> > >
> > > Usage:
> > > sh check_staged_release.sh 1362 /tmp/felix-staging
> > >
> > > Please vote to approve this release:
> > >
> > > [ ] +1 Approve the release
> > > [ ] -1 Veto the release (please provide specific comments)
> > >
> > > Regards
> > > Carsten
> > > --
> > > Carsten Ziegeler
> > > Adobe Research Switzerland
> > > cziege...@apache.org
> >
> >
>
> --
> Karl Pauls
> karlpa...@gmail.com
>


-- 
*Raymond Augé* (@rotty3000)
Senior Software Architect *Liferay, Inc.* (@Liferay)
OSGi Fellow

Re: [VOTE] Release Apache Felix Eventadmin 1.6.2

[Raymond Auge]

+1

- Ray

On Wed., Jan. 6, 2021, 8:15 a.m. ,  wrote:

> +1
>
> David
>
> On Wed, 6 Jan 2021 at 13:04, Karl Pauls  wrote:
>
> > +1
> >
> > regards,
> >
> > Karl
> >
> > On Wed, Jan 6, 2021 at 1:55 PM Carsten Ziegeler 
> > wrote:
> > >
> > > I would like to call a vote on the eventadmin 1.6.2 release
> > >
> > > We solved one issue (caused by the maven bundle plugin 5.1.1):
> > >
> > > https://issues.apache.org/jira/browse/FELIX-6373
> > >
> > >
> > > Staging repositories:
> > > https://repository.apache.org/content/repositories/orgapachefelix-1361
> > >
> > > You can use this UNIX script to download the release and verify the
> > > signatures:
> > >
> https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> > >
> > > Usage:
> > > sh check_staged_release.sh 1361 /tmp/felix-staging
> > >
> > > Please vote to approve this release:
> > >
> > > [ ] +1 Approve the release
> > > [ ] -1 Veto the release (please provide specific comments)
> > >
> > > Regards
> > > Carsten
> > > --
> > > Carsten Ziegeler
> > > Adobe Research Switzerland
> > > cziege...@apache.org
> >
> >
> >
> > --
> > Karl Pauls
> > karlpa...@gmail.com
> >
>

Re: [VOTE] Release Apache Felix Configadmin 1.9.20

[Raymond Auge]

+1

- Ray

On Mon., Jan. 4, 2021, 6:51 a.m. ,  wrote:

> +1
>
> David Bosschaert
>
> On Mon, 4 Jan 2021 at 11:40, Grzegorz Grzybek 
> wrote:
>
> > +1 (non-binding)
> >
> > regards
> > Grzegorz Grzybek
> >
> > pon., 4 sty 2021 o 09:26 Karl Pauls  napisał(a):
> >
> > > +1
> > >
> > > regards,
> > >
> > > Karl
> > >
> > > On Mon, Jan 4, 2021 at 9:10 AM Carsten Ziegeler 
> > > wrote:
> > > >
> > > > +1
> > > >
> > > > Carsten
> > > >
> > > > Am 04.01.2021 um 07:21 schrieb Carsten Ziegeler:
> > > > > I would like to call a vote on the configadmin 1.9.20 release
> > > > >
> > > > > We solved two issues:
> > > > >
> > > > >
> > >
> >
> https://github.com/apache/felix-dev/blob/org.apache.felix.configadmin-1.9.20/configadmin/changelog.txt
> > > > >
> > > > >
> > > > >
> > > > > Staging repositories:
> > > > >
> > https://repository.apache.org/content/repositories/orgapachefelix-1360
> > > > >
> > > > > You can use this UNIX script to download the release and verify the
> > > > > signatures:
> > > > >
> > >
> https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> > > > >
> > > > > Usage:
> > > > > sh check_staged_release.sh 1360 /tmp/felix-staging
> > > > >
> > > > > Please vote to approve this release:
> > > > >
> > > > > [ ] +1 Approve the release
> > > > > [ ] -1 Veto the release (please provide specific comments)
> > > > >
> > > > > Regards
> > > > > Carsten
> > > > > --
> > > > > Carsten Ziegeler
> > > > > Adobe Research Switzerland
> > > > > cziege...@apache.org
> > > >
> > > > --
> > > > --
> > > > Carsten Ziegeler
> > > > Adobe Research Switzerland
> > > > cziege...@apache.org
> > >
> > >
> > >
> > > --
> > > Karl Pauls
> > > karlpa...@gmail.com
> > >
> >
>

Re: [VOTE] Apache Felix Framework 7.0.0 and related subproject releases

[Raymond Auge]

+1

- Ray

On Tue, Dec 22, 2020 at 2:46 AM  wrote:

> +1
>
> David
>
> On Tuesday, 22 December 2020, Carsten Ziegeler 
> wrote:
>
> > +1
> >
> > Carsten
> >
> > Am 21.12.2020 um 23:44 schrieb Karl Pauls:
> >
> >> I would like to call a vote on the following subproject releases:
> >>
> >> framework 7.0.0
> >> main 7.0.0
> >> main.distribution 7.0.0
> >> framework.security 2.8.0
> >>
> >> The main changelogs are in jira and at:
> >> https://github.com/apache/felix-dev/blob/org.apache.felix.
> >> framework-7.0.0/framework/doc/changelog.txt
> >>
> >> Staging repositories:
> >> https://repository.apache.org/content/repositories/orgapachefelix-1358/
> >> https://repository.apache.org/content/repositories/orgapachefelix-1359/
> >>
> >> You can use this UNIX script to download the release and verify the
> >> signatures:
> >> https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> >>
> >> Usage:
> >> sh check_staged_release.sh 1358 /tmp/felix-staging
> >> sh check_staged_release.sh 1359 /tmp/felix-staging
> >>
> >> Please vote to approve this release:
> >>
> >> [ ] +1 Approve the release
> >> [ ] -1 Veto the release (please provide specific comments)
> >>
> >>
> > --
> > --
> > Carsten Ziegeler
> > Adobe Research Switzerland
> > cziege...@apache.org
> >
>


-- 
*Raymond Augé* (@rotty3000)
Senior Software Architect *Liferay, Inc.* (@Liferay)
OSGi Fellow

Re: [VOTE] Release Apache Felix EventAdmin 1.6.0

[Raymond Auge]

+1

-Ray

On Mon., Dec. 14, 2020, 8:34 a.m. ,  wrote:

> +1
>
> David
>
> On Mon, 14 Dec 2020 at 13:15, Carsten Ziegeler 
> wrote:
>
> > I would like to call a vote on the eventadmin 1.6.0 release
> >
> > We solved three issues:
> >
> >
> >
> https://github.com/apache/felix-dev/blob/org.apache.felix.eventadmin-1.6.0/eventadmin/impl/changelog.txt
> >
> >
> > Staging repositories:
> > https://repository.apache.org/content/repositories/orgapachefelix-1357
> >
> > You can use this UNIX script to download the release and verify the
> > signatures:
> > https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh 1357 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > Regards
> > Carsten
> > --
> > Carsten Ziegeler
> > Adobe Research Switzerland
> > cziege...@apache.org
> >
>

Re: [VOTE] Release Apache Felix Webconsole 4.6.0

[Raymond Auge]

+1

- Ray




On Mon., Dec. 14, 2020, 3:57 a.m. Jean-Baptiste Onofre, 
wrote:

> +1 (binding)
>
> Regards
> JB
>
> > Le 14 déc. 2020 à 09:23, Carsten Ziegeler  a
> écrit :
> >
> > I would like to call a vote on the webconsole 4.6.0 release
> >
> > We solved five issues:
> >
> https://github.com/apache/felix-dev/blob/org.apache.felix.webconsole-4.6.0/webconsole/changelog.txt
> >
> >
> > Staging repositories:
> > https://repository.apache.org/content/repositories/orgapachefelix-1356/
> >
> > You can use this UNIX script to download the release and verify the
> signatures:
> > https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh 1356 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > Regards
> > Carsten
> > --
> > Carsten Ziegeler
> > Adobe Research Switzerland
> > cziege...@apache.org
>
>

Re: [VOTE] Apache Felix Framework 6.0.4 and related subproject releases

[Raymond Auge]

+1

- Ray


On Fri., Dec. 11, 2020, 6:03 p.m. Karl Pauls,  wrote:

> I would like to call a vote on the following subproject releases:
>
> framework 6.0.4
> main 6.0.4
> main.distribution 6.0.4
> resolver 2.0.2
>
> The main changelogs are in jira and at:
>
> https://github.com/apache/felix-dev/blob/org.apache.felix.resolver-2.0.2/resolver/doc/changelog.txt
>
> https://github.com/apache/felix-dev/blob/org.apache.felix.framework-6.0.4/framework/doc/changelog.txt
>
> Staging repositories:
> https://repository.apache.org/content/repositories/orgapachefelix-1355/
>
> You can use this UNIX script to download the release and verify the
> signatures:
> https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
>
> Usage:
> sh check_staged_release.sh 1355 /tmp/felix-staging
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>

Re: [VOTE] Release Apache Felix Http Jetty 4.1.4

[Raymond Auge]

+1

- Ray

On Wed, Nov 25, 2020 at 7:31 AM Carsten Ziegeler 
wrote:

> +1
>
> Carsten
>
> Am 25.11.2020 um 07:29 schrieb Carsten Ziegeler:
> > Hi all,
> >
> > I would like to release org.apache.felix.http.jetty.41.4
> >
> > We solved one issue in this release:
> > https://issues.apache.org/jira/browse/FELIX-6364
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachefelix-1354
> >
> >
> > You can use this UNIX script to download the release and verify the
> > signatures:
> > https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh 1354 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > This vote remains open for at least 72 hours.
> >
> > Regards
> > Carsten
> > --
> > Carsten Ziegeler
> > Adobe Research Switzerland
> > cziege...@apache.org
>
> --
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>


-- 
*Raymond Augé* (@rotty3000)
Senior Software Architect *Liferay, Inc.* (@Liferay)
OSGi Fellow

Re: [VOTE] Release Apache Felix Utils 1.11.6

[Raymond Auge]

+1

- Ray

On Tue, Nov 24, 2020 at 6:04 AM Carsten Ziegeler 
wrote:

> +1
>
> Carsten
>
> Am 24.11.2020 um 10:06 schrieb dav...@apache.org:
> > Hi all,
> >
> > I would like to release org.apache.felix.utils-1.11.6
> >
> > We solved the following issue:
> > https://issues.apache.org/jira/projects/FELIX/versions/12348849
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachefelix-1353
> > 
> >
> > You can use this UNIX script to download the release and verify the
> > signatures:
> > https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh 1353 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > This vote remains open for at least 72 hours.
> >
> > Best regards,
> >
> > David Bosschaert
> >
>
> --
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>


-- 
*Raymond Augé* (@rotty3000)
Senior Software Architect *Liferay, Inc.* (@Liferay)
OSGi Fellow

Re: Heads-up: framework release(s)

[Raymond Auge]

I'm anxious to see this stuff to get into the wild. Nice work gents!

+1

- Ray

On Fri, Oct 23, 2020 at 11:10 AM Karl Pauls  wrote:

> Well, it is not really a norm just because of the spec update. I will
> do it for the framework as we are going to at a minimum require java8.
>
> For SCR, i would say it depends - if it stays backwards compatible and
> doesn't include any new requirements I think going with 2.2 is fine.
>
> regards,
>
> Karl
>
> On Fri, Oct 23, 2020 at 4:52 PM Thomas Watson  wrote:
> >
> > +1 to cutting a release off current master and working towards a release
> of
> > the OSGi R8 Framework Felix implementation.
> >
> > As I am doing the work for SCR R8 implementation I have a question about
> > the version of the release.  I see you are going up by a major version
> > to 7.0.0.  Is that the norm for felix release versions based on new
> > versions of an OSGi specification?  For SCR I was planning on just moving
> > up minor versions to version 2.2 for the future OSGi R8 Declarative
> > Services implementation.  The updated specification is backwards
> compatible
> > with the OSGi R7 Declarative Services.  But should SCR really be moving
> up
> > to version 3.0?
> >
> > Tom
> >
> >
> > On Fri, Oct 23, 2020 at 9:23 AM Karl Pauls  wrote:
> >
> > > It has been some time since we had a framework release. Additionally,
> > > we have the OSGi R8 core spec being final now.
> > >
> > > As a consequence, we have some useful fixes in trunk and we have the
> > > „connect“ branch that passes the R8 core ct (and works a lot better
> > > with jpms).
> > >
> > > I think we should do a 6.0.4 release with the current trunk and then,
> > > subsequently, merge the connect branch into trunk and do a 7.0.0
> > > release that is R8 compliant.
> > >
> > > Unless somebody thinks we absolutely have to get some other fixes in
> > > I’ll start with doing a resolver 2.0.1 and a framework 6.0.4 release
> > > soon.
> > >
> > > After that, I’m going to merge in the connect branch changes and do a
> > > framework 7.0.0 and framework.security 2.6.2 release which will be R8
> > > core compliant.
> > >
> > > Regards,
> > >
> > > Karl
> > >
> > > --
> > > Karl Pauls
> > > karlpa...@gmail.com
> > >
>
>
>
> --
> Karl Pauls
> karlpa...@gmail.com
>


-- 
*Raymond Augé* (@rotty3000)
Senior Software Architect *Liferay, Inc.* (@Liferay)
OSGi Fellow

Re: [VOTE] Release Felix Gogo, jline version 1.1.8 and bom version 1.0.6

[Raymond Auge]

+1

- Ray

On Tue, Oct 13, 2020 at 12:39 PM Jean-Baptiste Onofre 
wrote:

> +1 (binding)
>
> Regards
> JB
>
> > Le 13 oct. 2020 à 18:39, Thomas Watson  a écrit :
> >
> > Hi,
> >
> > As promised here is the release of jline and bom to address this issue
> in jlink:
> > https://issues.apache.org/jira/browse/FELIX-6058
> >
> >
> > Staging repository:
> https://repository.apache.org/content/repositories/orgapachefelix-1352/
> >
> > You can use this UNIX script to download the release and verify the
> > signatures:
> https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh [YOUR REPOSITORY ID] /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.
> >
> >
> > Tom
>
>

-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: Release Apache Felix Gogo - Runtime 1.1.4, Shell 1.1.4, Command 1.1.2, BOM 1.0.4

[Raymond Auge]

+1

- Ray

On Mon, Oct 5, 2020 at 1:02 PM Thomas Watson  wrote:

> Hi,
>
> We solved 2 issues in Gogo Runtime this
> release:
> https://issues.apache.org/jira/browse/FELIX-2355?jql=project%20%3D%20FELIX%20AND%20fixVersion%20%3D%20gogo.runtime-1.1.4
>
>
> We solved 2 issues in Gogo Shell this release:
>
>
> https://issues.apache.org/jira/browse/FELIX-2340?jql=project%20%3D%20FELIX%20AND%20fixVersion%20%3D%20gogo.shell-1.1.4
>
>
> We solved 1 issue in Gogo Command this release:
>
>
> https://issues.apache.org/jira/browse/FELIX-6038?jql=project%20%3D%20FELIX%20AND%20fixVersion%20%3D%20gogo.command-1.1.2
>
>
> We updated the Gogo BOM to use the latest released Gogo artifacts this
> release.
>
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachefelix-1351/
>
> You can use this UNIX script to download the release and verify the
> signatures:
> https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
>
> Usage:
> sh check_staged_release.sh 1351 /tmp/felix-staging
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>
>
> Thanks
>
> Tom
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [VOTE] Release Apache Felix Http Jetty 4.1.2, Http Bridge 4.1.2 and Http Base 4.1.2

[Raymond Auge]

+1

- Ray

On Mon., Oct. 5, 2020, 4:22 a.m. Carsten Ziegeler, 
wrote:

> +1
>
> Carsten
>
> Am 05.10.2020 um 10:14 schrieb Carsten Ziegeler:
> > Hi,
> >
> > We solved 2 issues in http.jetty 4.1.2:
> >
> >
> https://issues.apache.org/jira/browse/FELIX-6343?jql=project%20%3D%20FELIX%20AND%20fixVersion%20%3D%20http.jetty-4.1.2
> >
> >
> > and one issue in http.base 4.1.2 and http.bridge 4.1.2
> > https://issues.apache.org/jira/browse/FELIX-6342
> >
> > Staging repositories:
> > https://repository.apache.org/content/repositories/orgapachefelix-1350
> >
> > You can use this UNIX script to download the release and verify the
> > signatures:
> > https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh 1350 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > Regards
> > Carsten
> > --
> > Carsten Ziegeler
> > Adobe Research Switzerland
> > cziege...@apache.org
>
> --
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>

Re: [VOTE] Release Apache Felix Http Base 4.1.0, Bridge 4.1.0 and Jetty 4.1.0

[Raymond Auge]

+1

- Ray

On Wed, Sep 23, 2020 at 9:26 AM Pierre De Rop 
wrote:

> Hi,
>
> +1
>
> thanks & regards
> Pierre
>
> On Wed, Sep 23, 2020 at 3:00 PM Thomas Watson  wrote:
>
> > +1
> >
> > Tom
> >
> > On Wed, Sep 23, 2020 at 2:57 AM Carsten Ziegeler 
> > wrote:
> >
> > > Hi,
> > >
> > > we solved three issues for http jetty:
> > >
> > >
> >
> https://issues.apache.org/jira/browse/FELIX-6333?jql=project%20%3D%20FELIX%20AND%20fixVersion%20%3D%20http.jetty-4.1.0
> > >
> > > and two issues for bridge 4.1.0 and base 4.1.0:
> > >
> > >
> >
> https://issues.apache.org/jira/browse/FELIX-6334?jql=project%20%3D%20FELIX%20AND%20fixVersion%20%3D%20http.base-4.1.0
> > >
> > >
> > > Staging repositories:
> > > https://repository.apache.org/content/repositories/orgapachefelix-1349
> > >
> > > You can use this UNIX script to download the release and verify the
> > > signatures:
> > >
> https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> > >
> > > Usage:
> > > sh check_staged_release.sh 1349 /tmp/felix-staging
> > >
> > > Please vote to approve this release:
> > >
> > > [ ] +1 Approve the release
> > > [ ] -1 Veto the release (please provide specific comments)
> > >
> > > Regards
> > > Carsten
> > > --
> > > Carsten Ziegeler
> > > Adobe Research Switzerland
> > > cziege...@apache.org
> > >
> >
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [VOTE] Apache Felix SCR 2.1.24 release

[Raymond Auge]

+1

- Ray

On Thu, Sep 17, 2020 at 4:58 AM Jean-Baptiste Onofre 
wrote:

> Hi guys,
>
> As discussed on the mailing list, I submit Apache Felix SCR 2.1.24 release
> to your vote.
> This release avoid the requirement to log service, potential
> NoSuchElementException when services are removed, and fix factory component
> eager deactivation.
>
> Release Notes:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100=12348738
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachefelix-1348/
>
> Staging Dist:
> https://dist.apache.org/repos/dist/dev/felix/scr/2.1.24/
>
> Git tag:
> org.apache.felix.scr-2.1.24
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
> Regards
> JB
>
>

-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: Why do the docs claim a DEPENDENCIES file is needed?

[Raymond Auge]

+1

I haven't understood the need or use of this. But I wasn't sure if this was
a felix project thing, or an ASF thing so I ignored it.

- Ray

On Thu, Sep 3, 2020 at 9:05 PM David Jencks 
wrote:

>
> https://felix.apache.org/documentation/development/dependencies-file-template.html
> claims that each released software archive (what is that? source? compiled?
> ???) must contain a “DEPENDENCIES” file.
>
> Why? The information in it is either useless and misleading for OSGI (if
> the dependency is not included in the archive) or already required to be in
> NOTICE or LICENCE (if the dependency is included), which are actual Apache
> required files.
>
> I may have inadvertently started the idea that a DEPENDENCIES file is
> useful, before I knew about OSGI, by getting maven to generate one, listing
> the maven dependencies.
>
> Can we drop this page and stop this confusing and useless practice?
>
> David Jencks



-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [VOTE] Apache Felix SCR 2.1.22 release

[Raymond Auge]

+1

- Ray

On Mon, Aug 31, 2020 at 12:32 PM Carsten Ziegeler 
wrote:

> +1
>
> Carsten
>
> Am 31.08.2020 um 18:21 schrieb Jean-Baptiste Onofre:
> > Hi guys,
> >
> > As discussed on the mailing list, I submit Apache Felix SCR 2.1.22
> release to your vote (after the mistake in 2.1.21 versioning).
> >
> > Release Notes:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100=12348094
> <
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100=12348094
> >
> >
> > Staging Repository:
> > https://repository.apache.org/content/repositories/orgapachefelix-1347/
> 
> >
> > Staging Dist:
> > https://dist.apache.org/repos/dist/dev/felix/scr/2.1.22/ <
> https://dist.apache.org/repos/dist/dev/felix/scr/2.1.22/>
> >
> > Git tag:
> > org.apache.felix.scr-2.1.22
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Don't approve the release (please provide specific comments)
> >
> > This vote will be open for at least 72 hours.
> >
> > Thanks,
> > Regards
> > JB
> >
> >
>
> --
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [VOTE] Apache Felix Log 1.2.4 release

[Raymond Auge]

+1 (binding)

- Ray

On Mon, Aug 31, 2020 at 10:43 AM Jean-Baptiste Onofre 
wrote:

> Hi everyone,
>
> Following the discussion on the mailing list, I submit Apache Felix Log
> 1.2.4 to your vote.
>
> Release Notes:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100=12348344
> <
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100=12348344
> >
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachefelix-1346/ <
> https://repository.apache.org/content/repositories/orgapachefelix-1346/>
>
> Staging Dist:
> https://dist.apache.org/repos/dist/dev/felix/log/1.2.4/ <
> https://dist.apache.org/repos/dist/dev/felix/log/1.2.4/>
>
> Git tag:
> org.apache.felix.log-1.2.4
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
> Regards
> JB



-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: release Felix log 1.2.4

[Raymond Auge]

Hey JB,

It's up to you but I can leave it in your hands.

Sincere thanks,
- Ray

On Mon, Aug 31, 2020 at 9:17 AM Jean-Baptiste Onofre 
wrote:

> Hi Ray,
>
> Up to know, I can cut Felix Log release if you want.
>
> Let me know.
>
> Regards
> JB
>
> > Le 31 août 2020 à 15:16, Raymond Auge 
> a écrit :
> >
> > Hello All,
> >
> > Given the fact that the in-flight vote of SCR appears to need a new Felix
> > log, we should release it.
> >
> > Shall I proceed with the release or is someone already taking care of it?
> >
> > - Ray
>
>

-- 
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
 (@Liferay)

release Felix log 1.2.4

[Raymond Auge]

Hello All,

Given the fact that the in-flight vote of SCR appears to need a new Felix
log, we should release it.

Shall I proceed with the release or is someone already taking care of it?

- Ray

Re: [VOTE] Apache Felix SCR 2.1.21 release

[Raymond Auge]

+1 (binding)

Thanks everyone!

- Ray



On Mon, Aug 31, 2020 at 7:53 AM Karl Pauls  wrote:

> +1
>
> regards,
>
> Karl
>
> On Mon, Aug 31, 2020 at 1:52 PM Jean-Baptiste Onofre 
> wrote:
> >
> > +1 (binding)
> >
> > Casting my own vote.
> >
> > Regards
> > JB
> >
> > > Le 30 août 2020 à 20:45, Jean-Baptiste Onofre  a
> écrit :
> > >
> > > Hi guys,
> > >
> > > As discussed on the mailing list, I submit Apache Felix SCR 2.1.21
> release to your vote.
> > >
> > > Release Notes:
> > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100=12348094
> <
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100=12348094
> >
> > >
> > > Staging Repository:
> > >
> https://repository.apache.org/content/repositories/orgapachefelix-1345/ <
> https://repository.apache.org/content/repositories/orgapachefelix-1345/>
> > >
> > > Staging Dist:
> > > https://dist.apache.org/repos/dist/dev/felix/scr/2.1.21/ <
> https://dist.apache.org/repos/dist/dev/felix/scr/2.1.21/>
> > >
> > > Git tag:
> > > org.apache.felix.scr-2.1.21
> > >
> > > Please vote to approve this release:
> > >
> > > [ ] +1 Approve the release
> > > [ ] -1 Don't approve the release (please provide specific comments)
> > >
> > > This vote will be open for at least 72 hours.
> > >
> > > Thanks,
> > > Regards
> > > JB
> >
>
>
> --
> Karl Pauls
> karlpa...@gmail.com
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: Your project website

[Raymond Auge]

Hey Karl,

The more time passes the less time I will have to do this work, but I'll
leave it until you're around.

- Ray

On Thu, Aug 6, 2020 at 3:43 AM Karl Pauls  wrote:

> Hi Ray,
>
> thanks a lot for picking this up!
>
> I’m mostly offline this week but would like to look at the options as well.
> Can we wait until next week until a decision is made?
>
>
> regards,
>
> Karl
>
> On Wednesday, August 5, 2020, Bertrand Delacretaz 
> wrote:
>
> > Hi,
> >
> > On Tue, Aug 4, 2020 at 6:30 PM Raymond Auge
> >  wrote:
> > > ...So far the Apache Aries project seems to be leaning toward choosing
> > Antora
> > > [1] for choice of static site building tool...
> >
> > I'm not really active in Felix so I'll let the PMC or whoever does the
> > work decide.
> >
> > However, as per [2] it looks like Antora supports only Asciidoc as its
> > input format, whereas the current Felix site content is in Markdown.
> >
> > This *might* represent more conversion work - however there are
> > various flavors of Markdown, so even staying in that format will
> > require some conversion work as well. For Sling we migrated from the
> > Apache CMS to Jbake [3] and a number of things required fixing, even
> > though we used Markdown in both cases.
> >
> > -Bertrand
> >
> > [1] https://docs.antora.org/antora/2.3/
> > [2] https://docs.antora.org/antora/2.3/page/
> > [3] https://issues.apache.org/jira/browse/SLING-6955
> >
>
>
> --
> Karl Pauls
> karlpa...@gmail.com
>


-- 
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
 (@Liferay)

Re: Your project website

[Raymond Auge]

I would make a case to integrate the site content into the same repository
that contains the code.

Why? This makes it much more apt to being kept up to date since changes can
be made to both sources, docs and site content in a single changeset.

Thoughts?

- Ray

On Tue, Aug 4, 2020 at 12:32 PM Raymond Auge 
wrote:

> For reference here is the INFRA ticket [1] for the migration task.
>
> - Ray
>
> [1] https://issues.apache.org/jira/browse/INFRA-20635
>
>
> On Tue, Aug 4, 2020 at 12:30 PM Raymond Auge 
> wrote:
>
>> Hey folks,
>>
>> So far the Apache Aries project seems to be leaning toward choosing
>> Antora [1] for choice of static site building tool.
>>
>> I would throw that here as an option.
>>
>> Would anyone here have some other preferred solution?
>>
>> - Ray
>>
>> [1] https://docs.antora.org/antora/2.3/
>>
>> On Tue, Aug 4, 2020 at 12:21 PM Andrew Wetmore 
>> wrote:
>>
>>> Raymond and I are now in a Slack chat on the migration issue.
>>>
>>>
>>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>>>  Virus-free.
>>> www.avast.com
>>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>>> <#m_-1565469872456774852_m_7808138197927144006_m_-6946200389618774736_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>
>>> On Tue, Aug 4, 2020 at 12:31 PM Raymond Auge 
>>> wrote:
>>>
>>>> forgot to CC you Andrew, please see thread.
>>>>
>>>> On Tue, Aug 4, 2020 at 10:43 AM Raymond Auge 
>>>> wrote:
>>>>
>>>>> Hey Andrew,
>>>>>
>>>>> Maybe I can try to work on both the felix site and the Aries site at
>>>>> the same time.
>>>>>
>>>>> - Ray
>>>>>
>>>>> On Tue, Aug 4, 2020 at 9:53 AM Andrew Wetmore 
>>>>> wrote:
>>>>>
>>>>>> Hi:
>>>>>>
>>>>>> I am part of the Infrastructure team, and am writing to ask whether
>>>>>> your
>>>>>> project is still using the Apache CMS for your project website. As you
>>>>>> know, the CMS is reaching end-of-life, and we need projects to move
>>>>>> their
>>>>>> websites onto a different option within the next few weeks.
>>>>>>
>>>>>> There are several alternatives available, including those listed on
>>>>>> this
>>>>>> page [1] on managing project websites. Infra is assembling a Wiki
>>>>>> page [2]
>>>>>> on migrating a website from the CMS, and is looking forward to helping
>>>>>> projects with this transition.
>>>>>>
>>>>>> Please let me know whether your site is still on the Apache CMS and,
>>>>>> if so,
>>>>>> who will be the project point-of-contact with Infra for the migration.
>>>>>>
>>>>>> Thank you!
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> [1] https://infra.apache.org/project-site.html
>>>>>>
>>>>>> [2]
>>>>>>
>>>>>> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Andrew Wetmore
>>>>>> Technical Writer-Editor
>>>>>> Infra
>>>>>> *Apache Software Foundation*
>>>>>> andr...@apache.org
>>>>>>
>>>>>> <
>>>>>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
>>>>>> >
>>>>>> Virus-free.
>>>>>> www.avast.com
>>>>>> <
>>>>>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
>>>>>> >
>>>>>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
>>>>>  (@rotty3000)
>>>>> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
>>>>>  (@Liferay)
>>>>>
>>>>
>>>>
>>>> --
>>>> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
>>>>  (@rotty3000)
>>>> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
>>>>  (@Liferay)
>>>>
>>>
>>>
>>> --
>>> Andrew Wetmore
>>> Technical Writer-Editor
>>> Infra
>>> *Apache Software Foundation*
>>> andr...@apache.org
>>>
>>>
>>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>>>  Virus-free.
>>> www.avast.com
>>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>>> <#m_-1565469872456774852_m_7808138197927144006_m_-6946200389618774736_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>
>>
>>
>> --
>> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
>>  (@rotty3000)
>> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
>>  (@Liferay)
>>
>
>
> --
> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
>  (@rotty3000)
> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
>  (@Liferay)
>


-- 
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
 (@Liferay)

Re: Your project website

[Raymond Auge]

For reference here is the INFRA ticket [1] for the migration task.

- Ray

[1] https://issues.apache.org/jira/browse/INFRA-20635


On Tue, Aug 4, 2020 at 12:30 PM Raymond Auge 
wrote:

> Hey folks,
>
> So far the Apache Aries project seems to be leaning toward choosing Antora
> [1] for choice of static site building tool.
>
> I would throw that here as an option.
>
> Would anyone here have some other preferred solution?
>
> - Ray
>
> [1] https://docs.antora.org/antora/2.3/
>
> On Tue, Aug 4, 2020 at 12:21 PM Andrew Wetmore  wrote:
>
>> Raymond and I are now in a Slack chat on the migration issue.
>>
>>
>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>>  Virus-free.
>> www.avast.com
>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>> <#m_7808138197927144006_m_-6946200389618774736_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>> On Tue, Aug 4, 2020 at 12:31 PM Raymond Auge 
>> wrote:
>>
>>> forgot to CC you Andrew, please see thread.
>>>
>>> On Tue, Aug 4, 2020 at 10:43 AM Raymond Auge 
>>> wrote:
>>>
>>>> Hey Andrew,
>>>>
>>>> Maybe I can try to work on both the felix site and the Aries site at
>>>> the same time.
>>>>
>>>> - Ray
>>>>
>>>> On Tue, Aug 4, 2020 at 9:53 AM Andrew Wetmore 
>>>> wrote:
>>>>
>>>>> Hi:
>>>>>
>>>>> I am part of the Infrastructure team, and am writing to ask whether
>>>>> your
>>>>> project is still using the Apache CMS for your project website. As you
>>>>> know, the CMS is reaching end-of-life, and we need projects to move
>>>>> their
>>>>> websites onto a different option within the next few weeks.
>>>>>
>>>>> There are several alternatives available, including those listed on
>>>>> this
>>>>> page [1] on managing project websites. Infra is assembling a Wiki page
>>>>> [2]
>>>>> on migrating a website from the CMS, and is looking forward to helping
>>>>> projects with this transition.
>>>>>
>>>>> Please let me know whether your site is still on the Apache CMS and,
>>>>> if so,
>>>>> who will be the project point-of-contact with Infra for the migration.
>>>>>
>>>>> Thank you!
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> [1] https://infra.apache.org/project-site.html
>>>>>
>>>>> [2]
>>>>>
>>>>> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
>>>>>
>>>>>
>>>>> --
>>>>> Andrew Wetmore
>>>>> Technical Writer-Editor
>>>>> Infra
>>>>> *Apache Software Foundation*
>>>>> andr...@apache.org
>>>>>
>>>>> <
>>>>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
>>>>> >
>>>>> Virus-free.
>>>>> www.avast.com
>>>>> <
>>>>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
>>>>> >
>>>>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
>>>>  (@rotty3000)
>>>> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
>>>>  (@Liferay)
>>>>
>>>
>>>
>>> --
>>> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
>>>  (@rotty3000)
>>> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
>>>  (@Liferay)
>>>
>>
>>
>> --
>> Andrew Wetmore
>> Technical Writer-Editor
>> Infra
>> *Apache Software Foundation*
>> andr...@apache.org
>>
>>
>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>>  Virus-free.
>> www.avast.com
>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>> <#m_7808138197927144006_m_-6946200389618774736_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>
>
> --
> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
>  (@rotty3000)
> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
>  (@Liferay)
>


-- 
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
 (@Liferay)

Re: Your project website

[Raymond Auge]

Hey folks,

So far the Apache Aries project seems to be leaning toward choosing Antora
[1] for choice of static site building tool.

I would throw that here as an option.

Would anyone here have some other preferred solution?

- Ray

[1] https://docs.antora.org/antora/2.3/

On Tue, Aug 4, 2020 at 12:21 PM Andrew Wetmore  wrote:

> Raymond and I are now in a Slack chat on the migration issue.
>
>
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>  Virus-free.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
> <#m_-6946200389618774736_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Tue, Aug 4, 2020 at 12:31 PM Raymond Auge 
> wrote:
>
>> forgot to CC you Andrew, please see thread.
>>
>> On Tue, Aug 4, 2020 at 10:43 AM Raymond Auge 
>> wrote:
>>
>>> Hey Andrew,
>>>
>>> Maybe I can try to work on both the felix site and the Aries site at the
>>> same time.
>>>
>>> - Ray
>>>
>>> On Tue, Aug 4, 2020 at 9:53 AM Andrew Wetmore 
>>> wrote:
>>>
>>>> Hi:
>>>>
>>>> I am part of the Infrastructure team, and am writing to ask whether your
>>>> project is still using the Apache CMS for your project website. As you
>>>> know, the CMS is reaching end-of-life, and we need projects to move
>>>> their
>>>> websites onto a different option within the next few weeks.
>>>>
>>>> There are several alternatives available, including those listed on this
>>>> page [1] on managing project websites. Infra is assembling a Wiki page
>>>> [2]
>>>> on migrating a website from the CMS, and is looking forward to helping
>>>> projects with this transition.
>>>>
>>>> Please let me know whether your site is still on the Apache CMS and, if
>>>> so,
>>>> who will be the project point-of-contact with Infra for the migration.
>>>>
>>>> Thank you!
>>>>
>>>>
>>>>
>>>>
>>>> [1] https://infra.apache.org/project-site.html
>>>>
>>>> [2]
>>>>
>>>> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
>>>>
>>>>
>>>> --
>>>> Andrew Wetmore
>>>> Technical Writer-Editor
>>>> Infra
>>>> *Apache Software Foundation*
>>>> andr...@apache.org
>>>>
>>>> <
>>>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
>>>> >
>>>> Virus-free.
>>>> www.avast.com
>>>> <
>>>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
>>>> >
>>>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>>
>>>
>>>
>>> --
>>> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
>>>  (@rotty3000)
>>> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
>>>  (@Liferay)
>>>
>>
>>
>> --
>> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
>>  (@rotty3000)
>> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
>>  (@Liferay)
>>
>
>
> --
> Andrew Wetmore
> Technical Writer-Editor
> Infra
> *Apache Software Foundation*
> andr...@apache.org
>
>
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>  Virus-free.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
> <#m_-6946200389618774736_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>


-- 
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
 (@Liferay)

Re: Your project website

[Raymond Auge]

forgot to CC you Andrew, please see thread.

On Tue, Aug 4, 2020 at 10:43 AM Raymond Auge 
wrote:

> Hey Andrew,
>
> Maybe I can try to work on both the felix site and the Aries site at the
> same time.
>
> - Ray
>
> On Tue, Aug 4, 2020 at 9:53 AM Andrew Wetmore  wrote:
>
>> Hi:
>>
>> I am part of the Infrastructure team, and am writing to ask whether your
>> project is still using the Apache CMS for your project website. As you
>> know, the CMS is reaching end-of-life, and we need projects to move their
>> websites onto a different option within the next few weeks.
>>
>> There are several alternatives available, including those listed on this
>> page [1] on managing project websites. Infra is assembling a Wiki page [2]
>> on migrating a website from the CMS, and is looking forward to helping
>> projects with this transition.
>>
>> Please let me know whether your site is still on the Apache CMS and, if
>> so,
>> who will be the project point-of-contact with Infra for the migration.
>>
>> Thank you!
>>
>>
>>
>>
>> [1] https://infra.apache.org/project-site.html
>>
>> [2]
>>
>> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
>>
>>
>> --
>> Andrew Wetmore
>> Technical Writer-Editor
>> Infra
>> *Apache Software Foundation*
>> andr...@apache.org
>>
>> <
>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
>> >
>> Virus-free.
>> www.avast.com
>> <
>> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
>> >
>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>
>
> --
> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
>  (@rotty3000)
> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
>  (@Liferay)
>


-- 
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
 (@Liferay)

Re: Your project website

[Raymond Auge]

Hey Andrew,

Maybe I can try to work on both the felix site and the Aries site at the
same time.

- Ray

On Tue, Aug 4, 2020 at 9:53 AM Andrew Wetmore  wrote:

> Hi:
>
> I am part of the Infrastructure team, and am writing to ask whether your
> project is still using the Apache CMS for your project website. As you
> know, the CMS is reaching end-of-life, and we need projects to move their
> websites onto a different option within the next few weeks.
>
> There are several alternatives available, including those listed on this
> page [1] on managing project websites. Infra is assembling a Wiki page [2]
> on migrating a website from the CMS, and is looking forward to helping
> projects with this transition.
>
> Please let me know whether your site is still on the Apache CMS and, if so,
> who will be the project point-of-contact with Infra for the migration.
>
> Thank you!
>
>
>
>
> [1] https://infra.apache.org/project-site.html
>
> [2]
>
> https://cwiki.apache.org/confluence/display/INFRA/Migrate+your+project+website+from+the+Apache+CMS
>
>
> --
> Andrew Wetmore
> Technical Writer-Editor
> Infra
> *Apache Software Foundation*
> andr...@apache.org
>
> <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >
> Virus-free.
> www.avast.com
> <
> https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail
> >
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: Configurator Release

[Raymond Auge]

Thanks Amit, it's already in progress.

- Ray

On Thu, Jul 23, 2020 at 8:03 AM Amit Mondal  wrote:

> Hi,
>
> It would be really helpful if anyone of the Felix core developers could
> make a release of the configurator bundle with the fix provided by Peter.
>
> Looking forward to your further assistance.
>
> Thanks and Regards,
> Amit
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [VOTE] Apache Felix FileInstall 3.6.8 release

[Raymond Auge]

+1

- Ray

On Sat, Jul 18, 2020, 02:25 Jean-Baptiste Onofre,  wrote:

> Hi everyone,
>
> We fixed an important issue in Felix FileInstall introduced in 3.6.6
> release: the configuration are bound to a bundle preventing "global"
> visibility, impacting lot of user bundles (SCR, etc).
>
> Felix FileInstall 3.6.8 fixes that.
>
> Please, take a look on Release Notes for details.
>
> Release Notes:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100=12348457
> <
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100=12348457
> >
>
> Staging Repository:
> https://repository.apache.org/content/repositories/orgapachefelix-1343/ <
> https://repository.apache.org/content/repositories/orgapachefelix-1343/>
>
> Staging Dist:
> https://dist.apache.org/repos/dist/dev/felix/fileinstall/3.6.8/ <
> https://dist.apache.org/repos/dist/dev/felix/fileinstall/3.6.8/>
>
> Git Tag:
> org.apache.felix.fileinstall-3.6.8
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
> Regards
> JB

Re: [VOTE] Release Apache Felix Webconsole 4.5.4

[Raymond Auge]

+1

- Ray

On Fri, Jul 17, 2020, 04:36 Karl Pauls,  wrote:

> +1
>
> regards,
>
> Karl
>
> On Fri, Jul 17, 2020 at 10:31 AM  wrote:
> >
> > +1
> >
> > David
> >
> > On Fri, 17 Jul 2020 at 07:31, Carsten Ziegeler 
> wrote:
> >
> > > Hi,
> > > we solved two issues in this release:
> > > https://issues.apache.org/jira/projects/FELIX/versions/12348561
> > >
> > > Staging repositories:
> > > https://repository.apache.org/content/repositories/orgapachefelix-1342
> > >
> > > You can use this UNIX script to download the release and verify the
> > > signatures:
> > >
> https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> > >
> > > Usage:
> > > sh check_staged_release.sh 1342 /tmp/felix-staging
> > >
> > > Please vote to approve this release:
> > >
> > > [ ] +1 Approve the release
> > > [ ] -1 Veto the release (please provide specific comments)
> > >
> > > Regards
> > > Carsten
> > > --
> > > Carsten Ziegeler
> > > Adobe Research Switzerland
> > > cziege...@apache.org
> > >
>
>
>
> --
> Karl Pauls
> karlpa...@gmail.com
>

Re: [VOTE] Release Apache Felix Configadmin 1.9.18

[Raymond Auge]

+1

- Ray

On Fri, Jul 17, 2020, 04:36 Karl Pauls,  wrote:

> +1
>
> regards,
>
> Karl
>
> On Fri, Jul 17, 2020 at 10:31 AM  wrote:
> >
> > +1
> >
> > David
> >
> > On Fri, 17 Jul 2020 at 07:31, Carsten Ziegeler 
> wrote:
> >
> > > Hi,
> > > we solved three issues in this release:
> > > https://issues.apache.org/jira/projects/FELIX/versions/12345955
> > >
> > > Staging repositories:
> > > https://repository.apache.org/content/repositories/orgapachefelix-1341
> > >
> > > You can use this UNIX script to download the release and verify the
> > > signatures:
> > >
> https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> > >
> > > Usage:
> > > sh check_staged_release.sh 1341 /tmp/felix-staging
> > >
> > > Please vote to approve this release:
> > >
> > > [ ] +1 Approve the release
> > > [ ] -1 Veto the release (please provide specific comments)
> > >
> > > Regards
> > > Carsten
> > > --
> > > Carsten Ziegeler
> > > Adobe Research Switzerland
> > > cziege...@apache.org
> > >
>
>
>
> --
> Karl Pauls
> karlpa...@gmail.com
>

Re: [VOTE] Release Apache Felix Http Jetty 4.0.20

[Raymond Auge]

+1

- Ray

On Fri, Jul 17, 2020, 04:36 Karl Pauls,  wrote:

> +1
>
> regards,
>
> Karl
>
> On Fri, Jul 17, 2020 at 10:31 AM  wrote:
> >
> > +1
> >
> > David
> >
> > On Fri, 17 Jul 2020 at 07:30, Carsten Ziegeler 
> wrote:
> >
> > > Hi,
> > > we solved one issue in this release:
> > > https://issues.apache.org/jira/browse/FELIX-6306
> > >
> > > Staging repositories:
> > > https://repository.apache.org/content/repositories/orgapachefelix-1340
> > >
> > > You can use this UNIX script to download the release and verify the
> > > signatures:
> > >
> https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> > >
> > > Usage:
> > > sh check_staged_release.sh 1340 /tmp/felix-staging
> > >
> > > Please vote to approve this release:
> > >
> > > [ ] +1 Approve the release
> > > [ ] -1 Veto the release (please provide specific comments)
> > >
> > > Regards
> > > Carsten
> > > --
> > > Carsten Ziegeler
> > > Adobe Research Switzerland
> > > cziege...@apache.org
> > >
>
>
>
> --
> Karl Pauls
> karlpa...@gmail.com
>

Re: [VOTE] Release Felix maven-bundle-plugin version 5.1.1

[Raymond Auge]

The vote succeeded with 7 +1 votes.

I will proceed with the release ASAP.

- Ray

On Tue, Jul 14, 2020 at 6:35 PM Raymond Auge 
wrote:

> My +1
>
> On Fri, Jul 10, 2020 at 11:54 AM Pierre De Rop 
> wrote:
>
>> Hi,
>>
>> +1
>>
>> Pierre
>>
>> Le ven. 10 juil. 2020 à 17:19, Georg Henzler  a
>> écrit :
>>
>> > +1
>> >
>> > -Georg
>> >
>> > On 2020-07-09 18:50, Raymond Auge wrote:
>> > > Hi,
>> > >
>> > > We've updated the maven-bundle-plugin to use bnd 5.1.1.
>> > >
>> > > Staging repository:
>> > >
>> https://repository.apache.org/content/repositories/orgapachefelix-1338/
>> > >
>> > > You can use this UNIX script to download the release and verify the
>> > > signatures:
>> > >
>> https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
>> > >
>> > > Usage:
>> > > sh check_staged_release.sh 1338 /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.
>> >
>>
>
>
> --
> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
>  (@rotty3000)
> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
>  (@Liferay)
>


-- 
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
 (@Liferay)

Re: [VOTE] Release Felix maven-bundle-plugin version 5.1.1

[Raymond Auge]

My +1

On Fri, Jul 10, 2020 at 11:54 AM Pierre De Rop 
wrote:

> Hi,
>
> +1
>
> Pierre
>
> Le ven. 10 juil. 2020 à 17:19, Georg Henzler  a
> écrit :
>
> > +1
> >
> > -Georg
> >
> > On 2020-07-09 18:50, Raymond Auge wrote:
> > > Hi,
> > >
> > > We've updated the maven-bundle-plugin to use bnd 5.1.1.
> > >
> > > Staging repository:
> > >
> https://repository.apache.org/content/repositories/orgapachefelix-1338/
> > >
> > > You can use this UNIX script to download the release and verify the
> > > signatures:
> > >
> https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> > >
> > > Usage:
> > > sh check_staged_release.sh 1338 /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.
> >
>


-- 
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
 (@Liferay)

[VOTE] Release Felix maven-bundle-plugin version 5.1.1

[Raymond Auge]

Hi,

We've updated the maven-bundle-plugin to use bnd 5.1.1.

Staging repository:
https://repository.apache.org/content/repositories/orgapachefelix-1338/

You can use this UNIX script to download the release and verify the
signatures:
https://github.com/apache/felix-dev/blob/master/check_staged_release.sh

Usage:
sh check_staged_release.sh 1338 /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.

-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

starting a release of maven-bundle-plugin

[Raymond Auge]

Hey All,

Just wanted to warn ya'll that I am starting a release of
maven-bundle-plugin to sync with bnd 5.1.1.

Sincerely,
-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [VOTE] Release Apache Felix WebConsole 4.5.2

[Raymond Auge]

+1

- Ray

On Tue, May 5, 2020, 02:59 Jean-Baptiste Onofre,  wrote:

> +1 (binding)
>
> Regards
> JB
>
> > Le 5 mai 2020 à 08:54, Carsten Ziegeler  a écrit :
> >
> > Hi,
> > we solved two issues in this release:
> >
> > https://github.com/apache/felix-dev/blob/master/webconsole/changelog.txt
> >
> > Staging repositories:
> > https://repository.apache.org/content/repositories/orgapachefelix-1337
> >
> > You can use this UNIX script to download the release and verify the
> > signatures:
> > https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh 1337 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > Regards
> > Carsten
> >
> > --
> > Carsten Ziegeler
> > Adobe Research Switzerland
> > cziege...@apache.org
>
>

Re: [VOTE] Accept the application metrics bundles contribution

[Raymond Auge]

+1

- Ray

On Thu, Apr 30, 2020 at 12:59 PM Jean-Baptiste Onofre 
wrote:

> +1 (binding)
>
> Regards
> JB
>
> > Le 30 avr. 2020 à 17:22, Karl Pauls  a écrit :
> >
> > I think the discussion of the "application metrics bundles" contribution
> > (https://github.com/apache/sling-whiteboard/tree/master/osgi-metrics)
> > by Robert Munteanu has died down by now. It looks like there is some
> > interest in the idea and
> > given that Robert is willing to maintain it we should bring it to a vote.
> >
> > This vote is about officially accepting the donation. As this has been
> > developed in Apache already we don't have to sort out the IP
> > clearance.
> >
> > Please cast your votes:
> >
> > [ ] +1 Accept the contribution into Felix
> > [ ] -1 Do not
>
>

-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [VOTE] Release Apache Felix Webconsole 4.5.0

[Raymond Auge]

+1

- Ray

On Fri, Apr 24, 2020, 07:19 ,  wrote:

> +1
>
> David
>
> On Fri, 24 Apr 2020 at 11:15, Carsten Ziegeler 
> wrote:
>
> > Hi,
> >
> > we solved four issues in this release:
> > https://issues.apache.org/jira/projects/FELIX/versions/12347877
> >
> > Staging repositories:
> > https://repository.apache.org/content/repositories/orgapachefelix-1336
> >
> > You can use this UNIX script to download the release and verify the
> > signatures:
> > https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh 1336 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > Regards
> > Carsten
> > --
> > Carsten Ziegeler
> > Adobe Research Switzerland
> > cziege...@apache.org
> >
>

Re: [VOTE] Release Apache Felix cm.json 1.0.2

[Raymond Auge]

+1

- Ray

On Mon, Apr 20, 2020 at 7:39 AM  wrote:

> +1
>
> David
>
> On Mon, 20 Apr 2020 at 12:32, Jean-Baptiste Onofre 
> wrote:
>
> > +1 (binding)
> >
> > Regards
> > JB
> >
> > > Le 20 avr. 2020 à 12:38, Carsten Ziegeler  a
> > écrit :
> > >
> > > Hi,
> > > we solved two issues
> > >
> > >
> >
> https://issues.apache.org/jira/browse/FELIX-6264?jql=project%20%3D%20FELIX%20AND%20fixVersion%20%3D%20cm.json-1.0.2
> > >
> > > Staging repositories:
> > > https://repository.apache.org/content/repositories/orgapachefelix-1335
> > >
> > > You can use this UNIX script to download the release and verify the
> > > signatures:
> > >
> https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> > >
> > > Usage:
> > > sh check_staged_release.sh 1335 /tmp/felix-staging
> > >
> > > Please vote to approve this release:
> > >
> > > [ ] +1 Approve the release
> > > [ ] -1 Veto the release (please provide specific comments)
> > >
> > > Regards
> > > Carsten
> > >
> > > --
> > > Carsten Ziegeler
> > > Adobe Research Switzerland
> > > cziege...@apache.org
> >
> >
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [VOTE] Release Apache Felix SCR 2.1.20

[Raymond Auge]

+1

- Ray

On Fri, Apr 17, 2020 at 11:21 AM David Bosschaert <
david.bosscha...@gmail.com> wrote:

> +1
>
> David
>
> On Fri, 17 Apr 2020 at 15:47, Carsten Ziegeler 
> wrote:
>
> > Hi,
> > we solved one regression in this release:
> > https://issues.apache.org/jira/browse/FELIX-6261
> >
> > Staging repositories:
> > https://repository.apache.org/content/repositories/orgapachefelix-1334
> >
> > You can use this UNIX script to download the release and verify the
> > signatures:
> > https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh 1334 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > Regards
> > Carsten
> > --
> > Carsten Ziegeler
> > Adobe Research Switzerland
> > cziege...@apache.org
> >
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [VOTE] Release Apache Felix Converter 1.0.14

[Raymond Auge]

+1

- Ray

On Fri, Apr 17, 2020, 08:07 Jean-Baptiste Onofre,  wrote:

> +1 (binding)
>
> Regards
> JB
>
> > Le 17 avr. 2020 à 10:26, David Bosschaert 
> a écrit :
> >
> > Hi all,
> >
> > I would like to release org.apache.felix.converter-1.0.14
> >
> > We solved the following issues in this release:
> > https://issues.apache.org/jira/projects/FELIX/versions/12346490
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachefelix-1333
> >
> > You can use this UNIX script to download the release and verify the
> > signatures:
> > https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh 1333 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > Best regards,
> >
> > David Bosschaert
>
>

Re: [VOTE] Release Apache Felix CM Json 1.0.0

[Raymond Auge]

+1

- Ray

On Fri, Apr 17, 2020, 05:00 Karl Pauls,  wrote:

> +1
>
> regards,
>
> Karl
>
> On Friday, April 17, 2020, Carsten Ziegeler  wrote:
>
> > +1
> >
> > Carsten
> >
> > On 17.04.2020 07:50, Carsten Ziegeler wrote:
> >
> >> Hi,
> >>
> >> i've extracted the handling of json based configurations from the
> >> configurator implementation and made a separate api out of it which
> allows
> >> to read/write configuration (resources). Without this api, tooling
> needing
> >> to deal with configuration resources either needed to reinvent the
> wheel or
> >> depend on configurator implementation internals.
> >>
> >> So please cast your vote for the first release of this module
> >>
> >> Staging repositories:
> >> https://repository.apache.org/content/repositories/orgapachefelix-1332
> >>
> >> You can use this UNIX script to download the release and verify the
> >> signatures:
> >> https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> >>
> >> Usage:
> >> sh check_staged_release.sh 1332 /tmp/felix-staging
> >>
> >> Please vote to approve this release:
> >>
> >> [ ] +1 Approve the release
> >> [ ] -1 Veto the release (please provide specific comments)
> >>
> >> Regards
> >> Carsten
> >> --
> >> Carsten Ziegeler
> >> Adobe Research Switzerland
> >> cziege...@apache.org
> >>
> >
> > --
> > --
> > Carsten Ziegeler
> > Adobe Research Switzerland
> > cziege...@apache.org
> >
>
>
> --
> Karl Pauls
> karlpa...@gmail.com
>

Re: [VOTE] Release Apache Felix Parent 7

[Raymond Auge]

+1

- Ray

On Wed, Apr 15, 2020 at 7:53 AM Carsten Ziegeler 
wrote:

> Hi,
>
> i've updated our parent pom to the latest plugin versions, switched to
> Java 8 as the default version (bnd >= 4.0.0 requires it anyway), changed
> http: urls to https: and allow to use Java versions > 9 for a project.
>
> Staging repositories:
> https://repository.apache.org/content/repositories/orgapachefelix-1331
>
> You can use this UNIX script to download the release and verify the
> signatures:
> https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
>
> Usage:
> sh check_staged_release.sh 1331 /tmp/felix-staging
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>
> Regards
> Carsten
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [VOTE] Release Apache Felix SCR 2.1.18

[Raymond Auge]

+1

- Ray

On Mon, Apr 13, 2020 at 12:26 PM  wrote:

> +1
>
> David
>
> On Mon, 13 Apr 2020 at 16:00, Carsten Ziegeler 
> wrote:
>
> > Hi,
> >
> > We solved 9 issues in this release:
> >
> >
> https://github.com/apache/felix-dev/blob/org.apache.felix.scr-2.1.18/scr/changelog.txt
> >
> > Staging repositories:
> > https://repository.apache.org/content/repositories/orgapachefelix-1329
> >
> > You can use this UNIX script to download the release and verify the
> > signatures:
> > https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh 1329 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > Regards
> > Carsten
> > --
> > Carsten Ziegeler
> > Adobe Research Switzerland
> > cziege...@apache.org
> >
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [VOTE] Release http.base 4.0.10, http.bridge 4.0.12, and http.jetty 4.0.18

[Raymond Auge]

+1

- Ray

On Mon, Apr 13, 2020 at 11:43 AM Carsten Ziegeler 
wrote:

> Hi,
>
> We solved 2 issues in http.jetty 4.0.18:
>
>
> https://issues.apache.org/jira/browse/FELIX-6257?jql=project%20%3D%20FELIX%20AND%20fixVersion%20%3D%20http.jetty-4.0.18
>
> and one issue in http.base 4.0.10 and http.bridge 4.0.12:
> https://issues.apache.org/jira/browse/FELIX-6253
>
> Staging repositories:
> https://repository.apache.org/content/repositories/orgapachefelix-1330
>
> You can use this UNIX script to download the release and verify the
> signatures:
> https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
>
> Usage:
> sh check_staged_release.sh 1330 /tmp/felix-staging
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>
> Regards
> Carsten
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: Proposal for a microservice blueprint

[Raymond Auge]

Hi Christian,

I also think it's a good idea. You might be aware that Aries CDI project is
also working toward this exact goal by implementing key Eclipse
MicroProfile parts (with the assistance of Apache Geronimo) which deliver
some of the feature areas you've outlined. The Apache Aries CDI BOM already
contains a great value and a repository of this nature I think is the most
useful resource as a _repo_.

We could do something similar for Felix?

This is just to say that I think it's a great idea and would like to help
work toward that goal.

- Ray


On Sun, Apr 12, 2020 at 7:58 AM Christian Schneider 
wrote:

> Hi Neil,
>
> indeed the idea is to build upon the same building blocks as the enroute
> microservice example but enrich it with everything you need to get a fully
> cloud ready service. It would be ideal to make it modular like spring boot
> with the individual starters you can simply combine. Not sure though if
> that is achievable. The simpler alternative is to provide a OSGi bundle
> repo that has maybe too many bundles but let the resolver choose the needed
> ones.
>
> Christian
>
>
> Am So., 12. Apr. 2020 um 12:44 Uhr schrieb Neil Bartlett <
> njbartl...@gmail.com>:
>
> > Hi Christian,
> >
> > I think this would be great, but it does have a fair degree of overlap
> with
> > enRoute, at least in the early stages. It's always been a problem that
> OSGi
> > offers too many competing ways to do simple things, and if not done well
> > your idea would exacerbate the problem.
> >
> > On the other hand, enRoute is limited to working with OSGi specification
> > technologies, because it is funded by Alliance members who are in
> > competition with each other. So it would be ideal if your effort could be
> > built as an extension to the existing enRoute microservices
> > tutorial/example. The original idea for enRoute was to have a bunch of
> > these extensions, perhaps even linked (though not endorsed) from the
> > enRoute page.
> >
> > Neil
> >
> > On Sun, 12 Apr 2020 at 10:58, Christian Schneider <
> ch...@die-schneider.net
> > >
> > wrote:
> >
> > > In recent years we saw a big trend towards micro services and cloud.
> > > Lately people discovered though that such services are often made too
> > fine
> > > grained.
> > > The newest trend goes to building bigger micro services on the level of
> > > domain driven design bounded contexts.
> > >
> > > Especially for these services OSGi is a very interesting platform as
> they
> > > need more internal structure than the more fine grained services.
> > > Unfortunately it is quite hard to build a cloud native service in OSGi
> > from
> > > scratch.
> > >
> > > So I would like to offer a blueprint for cloud native micro services
> > inside
> > > the felix community. The goal is to provide all parts of a cloud native
> > > system that are usually needed, like:
> > >
> > >  * Declarative services as dependency injection
> > >  * Aries Jaxrs Whiteboard for REST
> > >  * Dropwizard metrics exported as Prometheus metrics
> > >  * Swagger
> > >  * Halbrowser
> > >  * Felix healthchecks
> > >  * Configuration using OSGi configurator + Environment variables plugin
> > >  * Logging to console
> > >  * Final application is provided as a runnable jar
> > >  * Example docker build files
> > >  * Example kubernetes yaml
> > >
> > > What do you think?
> > >
> > > Christian
> > >
> > > --
> > > --
> > > Christian Schneider
> > > http://www.liquid-reality.de
> > >
> > > Computer Scientist
> > > http://www.adobe.com
> > >
> >
>
>
> --
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Computer Scientist
> http://www.adobe.com
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [VOTE] Apache Felix Gogo Parent 6 & Gogo JLine 1.1.6 releases

[Raymond Auge]

It would be nice to also update the gogo BOM, but not a stopper.

+1

- Ray

On Sun, Apr 5, 2020 at 1:54 AM Jean-Baptiste Onofre  wrote:

> Hi everyone,
>
> I’m calling a vote to release Gogo Parent 6 (just to update scm section)
> and Gogo JLine 1.1.6 containing:
>
> * [FELIX-6214] - Gogo JLine range import/upgrade
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachefelix-1328/ <
> https://repository.apache.org/content/repositories/orgapachefelix-1328/>
>
> Please vote to approve this release:
>
>  [ ] + 1 Approve the release
>  [ ] -1 Don’t approve the release (please provide specific comments)
>
> This vote will be open for 72 hours.
>
> Regards
> JB



-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [VOTE] Release Apache Felix Web Console 4.4.0

[Raymond Auge]

+1

- Ray

On Thu, Apr 2, 2020 at 7:06 AM Jean-Baptiste Onofre  wrote:

> +1 (binding)
>
> Regards
> JB
>
> > Le 2 avr. 2020 à 13:00, dav...@apache.org a écrit :
> >
> > Hi all,
> >
> > I would like to release webconsole-4.4.0
> >
> > We solved the following issues in this release:
> > https://issues.apache.org/jira/projects/FELIX/versions/12346045
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachefelix-1327
> >
> > You can use this UNIX script to download the release and verify the
> > signatures:
> > https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh 1327 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > Best regards,
> >
> > David Bosschaert
>
>

-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [VOTE] Release FileInstall 3.6.6

[Raymond Auge]

+1

- Ray

On Wed, Apr 1, 2020 at 9:53 AM David Bosschaert 
wrote:

> +1
>
> David
>
> On Wed, 1 Apr 2020 at 14:36, Jean-Baptiste Onofre  wrote:
>
> > +1 (binding)
> >
> > Regards
> > JB
> >
> > > Le 1 avr. 2020 à 15:34, Guillaume Nodet  a écrit :
> > >
> > > I'm calling a vote to release the following 4 bugs in FileInstall:
> > >* [FELIX-5832] - ConfigInstaller should only handle events for
> > > configurations it manages
> > >* [FELIX-6103] - ConfigInstaller, when using
> > > NotCachablePersistenceManager, can restore cached stale properties
> > >* [FELIX-6109] - NPE from null listener in
> > DirectoryWatcher.findListener
> > >* [FELIX-6211] - fileinstall filter out subdirectories even though
> > > felix.fileinstall.subdir.mode property is set to 'recurse'
> > >
> > > Staging repository:
> > >
> https://repository.apache.org/content/repositories/orgapachefelix-1326/
> > >
> > >
> > > You can use this UNIX script to download the release and verify the
> > > signatures:
> > >
> https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> > >
> > > Usage:
> > > sh check_staged_release.sh 1326 /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.
> > > --
> > > 
> > > Guillaume Nodet
> >
> >
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [VOTE] Release Apache Felix Http Jetty 4.0.16

[Raymond Auge]

+1

- Ray

On Thu, Mar 12, 2020 at 12:18 PM Jean-Baptiste Onofre 
wrote:

> +1 (binding)
>
> Regards
> JB
>
> > Le 12 mars 2020 à 17:15, dav...@apache.org a écrit :
> >
> > Hi all,
> >
> > I would like to release http.jetty-4.0.16
> >
> > We solved the following issues in this release:
> > https://issues.apache.org/jira/projects/FELIX/versions/12346636
> >
> > Staging repositories:
> > https://repository.apache.org/content/repositories/orgapachefelix-1325
> >
> > You can use this UNIX script to download the release and verify the
> > signatures:
> > https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh 1325 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > Best regards,
> >
> > David Bosschaert
>
>

-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: Felix on git(box)

[Raymond Auge]

Furthermore, while traveling you will find that a great many public wifis
block ssh, so you'll have to revert to https in those places anyway.

- Ray

On Fri, Feb 28, 2020 at 9:30 AM Karl Pauls  wrote:

> The default seems to be https theses days - I think we should stick
> with that (FWIW, I converted all scm info in the poms into https).
>
> regards,
>
> Karl
>
> On Fri, Feb 28, 2020 at 3:25 PM Carsten Ziegeler 
> wrote:
> >
> > Sure, that works - or everyone uses ssh. But as soon as we have mixed
> > usage it fails :(
> >
> > Regards
> > Carsten
> >
> > On 28.02.2020 15:23, Raymond Auge wrote:
> > > Carsten, just don't use ssh! Use https for everything. I've never
> > > encountered a problem with that even with gitbox which many other
> Apache
> > > projects already use (aries-* for example).
> > >
> > > - Ray
> > >
> > > On Fri, Feb 28, 2020 at 1:46 AM Carsten Ziegeler  >
> > > wrote:
> > >
> > >> Thanks for all the work and your patience Karl! :)
> > >>
> > >> How do we want to handle splitting out projects into separate git
> > >> repositories? Is a volunteer and a notice via mail enough or do we
> need
> > >> to do a vote?
> > >>
> > >> I'm checking out code using the ssh urls from github, so in order to
> do
> > >> a mvn release I needed to change the connectionUrl in the pom to use
> the
> > >> ssh url (and not the https one). Not sure how we want to handle this?
> > >>
> > >> Regards
> > >> Carsten
> > >>
> > >> On 28.02.2020 00:50, Karl Pauls wrote:
> > >>> Hi,
> > >>>
> > >>> I finished the migration to git. Following the outline from last
> week,
> > >>> we now have two git repositories namely:
> > >>>
> > >>> Felix Dev - https://github.com/apache/felix-dev
> > >>> Felix Atomos - https://github.com/apache/felix-atomos
> > >>>
> > >>> Felix Dev has been migrated with history and I managed to get our
> > >>> release tags hooked up as well. Tom imported Atomos into Felix Atomos
> > >>> too.
> > >>>
> > >>> Subsequently, I created an "archived" branch for the old apache/felix
> > >>> mirror which is at the point the trunk was in. Then, I emptied the
> > >>> trunk, put a readme explaining where to find the new repositories,
> and
> > >>> that the mirror is now considered obsolete.
> > >>>
> > >>> In other words, our third git repo (which is the read-only mirror of
> > >>> svn trunk) is still:
> > >>>
> > >>> Felix - https://github.com/apache/felix
> > >>>
> > >>> but is now only the index to our other repos.
> > >>>
> > >>> Please double check that things are still working for you and that I
> > >>> didn't overlook anything obvious (I did update the scm connections in
> > >>> the poms already).
> > >>>
> > >>> I will go over the website tomorrow and update the info about where
> to
> > >>> find the source code.
> > >>>
> > >>> regards,
> > >>>
> > >>> Karl
> > >>>
> > >>
> > >> --
> > >> --
> > >> Carsten Ziegeler
> > >> Adobe Research Switzerland
> > >> cziege...@apache.org
> > >>
> > >
> > >
> >
> > --
> > --
> > Carsten Ziegeler
> > Adobe Research Switzerland
> > cziege...@apache.org
>
>
>
> --
> Karl Pauls
> karlpa...@gmail.com
>


-- 
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
 (@Liferay)

Re: [VOTE] Release Apache Felix Configadmin Interpolator Plugin 1.1.0

[Raymond Auge]

+1

On Fri, Feb 28, 2020 at 3:34 AM  wrote:

> +1
>
> David
>
> On Fri, 28 Feb 2020 at 08:00, Carsten Ziegeler 
> wrote:
>
> > +1
> >
> > Carsten
> >
> > On 28.02.2020 07:49, Carsten Ziegeler wrote:
> > > We solved two issues in this release:
> > >
> > > https://issues.apache.org/jira/projects/FELIX/versions/12347152
> > >
> > > Staging repositories:
> > > https://repository.apache.org/content/repositories/orgapachefelix-1324
> > >
> > > 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 1324 /tmp/felix-staging
> > >
> > > Please vote to approve this release:
> > >
> > > [ ] +1 Approve the release
> > > [ ] -1 Veto the release (please provide specific comments)
> > >
> > > Regards
> > > Carsten
> > > --
> > > Carsten Ziegeler
> > > Adobe Research Switzerland
> > > cziege...@apache.org
> >
> > --
> > --
> > Carsten Ziegeler
> > Adobe Research Switzerland
> > cziege...@apache.org
> >
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: Felix on git(box)

[Raymond Auge]

Carsten, just don't use ssh! Use https for everything. I've never
encountered a problem with that even with gitbox which many other Apache
projects already use (aries-* for example).

- Ray

On Fri, Feb 28, 2020 at 1:46 AM Carsten Ziegeler 
wrote:

> Thanks for all the work and your patience Karl! :)
>
> How do we want to handle splitting out projects into separate git
> repositories? Is a volunteer and a notice via mail enough or do we need
> to do a vote?
>
> I'm checking out code using the ssh urls from github, so in order to do
> a mvn release I needed to change the connectionUrl in the pom to use the
> ssh url (and not the https one). Not sure how we want to handle this?
>
> Regards
> Carsten
>
> On 28.02.2020 00:50, Karl Pauls wrote:
> > Hi,
> >
> > I finished the migration to git. Following the outline from last week,
> > we now have two git repositories namely:
> >
> > Felix Dev - https://github.com/apache/felix-dev
> > Felix Atomos - https://github.com/apache/felix-atomos
> >
> > Felix Dev has been migrated with history and I managed to get our
> > release tags hooked up as well. Tom imported Atomos into Felix Atomos
> > too.
> >
> > Subsequently, I created an "archived" branch for the old apache/felix
> > mirror which is at the point the trunk was in. Then, I emptied the
> > trunk, put a readme explaining where to find the new repositories, and
> > that the mirror is now considered obsolete.
> >
> > In other words, our third git repo (which is the read-only mirror of
> > svn trunk) is still:
> >
> > Felix - https://github.com/apache/felix
> >
> > but is now only the index to our other repos.
> >
> > Please double check that things are still working for you and that I
> > didn't overlook anything obvious (I did update the scm connections in
> > the poms already).
> >
> > I will go over the website tomorrow and update the info about where to
> > find the source code.
> >
> > regards,
> >
> > Karl
> >
>
> --
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: Felix on git(box)

[Raymond Auge]

+1

- Ray

On Fri, Feb 21, 2020 at 11:54 AM David Jencks 
wrote:

> +1
>
> I think your plan will be a big improvement for now and allow for further
> rearrangement if needed.
>
> thanks!
> David Jencks
>
> > On Feb 21, 2020, at 8:27 AM, Karl Pauls  wrote:
> >
> > Hi,
> >
> > I know i've been dragging my feet with regard to the migration to git.
> > Unfortunately, I didn't find the time until now.
> >
> > I would like to try to make some progress now and there are a couple
> > of points to consider namely,
> >
> > - our website is currently based on svn and we are using the apache
> > cms which IIUC doesn't translate directly to the gitbox support.
> > - with the ip clearance done, Tom would like to have a separate repo
> > for atomos as there are several submodules in atomos already.
> >
> > Hence, I would propose the following:
> >
> > We create two git repos called felix-dev and felix-atomos and keep the
> > current svn for the website.
> >
> > That would mean, we move all of the current svn/trunk into the new
> > felix-dev repo and put a Readme in the svn/trunk instead, pointing to
> > the two new repositories. That way, the website would still work as
> > is, the trunk would be in git, and we could give atomos a separate
> > repo.
> >
> > Effectively, that would give us 3 repos on github for now namely,
> > apache/felix (which is just a Readme pointing to the other two repos),
> > apache/felix-dev, and apache/felix-atomos. If in the future we want to
> > move out other parts of the trunk into their own repo we could do so
> > if we think it makes sense.
> >
> > I should be able to get that done next week and I'll start with it on
> > Tuesday unless somebody really is against it (in other words, I'm
> > calling for lazy consensus).
> >
> > The alternatives I see are to either create a separate repo per module
> > directly or to convert the current svn to just be the felix repo which
> > would require to rework the website with asf.yml support and not give
> > Tom a separate repo for atomos. However, in both cases, we would need
> > some volunteers as I likely don't have enough time.
> >
> > regards,
> >
> > Karl
> >
> > --
> > Karl Pauls
> > karlpa...@gmail.com
>
>

-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [VOTE] Accept the Atomos contribution

[Raymond Auge]

+1

- Ray

On Wed, Jan 29, 2020 at 4:41 PM Karl Pauls  wrote:

> I think the discussion of the "Atomos" contribution
> (https://github.com/tjwatson/atomos) by Thomas Watson has died down by
> now. It looks like there is quite some interest in the idea and
> assuming that the OSGI R8 Core specification will eventually have
> something like the "OSGi Connect" proposal as part of the Core
> Framework specification we would need something in this direction
> anyway.
>
> We should bring it to a vote.
>
> This vote is about officially accepting the donation. If the vote is
> successful I will follow-up with the incubator to get the IP clearance
> sorted out.
>
> Please cast your votes:
>
> [ ] +1 Accept the contribution into Felix
> [ ] -1 Do not
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [DISCUSS] Contribute Atomos to Apache Felix

[Raymond Auge]

Great idea!

+1

- Ray

On Thu, Jan 23, 2020 at 10:09 AM Thomas Watson  wrote:

> Hi,
>
> The OSGI R8 Core specification is currently being worked on by the OSGi
> Alliance.  One of the proposals is to add something called OSGi Connect to
> the Core Framework specification [1] [2].
>
> This specification takes much of its initial inspiration from the current
> Felix Connect/PojoSR project.  The basic idea for OSGI Connect is to allow
> content managed outside of the OSGi Framework to be represented as
> (connected to) bundles installed inside the Framework.
>
> As we have been developing the OSGi Connect specification I have been
> working on a proof of concept called Atomos [3] that implements different
> strategies for representing content managed from outside the Framework as
> bundles inside the framework.  Currently Atomos can run bundles from the
> following environments:
>
> 1) Using the Java class path - Atomos will discover any bundle JARs on the
> class path and represent them as installed bundles.  This most closely
> resembles what Felix PojoSR currently does I think.
>
> 2) Using the Java module path - Atomos will discover all modules in the
> Module Layer hierarchy and represent them as installed bundles.  This
> includes modules that have bundle manifests as well as ones that do not.
> This also extends to the ability to load the framework and set of bundles
> from a jlink image.
>
> 3) Using Graal Substrate native - With additional work to configure native
> compilation Atomos can enable the Framework and a set of bundles to be
> compiled into a native image.
>
> Now that we are progressing the specification for OSGi R8, I would like to
> contribute Atomos to an existing OSGi community where it may gain greater
> adoption and contribution from others. I think Apache Felix is a good fit.
> My plan is to have Atomos work with any OSGi R8 Framework implementation
> that supports OSGi Connect and would have the tests run using both the
> Felix and Equinox Framework to prove it continues to only use OSGi
> specified APIs to do so. The project itself already is Apache-2.0 licensed.
>
> What to others think about contributing Atomos to Apache Felix?
>
> Tom
>
> [1] - https://blog.osgi.org/2019/09/osgi-connect-revisited.html
> [2] -
>
> https://github.com/osgi/design/blob/master/rfcs/rfc0243/rfc-0243-Connect.pdf
> [3] - https://github.com/tjwatson/atomos
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [VOTE] Release Apache Felix Configuration Admin Values Interpolation Plugin 1.0.0

[Raymond Auge]

+1

- Ray

On Fri, Jan 10, 2020, 06:43 Carsten Ziegeler,  wrote:

> +1
>
> Carsten
>
> On 10.01.2020 15:28, Carsten Ziegeler wrote:
> > We solved five issues in this release:
> >
> > https://issues.apache.org/jira/projects/FELIX/versions/12346507
> >
> > Staging repositories:
> > https://repository.apache.org/content/repositories/orgapachefelix-1323/
> >
> > 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 1323 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > Regards
> > Carsten
> > --
> > Carsten Ziegeler
> > Adobe Research Switzerland
> > cziege...@apache.org
>
> --
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>

Re: [Converter] Questions about the Converter

[Raymond Auge]

On Sat, Dec 14, 2019 at 5:50 PM David Leangen  wrote:

> The one released as org.osgi:org.osgi.util.converter is at version 1.0.1,
> while the one release as org.apache.felix:org.apache.felix.converter is at
> 1.0.12.
>

It's just the nature of the beast. Use the Felix one since it has many many
bug fixes more than the OSGi one. We're trying to rectify this situation,
but it's not going to be very soon.


>
> > By the way, why is there such a gap with the OSGi version? (Ok, perhaps
> not the right place to ask the question, but I’ll take whatever answer I
> can get.)
>

You asked in the right place I think! :)


> >
> > Second, what would I need to do to release the serializer and
> schematizer?


Releasing is pretty straightforward, if you follow this guide [1].


> I should still have committer status (unless it gets revoked due to
> inactivity?) but I have never done this before, and I’m not sure of the
> felix conventions and processes.
>

You never lose committer status in Apache projects unless you ask to be
removed :)

Welcome back! :)

[1]
http://felix.apache.org/documentation/development/release-management-nexus.html

-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: December board report

[Raymond Auge]

+1

- Ray

On Wed, Dec 11, 2019, 08:15 Jean-Baptiste Onofré,  wrote:

> +1 it looks good to me.
>
> Thanks !
> Regards
> JB
>
> On 10/12/2019 16:52, Karl Pauls wrote:
> > Hi,
> >
> > please find the board report below. Comments welcome.
> >
> > ## Description:
> >
> > Apache Felix is a project aimed at implementing specifications from the
> OSGi
> >
> > Alliance as well as implementing other supporting tools and technologies
> >
> > aligned with OSGi technology.
> >
> >
> > ## Issues:
> >
> > There are no issues requiring board attention.
> >
> >
> > ## Membership Data:
> >
> > Apache Felix was founded 2007-03-28 (13 years ago)
> >
> > There are currently 67 committers and 27 PMC members in this project.
> >
> > The Committer-to-PMC ratio is roughly 9:4.
> >
> >
> > Community changes, past quarter:
> >
> > - No new PMC members. Last addition was Georg Henzler on 2019-06-10.
> >
> > - No new committers. Last addition was Bertrand Delacretaz on 2018-12-18.
> >
> >
> > ## Project Activity:
> >
> > - Existing implementations have been improved/enhanced based on community
> >
> >   feedback.
> >
> > - We voted to migrate from svn to git(box).
> >
> > - Released 10 components (mostly bug fixes overall).
> >
> >
> > ## Releases:
> >
> > - maven-scr-plugin-1.26.2: 2019-12-07
> >
> > - org.apache.felix.scr.bnd-1.9.6: 2019-12-07
> >
> > - org.apache.felix.scr.generator-1.18.4: 2019-12-07
> >
> > - org.apache.felix.configadmin.plugin.interpolation-0.0.4: 2019-11-14
> >
> > - org.apache.felix.converter-1.0.12: 2019-11-11
> >
> > - org.apache.felix.http.jetty-4.0.14: 2019-09-15
> >
> > - org.apache.felix.http.base-4.0.8: 2019-09-07
> >
> > - org.apache.felix.http.bridge-4.0.10: 2019-09-07
> >
> > - org.apache.felix.http.jetty-4.0.12: 2019-09-07
> >
> >
> > ## Community Health:
> >
> > - Overall the project is in ok health.
> >
> > - Questions on the user list are answered, development concerns are
> either
> >
> >   discussed on the mailing list or directly in the JIRA issues.
> >
> > - The project as well as the OSGi community in general is still in the
> process
> >
> >   of adapting to JPMS and its long term impact.
> >
> > - We need to be on the lookout for new committers. We hope that moving to
> >
> >   git(box) and with that to github we will make it easier to attract new
> >
> >   people.
> >
> > - We had no issues voting on releases and JIRA issues are generally
> addressed.
> >
> > - dev@felix.apache.org had a 31% increase in traffic in the past
> quarter (425
> >
> >   emails compared to 323)
> >
> > - us...@felix.apache.org had a 86% decrease in traffic in the past
> quarter (3
> >
> >   emails compared to 21)
> >
> > - 26 issues opened in JIRA, past quarter (-29% decrease)
> >
> > - 16 issues closed in JIRA, past quarter (-44% decrease)
> >
> > - 30 commits in the past quarter (-70% decrease)
> >
> > - 7 code contributors in the past quarter (no change)
> >
> > - 13 PRs opened on GitHub, past quarter (1300% increase)
> >
> > - 6 PRs closed on GitHub, past quarter (600% increase)
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Release Apache Felix SCR Generator 1.18.4, SCR Bnd Plugin 1.9.6 and Maven SCR Plugin 1.26.4

[Raymond Auge]

+1

On Wed, Dec 4, 2019 at 6:18 AM David Bosschaert 
wrote:

> +1
>
> David
>
> On Wed, 4 Dec 2019 at 09:17, Carsten Ziegeler 
> wrote:
>
> > We solved one issue in the SCR Tooling:
> >
> > https://issues.apache.org/jira/browse/FELIX-6204
> >
> > Staging repositories:
> > https://repository.apache.org/content/repositories/orgapachefelix-1322/
> >
> > 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 1322 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > Regards
> > Carsten
> > --
> > Carsten Ziegeler
> > Adobe Research Switzerland
> > cziege...@apache.org
> >
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Release maven-bundle-plugin with bnd 4.3.1

[Raymond Auge]

Anyone object to releasing maven-bundle-plugin with bnd 4.3.1?

-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [VOTE] Move Felix to git(box)

[Raymond Auge]

+1

- Ray

On Tue, Nov 19, 2019, 05:26 Jean-Baptiste Onofré,  wrote:

> +1
>
> Regards
> JB
>
> On 19/11/2019 10:11, Karl Pauls wrote:
> > Following up on the discussion about moving Felix to git I'd like to
> > call for a vote now.
> >
> > The idea is to ask Infra to move the current svn to gitbox
> > (https://gitbox.apache.org) which will give us a two-master setup of
> > git repositories, allowing committers to utilize two different avenues
> > of committing code; through GitHub or through the ASF (gitbox) -
> > including the ability to work with pull requests on github directly.
> >
> > Please vote to approve this move:
> >
> >   [ ] +1 Move source control to gitbox
> >   [ ]  0 Don't care
> >   [ ] -1 Don't, because ...
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Release Config Admin Interpolation Plugin 0.0.4

[Raymond Auge]

+1

On Wed, Nov 13, 2019, 16:56 Georg Henzler,  wrote:

> +1
>
> - Georg
>
> On 2019-11-11 17:11, clement escoffier wrote:
> > +1,
> >
> > Regards,
> >
> > Clement
> > On 11 Nov 2019 at 14:21 +0100, Raymond Auge ,
> > wrote:
> >> +1
> >>
> >> - Ray
> >>
> >> On Mon, Nov 11, 2019, 05:34 Jean-Baptiste Onofré, 
> >> wrote:
> >>
> >> > +1 (binding)
> >> >
> >> > Regards
> >> > JB
> >> >
> >> > On 11/11/2019 10:36, dav...@apache.org wrote:
> >> > > I would like to call a vote on the Apache Felix Config Admin
> >> > Interpolation
> >> > > Plugin 0.0.4
> >> > >
> >> > > The following issues were fixed:
> >> > > https://issues.apache.org/jira/projects/FELIX/versions/12345964
> >> > >
> >> > > Staging repositories:
> >> > >
> https://repository.apache.org/content/repositories/orgapachefelix-1321/
> >> > >
> >> > > 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 1321 /tmp/felix-staging
> >> > >
> >> > > Please vote to approve this release:
> >> > >
> >> > > [ ] +1 Approve the release
> >> > > [ ] -1 Veto the release (please provide specific comments)
> >> > >
> >> > > This majority vote is open for at least 72 hours.
> >> > >
> >> > > Best regards,
> >> > >
> >> > > David Bosschaert
> >> > >
> >> >
> >> > --
> >> > Jean-Baptiste Onofré
> >> > jbono...@apache.org
> >> > http://blog.nanthrax.net
> >> > Talend - http://www.talend.com
> >> >
>

Re: [VOTE] Release Config Admin Interpolation Plugin 0.0.4

[Raymond Auge]

+1

- Ray

On Mon, Nov 11, 2019, 05:34 Jean-Baptiste Onofré,  wrote:

> +1 (binding)
>
> Regards
> JB
>
> On 11/11/2019 10:36, dav...@apache.org wrote:
> > I would like to call a vote on the Apache Felix Config Admin
> Interpolation
> > Plugin 0.0.4
> >
> > The following issues were fixed:
> > https://issues.apache.org/jira/projects/FELIX/versions/12345964
> >
> > Staging repositories:
> > https://repository.apache.org/content/repositories/orgapachefelix-1321/
> >
> > 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 1321 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > This majority vote is open for at least 72 hours.
> >
> > Best regards,
> >
> > David Bosschaert
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Release Apache Felix Utils 1.11.4

[Raymond Auge]

+1

- Ray

On Sun, Nov 10, 2019 at 2:30 AM Jean-Baptiste Onofré 
wrote:

> Hi all,
>
> I submit Apache Felix Utils 1.11.4 to your vote.
>
> The following issues were fixed:
> https://issues.apache.org/jira/projects/FELIX/versions/12344906
>
> Staging repositories:
> https://repository.apache.org/content/repositories/orgapachefelix-1320/
>
> 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 1320 /tmp/felix-staging
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>
> This majority vote is open for at least 72 hours.
>
> Regards
> JB
>
>

-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [VOTE] Release Felix Converter 1.0.12

[Raymond Auge]

+1

- Ray

On Wed, Nov 6, 2019 at 4:50 AM Jean-Baptiste Onofré  wrote:

> +1 (binding)
>
> Regards
> JB
>
> On 06/11/2019 10:49, dav...@apache.org wrote:
> > I would like to call a vote on the Apache Felix Converter 1.0.12
> >
> > The following issues were fixed:
> > https://issues.apache.org/jira/projects/FELIX/versions/12346062
> >
> > The release now contains an extra artifact, with the 'all' classifier.
> This
> > artifact is the converter _with_ dependencies as before. The jar artifact
> > without the classifier does not contain the external dependencies from
> now
> > on.
> >
> > Staging repositories:
> > https://repository.apache.org/content/repositories/orgapachefelix-1319/
> >
> > 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 1319 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > This majority vote is open for at least 72 hours.
> >
> > Best regards,
> >
> > David Bosschaert
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: Release Felix Converter 1.0.12 soon

[Raymond Auge]

+1 LGTM

- Ray

On Tue, Nov 5, 2019 at 11:36 AM David Bosschaert 
wrote:

> Hi all,
>
> I'm thinking to do a release of the Felix Converter 1.0.12 soon.
> Main difference is that the following issue was fixed:
>
> FELIX-6150 Converter bundle should not embed osgi functions
>
> There will be 2 converter artifacts. One with all it's dependencies, and
> one without embedded dependencies.
>
> Any other issue that should go in the next release?
>
> Best regards,
>
> David
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [Discuss] Another try.. move to git

[Raymond Auge]

+1

Ray

On Sat, Nov 2, 2019, 09:09 Jean-Baptiste Onofré,  wrote:

> It sounds like a plan ;)
>
> +1
>
> Regards
> JB
>
> On 02/11/2019 13:41, Christian Schneider wrote:
> > I propose we first move the whole repo and then extract projects if
> people
> > like this.
> > It is much easier to do the extraction based on a git project.
> >
> > Christian
> >
> > Am Sa., 2. Nov. 2019 um 13:21 Uhr schrieb Jean-Baptiste Onofré <
> > j...@nanthrax.net>:
> >
> >> +1
> >>
> >> The question is: do we keep an unique repository for all felix projects
> >> or we create one git repo per project.
> >>
> >> I would prefer to have one dedicated git repo per project
> >> (felix-framework, felix-configadmin, etc).
> >>
> >> Regards
> >> JB
> >>
> >> On 02/11/2019 10:06, Christian Schneider wrote:
> >>> In the past we discussed a few times about moving felix to git.
> >>>
> >>> A while ago we did this step for Aries and it was simpler than
> >> anticipated.
> >>> The problem in Aries were the remaining small bundles and subprojects
> >> that
> >>> were released by bundle. The larger sub projects were already moved out
> >> to
> >>> separate git repos a while ago.
> >>>
> >>> So the situation was very similar to felix. In the end we opted for the
> >>> simple solution of just migrating the full repo to git with the help of
> >> the
> >>> infra team.
> >>> This works quite fine since then. So I propose we do the same for
> felix.
> >>>
> >>> WDYT?
> >>>
> >>> Christian
> >>>
> >>
> >> --
> >> Jean-Baptiste Onofré
> >> jbono...@apache.org
> >> http://blog.nanthrax.net
> >> Talend - http://www.talend.com
> >>
> >
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTR] Release Apache Felix Http Jetty 4.0.14

[Raymond Auge]

+1

- Ray

On Thu, Sep 12, 2019, 10:50 Jean-Baptiste Onofré,  wrote:

> +1 (binding)
>
> Regards
> JB
>
> On 12/09/2019 07:29, Carsten Ziegeler wrote:
> > We solved two issues in this release:
> >
> >
> https://issues.apache.org/jira/browse/FELIX-6181?jql=project%20%3D%20FELIX%20AND%20fixVersion%20%3D%20http.jetty-4.0.14
> >
> >
> > Staging repositories:
> > https://repository.apache.org/content/repositories/orgapachefelix-1318/
> >
> > 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 1318 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > Regards
> > Carsten
> > --
> > Carsten Ziegeler
> > Adobe Research Switzerland
> > cziege...@apache.org
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Release Apache Felix Http Base 4.0.8, Http Bridge 4.0.10, and Http Jetty 4.0.12

[Raymond Auge]

+1

- Ray

On Wed, Sep 4, 2019 at 5:37 AM David Bosschaert 
wrote:

> +1
>
> David
>
> On Wed, 4 Sep 2019 at 11:06, Carsten Ziegeler 
> wrote:
>
> > Hi,
> >
> > We solved one issue in the http base release:
> > https://issues.apache.org/jira/projects/FELIX/versions/12346011
> >
> > We solved one issue in the http bridge release:
> > https://issues.apache.org/jira/projects/FELIX/versions/12346012
> >
> > We solved four issues in the http jetty release:
> > https://issues.apache.org/jira/projects/FELIX/versions/12345665
> >
> >
> > Staging repositories:
> > https://repository.apache.org/content/repositories/orgapachefelix-1317/
> >
> > 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 1317 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > Regards
> > Carsten
> > --
> > Carsten Ziegeler
> > Adobe Research Switzerland
> > cziege...@apache.org
> >
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [VOTE] Release Apache Felix Log 1.2.2

[Raymond Auge]

+1

- Ray

On Mon, Aug 26, 2019 at 4:42 AM Jelle Nelis  wrote:

> +1
>
> On 26/08/19 09:30, Carsten Ziegeler wrote:
> > Hi,
> >
> > We solved 1 issue in this release:
> >
> > https://issues.apache.org/jira/browse/FELIX-6144
> >
> > Staging repositories:
> > https://repository.apache.org/content/repositories/orgapachefelix-1316/
> >
> > 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 1316 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > Regards
> > Carsten
> > --
> > Carsten Ziegeler
> > Adobe Research Switzerland
> > cziege...@apache.org
>
> --
> ir. Jelle Nelis
> Ghent University - imec
> IDLab
> iGent Tower - Department of Information Technology
> Technologiepark-Zwijnaarde 15, B-9052 Ghent, Belgium
> T: +32 9 331 48 87
> E: jelle.ne...@ugent.be
> W: IDLab.UGent.be
> W: IDLab.technology
>
>

-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [VOTE] Release Felix Converter 1.0.10

[Raymond Auge]

+1

- Ray

On Thu, Aug 22, 2019 at 10:09 AM Carsten Ziegeler 
wrote:

> +1
>
> Am 22.08.2019 um 04:22 schrieb dav...@apache.org:
> > I would like to call a vote on the Apache Felix Converter 1.0.10
> >
> > The following issues were fixed:
> > https://issues.apache.org/jira/browse/FELIX/fixforversion/12345401
> >
> > Staging repositories:
> > https://repository.apache.org/content/repositories/orgapachefelix-1315/
> >
> > 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 1315 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > This majority vote is open for at least 72 hours.
> >
> > Best regards,
> >
> > David Bosschaert
> >
>
> --
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [VOTE] Release Apache Felix Webconsole 4.3.16

[Raymond Auge]

+1

- Ray

On Thu, Aug 22, 2019 at 2:47 AM Karl Pauls  wrote:

> +1
>
> regards,
>
> Karl
>
> On Thu, Aug 22, 2019 at 8:37 AM Jean-Baptiste Onofré 
> wrote:
> >
> > +1 (binding)
> >
> > Regards
> > JB
> >
> > On 20/08/2019 13:10, dav...@apache.org wrote:
> > > I would like to call a vote on the Apache Felix Webconsole 4.3.16
> > >
> > > The recent release 4.3.14 introduced a potential 'already registered'
> > > servlet exception.
> > >
> > > The following issue was fixed:
> > > https://issues.apache.org/jira/projects/FELIX/versions/12346022
> > >
> > > Staging repositories:
> > >
> https://repository.apache.org/content/repositories/orgapachefelix-1314/
> > >
> > > 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 1314 /tmp/felix-staging
> > >
> > > Please vote to approve this release:
> > >
> > > [ ] +1 Approve the release
> > > [ ] -1 Veto the release (please provide specific comments)
> > >
> > > This majority vote is open for at least 72 hours.
> > >
> > > Best regards,
> > >
> > > David Bosschaert
> > >
> >
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
>
>
>
> --
> Karl Pauls
> karlpa...@gmail.com
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: healthcheck: ServiceUnavailableFilter does not kick-in

[Raymond Auge]

By /system/ I guess you are referring to Felix webconsole?

The section of the Http Whiteboard spec that seems relevant is this one [1]

The issue is that the webconsole servlet is added via the legacy
HttpService API. If you wish to filter such paths using Http Whiteboard you
need to look into Felix's proprietary support for mapping Http Whiteboard
Services to legacy Http Service contexts. I do believe Felix supports this
but not sure it's documented.

But Carsten would know!

- Ray

[1]
https://osgi.org/specification/osgi.cmpn/7.0.0/service.http.whiteboard.html#service.http.whiteboard.httpservice.integration

On Tue, Aug 20, 2019 at 9:37 AM Nhut Thai Le  wrote:

> I am using filter.pattern in the mean time but the annoying is that it does
> not allow me to exclude requests for /system/
>
> I posted a question on paxweb , waiting for answer, will update this email
> thread when i have some news
>
> Thanks you for the tips
>
> Thai
>
> On Fri, Aug 16, 2019 at 2:20 AM Georg Henzler  wrote:
>
> > Hi Thai,
> >
> > > As far as I know, standard servlet filter does not allow using regex
> > > to match path so my guess is that the value of
> > > osgi.http.whiteboard.filter.regex service property from OSGI http
> > > whiteboard spec need to be converted into path specs by the whiteboard
> > > implementation (paxweb in my case) before passing it to jetty to check
> > > if the filter should process the request. Am i right?
> >
> > so osgi.http.whiteboard.filter.regex is standard [1], is this a bug in
> > the
> > whiteboard implementation paxweb then?
> >
> > you could also try to leave osgi.http.whiteboard.filter.regex out (as
> > you
> > select a specific context via osgi.http.whiteboard.context.select) or
> > use osgi.http.whiteboard.filter.pattern instead (the properties of
> > ServiceUnavailableFilter are passed one to one to
> > ServiceUnavailableFilter,
> > even if there will be a new one in the future you can just use it).
> >
> > -Georg
> >
> >
> > [1]
> >
> >
> https://osgi.org/specification/osgi.cmpn/7.0.0/service.http.whiteboard.html#d0e121055
> >
> > On 2019-08-15 00:23, Nhut Thai Le wrote:
> > > Hi Georg,
> > >
> > > Some more debug showed me that the cause for ServiceUnavailableFilter
> > > not picking up is due to the osgi.http.whiteboard.filter.regex that I
> > > use. At some point, jetty is building the filter chain to process the
> > > request and the ServiceUnavailableFilter is drop from the chain
> > > because the regex is pass as is to jetty's FilterMapping as a pattern
> > > to compare with the request path, but the compare does not use regex
> > > to match the pattern with the path. Here is the screenshot:
> > >
> >
> > >
> > > Thai
> > >
> > > On Wed, Aug 14, 2019 at 2:49 PM Nhut Thai Le 
> > > wrote:
> > >
> > >> Thank you for your suggestion Georg,
> > >> To address the issue of healthcheck start at level 4 instead of 3 as
> > >> desired, here are what i have tried:
> > >> Make sure the autoDisableFilter is false
> > >>
> > >
> >
> osgi.http.whiteboard.filter.regex=(?!/system/).*osgi.http.whiteboard.context.select=(
> > osgi.http.whiteboard.context.name
> > >> [1]=WebviewerServletContextHelper)
> > >> tags=systemalive
> > >> responseTextFor503=Service Unavailable, wait.. wait... wait
> > >> service.ranking=1
> > >> avoid404DuringStartup=true
> > >> autoDisableFilter=false
> > >>
> > >> I also tried setting service.ranking to 1, but it does not
> > >> change anything
> > >>
> > >> Enabling debug log show me these lines:
> > >> 12:19:02.697 [ConfigurationListener Event Queue] DEBUG
> > >> o.a.f.h.c.i.f.ServiceUnavailableFilter - Reloading HC references for
> > >> tags [systemalive]
> > >> 12:19:02.699 [ConfigurationListener Event Queue] DEBUG
> > >> o.a.f.h.c.i.f.ServiceUnavailableFilter - Found 2 health check
> > >> service references for tags [systemalive]
> > >> 12:19:02.700 [ConfigurationListener Event Queue] DEBUG
> > >> o.a.f.h.c.i.f.ServiceUnavailableFilter - Registered
> > >> ServiceUnavailableFilter for tags [systemalive]
> > >> 12:19:02.701 [ConfigurationListener Event Queue] INFO
> > >> o.a.f.h.c.i.f.ServiceUnavailableFilter - ServiceUnavailableFilter
> > >> active (start level 4)
> > >>
> > >> There is no other log from ServiceUnavailableFilter, and my
> > >> breakpoint in the doFilter of this servlet was never got hit.
> > >> Checking the imports of the healthcheck bundles, i found they
> > >> require some packages from slf4j, lang3, pax-web-api, javax.servlet
> > >> and osgi.service.component so i also changed the start level of
> > >> these bundles to the same level as healthcheck but
> > >> ServiceUnavailableFilter still report start level 4. One question
> > >> here is that once i start playing around with start level i realize
> > >> that I may need to set start level for a lot of infrastructure
> > >> bundles (jetty, paxweb, logging, ...) to be earlier than business
> > >> logic bundles, is it normal since i remember reading somewhere that
> > >> i should let the 

Issues URLs working or not...

[Raymond Auge]

The last 2 votes that used an issues url like
https://issues.apache.org/jira/projects/FELIX/versions/12346015 resulted in
jira error for me. Anyone else?

- Ray

Re: [VOTE] Release Apache Felix Webconsole 4.3.14

[Raymond Auge]

+1

- Ray

On Fri, Aug 16, 2019, 08:05 ,  wrote:

> I would like to call a vote on the Apache Felix Webconsole 4.3.14
>
> The following 2 issues were fixed:
> https://issues.apache.org/jira/projects/FELIX/versions/12346015
>
> Staging repositories:
> https://repository.apache.org/content/repositories/orgapachefelix-1313/
>
> 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 1313 /tmp/felix-staging
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>
> This majority vote is open for at least 72 hours.
>
> Best regards,
>
> David Bosschaert
>

Re: [VOTE] Release Apache Felix Maven Bundle Plugin 4.2.1

[Raymond Auge]

+1

- Ray

On Thu, Aug 15, 2019 at 11:11 AM David Bosschaert <
david.bosscha...@gmail.com> wrote:

> +1
>
> David
>
> On Thu, 15 Aug 2019 at 15:10, Stefan Seifert 
> wrote:
>
> > Hi,
> >
> > We solved 1 issues in this release:
> > https://issues.apache.org/jira/browse/FELIX/fixforversion/12345491
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachefelix-1312/
> >
> > 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 1312 /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.
> >
> > stefan
> >
> >
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: [VOTE] Felix Config Admin Plugin Interpolation 0.0.2

[Raymond Auge]

+1

On Mon, Jul 29, 2019 at 2:15 PM Georg Henzler  wrote:

> (so +1 for the preview release 0.0.2, I think at least the property name
> org.apache.felix.configadmin.plugin.interpolation.dir should be adjusted
> before a 1.0.0)
>
> On 2019-07-29 20:11, Georg Henzler wrote:
> > +1
> >
> > Georg
> >
> > On 2019-07-29 14:35, David Bosschaert wrote:
> >> Here's my +1
> >>
> >> David
> >>
> >> On Mon, 29 Jul 2019 at 12:37, Carsten Ziegeler 
> >> wrote:
> >>
> >>> +1
> >>>
> >>>
> >>> Carsten
> >>>
> >>>
> >>> Davidb wrote
> >>> > Hi all,
> >>> >
> >>> > I would like to propose the very first version of the Apache Felix
> >>> > Configuration Admin interpolation plugin.
> >>> > With this plugin you can substitute values in configuration coming
> from
> >>> > Environment variables, System or Framework Properties or files on
> disk,
> >>> for
> >>> > example to pick up Kubernetes Secrets.
> >>> > For documentation see
> >>> >
> >>>
> https://github.com/apache/felix/blob/trunk/configadmin-plugins/interpolation/README.md
> >>> >
> >>> > SVN Release name:
> >>> > org.apache.felix.configadmin.plugin.interpolation-0.0.2
> >>> >
> >>> > Staging Repository:
> >>> >
> https://repository.apache.org/content/repositories/orgapachearies-1311
> >>> >
> >>> > 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 1311 /tmp/felix-staging
> >>> >
> >>> > Please vote to approve this release:
> >>> >
> >>> > [ ] +1 Approve the release
> >>> > [ ] -1 Don't approve the release (please provide specific comments)
> >>> >
> >>> > This vote will be open for at least 72 hours.
> >>> >
> >>> > Best regards,
> >>> >
> >>> > David
> >>> >
> >>> --
> >>> Carsten Ziegeler
> >>> Adobe Research Switzerland
> >>> cziege...@apache.org
> >>>
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)

Re: Potential Felix contribution: ConfigAdmin plugin that can substitute variable placeholders (e.g. for K8s secrets)

[Raymond Auge]



On Fri, Jul 26, 2019 at 10:20 AM David Bosschaert <
david.bosscha...@gmail.com> wrote:

> While Carsten reviewed the code earlier today he suggested that this
> mechanism be supported, so the plugin is registered with a
> config.plugin.id
> value of 'org.apache.felix.configadmin.plugin.interpolation' [1]
>
> Thanks for the review, Carsten!
>
> David
>
> [1]
>
> https://github.com/apache/felix/blob/trunk/configadmin-plugins/interpolation/src/main/java/org/apache/felix/configadmin/plugin/interpolation/Activator.java#L44
>
> On Fri, 26 Jul 2019 at 15:02, Raymond Auge 
> wrote:
>
> > Perfect (I didn't look at the impl), but as long as there's a way to
> > enforce it! :)
> >
> > - Ray
> >
> > On Fri, Jul 26, 2019 at 9:58 AM Carsten Ziegeler 
> > wrote:
> >
> > > Not sure, if that's what you're looking for, but with FELIX-6059 you
> can
> > > configure the configuration admin to depend on the plugin being
> available
> > >
> > > Carsten
> > >
> > > Raymond Auge wrote
> > > > An idea for the future might be a requirement so that we can make
> sure
> > > the
> > > > feature is available during provisioning of the framework bundles.
> > > >
> > > > - Ray
> > > >
> > > > On Fri, Jul 26, 2019 at 7:12 AM David Bosschaert <
> > > david.bosscha...@gmail.com>
> > > > wrote:
> > > >
> > > >> Thanks for the suggestion, Bertrand!
> > > >>
> > > >> I have renamed the plugin to 'interpolation'.
> > > >> I have also implemented framework/system property based substitution
> > as
> > > >> suggested by JB Onofré
> > > >> And I have added substitution support for environment variables,
> which
> > > can
> > > >> be useful when you'd like to configure your runtime (e.g.
> containers)
> > > >> 12-factor style
> > > >>
> > > >> The code is here:
> > > >>
> > > >>
> > >
> >
> https://svn.apache.org/repos/asf/felix/trunk/configadmin-plugins/interpolation
> > > >> Documentation is best read on github:
> > > >>
> > > >>
> > >
> >
> https://github.com/apache/felix/blob/trunk/configadmin-plugins/interpolation/README.md
> > > >>
> > > >> I'd like to do an initial 0.0.2 release early next week to make it
> > easy
> > > for
> > > >> everyone to try it out.
> > > >>
> > > >> Any suggestions, let me know!
> > > >>
> > > >> Cheers,
> > > >>
> > > >> David
> > > >>
> > > >>
> > > >> On Fri, 26 Jul 2019 at 10:06, Bertrand Delacretaz <
> > > bdelacre...@apache.org>
> > > >> wrote:
> > > >>
> > > >>> Hi,
> > > >>>
> > > >>> On Thu, Jul 25, 2019 at 4:32 PM David Bosschaert
> > > >>>  wrote:
> > > >>>> ...I was thinking of putting it at
> > configadmin-plugins/substitution..
> > > >>>
> > > >>> FWIW, "interpolation" is a common term for that as per
> > > >>> https://en.wikipedia.org/wiki/String_interpolation
> > > >>>
> > > >>> -Bertrand
> > > >>>
> > > >>
> > > >
> > > >
> > > --
> > > Carsten Ziegeler
> > > Adobe Research Switzerland
> > > cziege...@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)
> >
>


-- 
*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: Potential Felix contribution: ConfigAdmin plugin that can substitute variable placeholders (e.g. for K8s secrets)

[Raymond Auge]

Perfect (I didn't look at the impl), but as long as there's a way to
enforce it! :)

- Ray

On Fri, Jul 26, 2019 at 9:58 AM Carsten Ziegeler 
wrote:

> Not sure, if that's what you're looking for, but with FELIX-6059 you can
> configure the configuration admin to depend on the plugin being available
>
> Carsten
>
> Raymond Auge wrote
> > An idea for the future might be a requirement so that we can make sure
> the
> > feature is available during provisioning of the framework bundles.
> >
> > - Ray
> >
> > On Fri, Jul 26, 2019 at 7:12 AM David Bosschaert <
> david.bosscha...@gmail.com>
> > wrote:
> >
> >> Thanks for the suggestion, Bertrand!
> >>
> >> I have renamed the plugin to 'interpolation'.
> >> I have also implemented framework/system property based substitution as
> >> suggested by JB Onofré
> >> And I have added substitution support for environment variables, which
> can
> >> be useful when you'd like to configure your runtime (e.g. containers)
> >> 12-factor style
> >>
> >> The code is here:
> >>
> >>
> https://svn.apache.org/repos/asf/felix/trunk/configadmin-plugins/interpolation
> >> Documentation is best read on github:
> >>
> >>
> https://github.com/apache/felix/blob/trunk/configadmin-plugins/interpolation/README.md
> >>
> >> I'd like to do an initial 0.0.2 release early next week to make it easy
> for
> >> everyone to try it out.
> >>
> >> Any suggestions, let me know!
> >>
> >> Cheers,
> >>
> >> David
> >>
> >>
> >> On Fri, 26 Jul 2019 at 10:06, Bertrand Delacretaz <
> bdelacre...@apache.org>
> >> wrote:
> >>
> >>> Hi,
> >>>
> >>> On Thu, Jul 25, 2019 at 4:32 PM David Bosschaert
> >>>  wrote:
> >>>> ...I was thinking of putting it at configadmin-plugins/substitution..
> >>>
> >>> FWIW, "interpolation" is a common term for that as per
> >>> https://en.wikipedia.org/wiki/String_interpolation
> >>>
> >>> -Bertrand
> >>>
> >>
> >
> >
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@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: Potential Felix contribution: ConfigAdmin plugin that can substitute variable placeholders (e.g. for K8s secrets)

[Raymond Auge]

An idea for the future might be a requirement so that we can make sure the
feature is available during provisioning of the framework bundles.

- Ray

On Fri, Jul 26, 2019 at 7:12 AM David Bosschaert 
wrote:

> Thanks for the suggestion, Bertrand!
>
> I have renamed the plugin to 'interpolation'.
> I have also implemented framework/system property based substitution as
> suggested by JB Onofré
> And I have added substitution support for environment variables, which can
> be useful when you'd like to configure your runtime (e.g. containers)
> 12-factor style
>
> The code is here:
>
> https://svn.apache.org/repos/asf/felix/trunk/configadmin-plugins/interpolation
> Documentation is best read on github:
>
> https://github.com/apache/felix/blob/trunk/configadmin-plugins/interpolation/README.md
>
> I'd like to do an initial 0.0.2 release early next week to make it easy for
> everyone to try it out.
>
> Any suggestions, let me know!
>
> Cheers,
>
> David
>
>
> On Fri, 26 Jul 2019 at 10:06, Bertrand Delacretaz 
> wrote:
>
> > Hi,
> >
> > On Thu, Jul 25, 2019 at 4:32 PM David Bosschaert
> >  wrote:
> > > ...I was thinking of putting it at configadmin-plugins/substitution..
> >
> > FWIW, "interpolation" is a common term for that as per
> > https://en.wikipedia.org/wiki/String_interpolation
> >
> > -Bertrand
> >
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)

Re: [VOTE] Release Felix UserAdmin version 1.6

[Raymond Auge]

+1

- Ray

On Fri, Jun 21, 2019, 07:54 Francois Papon, 
wrote:

> +1 (non-binding)
>
> Thanks!
>
> regards,
>
> François
> fpa...@apache.org
>
> Le 21/06/2019 à 12:36, Peter Kriens a écrit :
> > Hi, We've added a service capability to UserAdmin in this release:
> >
> >   https://issues.apache.org/jira/browse/FELIX-6093
> >
> > Staging repository:
> >
> >
> https://repository.apache.org/content/repositories/orgapachefelix-1310
> >
> > 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 1310 /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.
> >
> > Kind regards,
> >
> >   Peter Kriens
>

Re: [VOTE] Release Apache Felix Configurator 1.0.10

[Raymond Auge]

+1

- Ray

On Mon, Jun 17, 2019 at 7:46 AM Karl Pauls  wrote:

> +1
>
> regards,
>
> Karl
>
> On Sat, Jun 15, 2019 at 6:12 PM Jean-Baptiste Onofré 
> wrote:
> >
> > +1 (binding)
> >
> > Regards
> > JB
> >
> > On 15/06/2019 14:37, Carsten Ziegeler wrote:
> > > We solved one issue in this release:
> > >
> > > https://issues.apache.org/jira/browse/FELIX-6143
> > >
> > > Staging repositories:
> > >
> https://repository.apache.org/content/repositories/orgapachefelix-1305/
> > >
> > > 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 1305 /tmp/felix-staging
> > >
> > > Please vote to approve this release:
> > >
> > > [ ] +1 Approve the release
> > > [ ] -1 Veto the release (please provide specific comments)
> > >
> > > Regards
> > > Carsten
> > > --
> > > Carsten Ziegeler
> > > Adobe Research Switzerland
> > > cziege...@apache.org
> >
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
>
>
>
> --
> Karl Pauls
> karlpa...@gmail.com
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)

Re: [VOTE] Release Apache Felix ConfigAdmin 1.9.16

[Raymond Auge]

+1

- Ray

On Mon, Jun 17, 2019 at 7:46 AM Karl Pauls  wrote:

> +1
>
> regards,
>
> Karl
>
> On Sat, Jun 15, 2019 at 6:12 PM Jean-Baptiste Onofré 
> wrote:
> >
> > +1 (binding)
> >
> > Regards
> > JB
> >
> > On 15/06/2019 14:46, Carsten Ziegeler wrote:
> > > We solved three issues in this release:
> > >
> > >
> https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.configadmin-1.9.16/changelog.txt
> > >
> > >
> > > Staging repositories:
> > >
> https://repository.apache.org/content/repositories/orgapachefelix-1306/
> > >
> > > You can use this UNIX script to download the release and verify the
> > > signatures:
> > > https://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
> > >
> > > Usage:
> > > sh check_staged_release.sh 1306 /tmp/felix-staging
> > >
> > > Please vote to approve this release:
> > >
> > > [ ] +1 Approve the release
> > > [ ] -1 Veto the release (please provide specific comments)
> > >
> > > Regards
> > > Carsten
> > > --
> > > Carsten Ziegeler
> > > Adobe Research Switzerland
> > > cziege...@apache.org
> >
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
>
>
>
> --
> Karl Pauls
> karlpa...@gmail.com
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)

Re: [VOTE] Release Apache Felix Http Bridge 4.0.8 and Http Jetty 4.0.10

[Raymond Auge]

+1

- Ray

On Mon, Jun 17, 2019 at 7:46 AM Karl Pauls  wrote:

> +1
>
> regards,
>
> Karl
>
> On Sat, Jun 15, 2019 at 6:12 PM Jean-Baptiste Onofré 
> wrote:
> >
> > +1 (binding)
> >
> > Regards
> > JB
> >
> > On 15/06/2019 15:06, Carsten Ziegeler wrote:
> > >
> > > We solved one issue for http.bridge:
> > > https://issues.apache.org/jira/projects/FELIX/versions/12345662
> > >
> > > We solved four issues for http.jetty:
> > > https://issues.apache.org/jira/projects/FELIX/versions/12345447
> > >
> > >
> > > Staging repositories:
> > >
> https://repository.apache.org/content/repositories/orgapachefelix-1307/
> > >
> > > You can use this UNIX script to download the release and verify the
> > > signatures:
> > > https://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
> > >
> > > Usage:
> > > sh check_staged_release.sh 1307 /tmp/felix-staging
> > >
> > > Please vote to approve this release:
> > >
> > > [ ] +1 Approve the release
> > > [ ] -1 Veto the release (please provide specific comments)
> > >
> > > Regards
> > > Carsten
> > > --
> > > Carsten Ziegeler
> > > Adobe Research Switzerland
> > > cziege...@apache.org
> >
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
>
>
>
> --
> Karl Pauls
> karlpa...@gmail.com
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)

Re: Potential Felix contribution: ConfigAdmin plugin that can substitute variable placeholders (e.g. for K8s secrets)

[Raymond Auge]

Sounds nice!

- Ray

On Tue, Jun 11, 2019 at 8:30 AM  wrote:

> Hi all,
>
> Some time ago I wrote a small bundle that provides a Configuration Admin
> plugin to substitute placeholders in configuration items with values
> obtained from the local file system. It was initially developed to obtain
> Kubernetes secrets, which surface as local files in the running container.
>
> For example, a configuration PID could be configured in ConfigAdmin like
> this:
> com.my.database:
>   "user": "my-user",
>   "password": "$[secret:db.password]"
>
> With this plugin configured, the value for password is picked up by the
> Configuration Admin plugin from a local file called 'db.password'. The
> entire content of the file is used as value. The file itself can be found
> in a configurable location.
>
> The bundle is quite simple, and while I developed it for a K8s use-case it
> does not have any K8s dependencies, and would probably also apply to other
> use-cases, maybe with some modifications or enhancements.
> What do you think? Would this be an interesting contribution to the Felix
> codebase?
>
> Best regards,
>
> David Bosschaert
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)

Re: June board report

[Raymond Auge]

LGTM

- Ray

On Mon, Jun 10, 2019 at 5:05 PM Karl Pauls  wrote:

> Hi,
>
> Please find the board report below. Comments welcome.
>
> ## Description:
>
>
> Apache Felix is a project aimed at implementing specifications from the
> OSGi
>
> Alliance as well as implementing other supporting tools and technologies
>
> aligned with OSGi technology.
>
>
> ## Issues:
>
>
>  - There are no issues requiring board attention at this time.
>
>
> ## Activity:
>
>
>  - Existing implementations have been improved/enhanced based on community
>
>feedback.
>
>  - Released 11 components (including a new framework release - mostly bug
>
>fixes overall).
>
>
> ## Health report:
>
>
>  - Overall the project is in good health.
>
>  - Questions on the user list are answered, development concerns are either
>
>discussed on the mailing list or directly in the JIRA issues.
>
>  - The project as well as the OSGi community in general is still in the
>
>process of adapting to JPMS and its long term impact.
>
>  - We added 1 new PMC Member (Georg Henzler).
>
>  - We need to be on the lookout for new committers.
>
>  - We had no issues voting on releases and JIRA issues are generally
> addressed
>
>promptly.
>
>
> ## PMC changes:
>
>
>  - Currently 27 PMC members.
>
>  - New PMC members:
>
>- Georg Henzler was added to the PMC on Mon May 10 2019
>
>
> ## Committer base changes:
>
>
>  - Currently 67 committers.
>
>  - No new committers added in the last 3 months
>
>  - Last committer addition was Bertrand Delacretaz at Tue Dec 18 2018
>
>
> ## Releases:
>
>
>  - maven-bundle-plugin-4.2.0 was released on Mon Apr 08 2019
>
>  - org.apache.felix.converter-1.0.8 was released on Tue Apr 23 2019
>
>  - org.apache.felix.framework-6.0.3 was released on Thu May 02 2019
>
>  - org.apache.felix.healthcheck.core-2.0.2 was released on Fri Apr 05 2019
>
>  - org.apache.felix.healthchecks.api-2.0.2 was released on Mon May 20 2019
>
>  - org.apache.felix.healthchecks.core-2.0.6 was released on Mon May 20 2019
>
>  - org.apache.felix.main-6.0.3 was released on Thu May 02 2019
>
>  - org.apache.felix.main.distribution-6.0.3 was released on Thu May 02 2019
>
>  - org.apache.felix.systemready-0.4.2 was released on Fri Apr 05 2019
>
>  - org.apache.felix.webconsole-4.3.12 was released on Mon May 27 2019
>
>  - org.apache.felix.webconsole.plugins.memoryusage-1.0.10 was released on
> Tue
>
>Apr 02 2019
>
>
> ## Mailing list activity:
>
>
>  - us...@felix.apache.org:
>
> - 560 subscribers (down -5 in the last 3 months):
>
> - 58 emails sent to list (63 in previous quarter)
>
>
>  - dev@felix.apache.org:
>
> - 317 subscribers (down -3 in the last 3 months):
>
> - 404 emails sent to list (863 in previous quarter)
>
>
> ## JIRA activity:
>
>
>  - 63 JIRA tickets created in the last 3 months
>
>  - 53 JIRA tickets closed/resolved in the last 3 months
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)

Re: [ANN] Welcome Georg Henzler as a new PMC member

[Raymond Auge]

Welcome Georg!

- Ray

On Tue, Jun 11, 2019 at 2:04 AM Georg Henzler  wrote:

> Hi all,
>
> thanks for bringing me onboard! Looking forward to contributing more and
> having a binding vote for releases :)
>
> -Georg
>
> On 2019-06-10 22:42, Karl Pauls wrote:
> > I'm pleased to announce that the Felix Project Management Committee
> > (PMC) has just elected Georg Henzler as a new PMC member, and he has
> > accepted.
> >
> > Congrats and welcome Georg!
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)

Re: User Admin Release

[Raymond Auge]

Hey Amit,

Please note that I had some issues verifying that the mongodb integration
was working or not. If you could resolve that (with a PR) which I could
verify, then I could do the release. But I feel doing the release with a
potentially broken integration wouldn't be very nice.

Note there;s another thread where I asked for help in this topic.

Sincerely,
- Ray

On Tue, May 21, 2019 at 12:24 PM Amit  wrote:

> Hi Karl and Ray,
>
> In reference to our earlier conversation, I would really appreciate if you
> could build a User Admin release.
>
> Thanks and Regards,
>
> Amit Kumar Mondal
> Phone: +49 160 9100 3436  Email: ad...@amitinside.com
> Skype: arsenalnerk   GitHub: amitjoy
> Blog: blog.amitinside.com



-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)

User Admin mongodb

[Raymond Auge]

Anyone know anything about the mongodb user admin ITests?

I fixed a few issues and the ITests mostly run. I have mongodb server
installed (none of the required configuration is documented btw) but the
mongodb tests are failing in a pax-exam-ish way that I do not understand.

Little help?
-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)

releasing config admin

[Raymond Auge]

Hi,

Anyone object to me releasing config admin? Any one have pending work I
should wait for?

- Ray

-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)

Re: [VOTE] Release Apache Felix Webconsole 4.3.12

[Raymond Auge]

+1

- Ray

On Tue, May 21, 2019 at 10:46 PM Francois Papon <
francois.pa...@openobject.fr> wrote:

> +1 (non-binding)
>
> Thanks!
>
> regards,
>
> François
> fpa...@apache.org
>
> Le 21/05/2019 à 17:08, Karl Pauls a écrit :
> > I would like to call a vote on the Apache Felix Webconsole 4.3.12
> >
> > The main changelogs are in jira and at:
> >
> https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.webconsole-4.3.12/changelog.txt
> >
> > Staging repositories:
> > https://repository.apache.org/content/repositories/orgapachefelix-1304/
> >
> > 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 1304 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)

Re: [VOTE] Release Apache Felix Webconsole 4.3.10

[Raymond Auge]

+1

 - Ray

On Thu, May 16, 2019, 08:18 Jean-Baptiste Onofré,  wrote:

> +1 (binding)
>
> Regards
> JB
>
> On 15/05/2019 22:47, Karl Pauls wrote:
> > I would like to call a vote on the Apache Felix Webconsole 4.3.10
> >
> > The main changelogs are in jira and at:
> >
> https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.webconsole-4.3.10/changelog.txt
> >
> > Staging repositories:
> > https://repository.apache.org/content/repositories/orgapachefelix-1303/
> >
> > 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 1303 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [VOTE] Release Health Check API 2.0.2, Health Check Core 2.0.6

[Raymond Auge]

+1

Numbers are cheap, so it's all good.

"Release early, Release often. And listen to your customers." - Eric S.
Raymond

- Ray

On Wed, May 15, 2019 at 4:08 PM Georg Henzler  wrote:

> Hi,
>
> 
> Sorry I have to release again due to a regression (FELIX-6130), but I
> also implemented a new feature (logging) and fixed another bug. The API
> change does not require a version bump of the semantic version, here we
> are still at 2.0.0.
> 
>
> We solved 3 issues in Health Check API 2.0.2 / Health Check Core 2.0.6:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20FELIX%20AND%20fixVersion%20in%20(%22healthcheck.core%202.0.6%22%2C%22healthcheck.api%202.0.2%22)
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachefelix-1302/
>
> 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 1302 /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.
>
> -Georg
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)

Re: [VOTE] Release Health Check Core 2.0.4, Health Check General Checks 2.0.4

[Raymond Auge]

+1

- Ray

On Wed, May 8, 2019 at 6:34 PM Georg Henzler  wrote:

> Hi,
>
> We solved 2 issues in Health Check Core 2.0.4:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20FELIX%20AND%20fixVersion%20%3D%20
> "healthcheck.core%202.0.4"
>
> We solved 2 issues in Health Check General Checks 2.0.4:
>
> https://issues.apache.org/jira/issues/?jql=project+%3D+FELIX+AND+fixVersion+%3D+%22healthcheck.generalchecks+2.0.4%22
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachefelix-1301/
>
> 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 1301 /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.
>
> -Georg
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)

Re: [VOTE] Release Apache Felix Http Proxy 3.0.6

[Raymond Auge]

+1

- Ray

On Wed, May 8, 2019 at 9:21 AM Carsten Ziegeler 
wrote:

> +1
>
>
> Carsten
>
>
> Carsten Ziegeler wrote
> > We solved two issues in this release:
> >
> > https://issues.apache.org/jira/projects/FELIX/versions/12345474
> >
> > Staging repositories:
> > https://repository.apache.org/content/repositories/orgapachefelix-1300/
> >
> > 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 1300 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > Regards
> > Carsten
> > --
> > Carsten Ziegeler
> > Adobe Research Switzerland
> > cziege...@apache.org
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance  (@OSGiAlliance)