I apologise, I didn't read David's email properly. Since the spec JARs are
already released, there is no problem.

+1 from me.

On Mon, Apr 23, 2018 at 2:54 PM, Neil Bartlett <njbartl...@gmail.com> wrote:

> Is there any chance the Converter spec might change before R7 is released?
> Just thinking about the wisdom of publishing this as 1.0.0 before the spec
> it implements is final...
>
> On Mon, Apr 23, 2018 at 2:43 PM, Raymond Auge <raymond.a...@liferay.com>
> wrote:
>
>> +1 nonbinding
>>
>> - Ray
>>
>> On Mon, Apr 23, 2018 at 9:23 AM, Carsten Ziegeler <cziege...@apache.org>
>> wrote:
>>
>> > +1
>> >
>> >
>> > David Bosschaert wrote
>> > > Hi all,
>> > >
>> > > I would like to call a vote on the Felix Converter version 1.0.0.
>> > > The Converter implements chapter 707 of the new OSGi R7 Compendium
>> > > Specifications which can be found here:
>> > > https://osgi.org/specification/osgi.cmpn/7.0.0/util.converter.html
>> > >
>> > > As the OSGi R7 API is now available in Maven Central as released
>> > artifacts,
>> > > the release of the Felix Converter can take place.
>> > >
>> > > Staging repositories:
>> > > https://repository.apache.org/content/repositories/orgapache
>> felix-1218/
>> > >
>> > > 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 1218 /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 at least 72 hours.
>> > >
>> > > Best regards,
>> > >
>> > > David
>> > >
>> > --
>> > 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)
>>
>
>

Reply via email to