Tested and checked signatures;

+1 (binding)

thanks !

BR
/pierre

On Wed, Oct 5, 2016 at 4:35 PM, Raymond Auge <[email protected]>
wrote:

> +1 (non-binding)
>
> On Wed, Oct 5, 2016 at 9:46 AM, Clement Escoffier <
> [email protected]> wrote:
>
> > +1,
> >
> > Regards,
> >
> > Clement
> > > On 5 oct. 2016, at 07:02, Karl Pauls <[email protected]> wrote:
> > >
> > > +1
> > >
> > > regards,
> > >
> > > Karl
> > >
> > > On Wed, Oct 5, 2016 at 1:25 PM, Carsten Ziegeler <[email protected]
> >
> > > wrote:
> > >
> > >> I would like to call a vote on the following subproject releases:
> > >>
> > >> Http Base 3.0.16 (2 issues)
> > >> https://issues.apache.org/jira/browse/FELIX/fixforversion/12338092
> > >>
> > >> Http Bridge 3.0.16 (2 issues)
> > >> https://issues.apache.org/jira/browse/FELIX/fixforversion/12338093
> > >>
> > >> Http Jetty 3.4.0 (3 issues)
> > >> https://issues.apache.org/jira/browse/FELIX/fixforversion/12338094
> > >>
> > >>
> > >> Staging repositories:
> > >> https://repository.apache.org/content/repositories/
> orgapachefelix-1141/
> > >> https://repository.apache.org/content/repositories/
> orgapachefelix-1142/
> > >>
> > >> 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 1141 /tmp/felix-staging
> > >> sh check_staged_release.sh 1142 /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
> > >> [email protected]
> > >>
> > >
> > >
> > >
> > > --
> > > Karl Pauls
> > > [email protected]
> >
> >
>
>
> --
> *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