[jira] [Resolved] (ARIES-1665) Initial contribution of implementation of OSGi RFC-193

2017-01-24 Thread David Bosschaert (JIRA)
[ https://issues.apache.org/jira/browse/ARIES-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert resolved ARIES-1665. - Resolution: Fixed Committed in the following commits with many thanks!

[jira] [Commented] (ARIES-1665) Initial contribution of implementation of OSGi RFC-193

2017-01-24 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/ARIES-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836898#comment-15836898 ] ASF GitHub Bot commented on ARIES-1665: --- Github user asfgit closed the pull request at:

[jira] [Commented] (ARIES-1665) Initial contribution of implementation of OSGi RFC-193

2017-01-24 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/ARIES-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836897#comment-15836897 ] ASF subversion and git services commented on ARIES-1665: Commit 1780127 from

[GitHub] aries pull request #64: ARIES-1665 Initial contribution of implementation of...

2017-01-24 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/aries/pull/64 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (ARIES-1665) Initial contribution of implementation of OSGi RFC-193

2017-01-24 Thread ASF subversion and git services (JIRA)
[ https://issues.apache.org/jira/browse/ARIES-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836867#comment-15836867 ] ASF subversion and git services commented on ARIES-1665: Commit 1780123 from

Re: [DISCUSS] [POLICY] IP tracking for OSGi APIs

2017-01-24 Thread Carsten Ziegeler
Guillaume Nodet wrote > My point is that there is a source identified, preferably public if > possible, private if not. > > Of course if the API is not public, we can refer to the private commit so > that PMC members which are not OSGi members can be confident about the IP > tracking. > I think

Re: [DISCUSS] [POLICY] IP tracking for OSGi APIs

2017-01-24 Thread Guillaume Nodet
My point is that there is a source identified, preferably public if possible, private if not. Of course if the API is not public, we can refer to the private commit so that PMC members which are not OSGi members can be confident about the IP tracking. I think it depends on what stage the API is.

Re: [DISCUSS] [POLICY] IP tracking for OSGi APIs

2017-01-24 Thread Carsten Ziegeler
Guillaume Nodet wrote > 2017-01-24 0:02 GMT+01:00 Carsten Ziegeler : > >> Guillaume Nodet wrote >>> Well maybe it should, but again, I don't think it has always been done >>> correctly in the past... >>> Hence this proposal to discuss what options we have to actually

Re: [DISCUSS] [POLICY] IP tracking for OSGi APIs

2017-01-24 Thread Guillaume Nodet
2017-01-24 0:02 GMT+01:00 Carsten Ziegeler : > Guillaume Nodet wrote > > Well maybe it should, but again, I don't think it has always been done > > correctly in the past... > > Hence this proposal to discuss what options we have to actually correctly > > implement it. > > >