+1

Checked:
 - mvn clean package verify (MacOS)
 - signatures

Thanks,
Sergey

On Wed, Dec 9, 2020 at 9:34 PM Ifropc <[email protected]> wrote:
>
> +1
>
> Checked the usual (mvn package verify and signatures)
>
> Thanks,
> Gleb.
>
>
> Sent with ProtonMail Secure Email.
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Wednesday, December 9, 2020 12:46 AM, Sergey Kamov <[email protected]> 
> wrote:
>
> > +1
> >
> >  - checked files,
> >
> >  - mvn (package, verify) under mac
> >
> > Remarks: Note please that jira link
> > (https://issues.apache.org/jira/projects/NLPCRAFT/versions/12349298) is
> > related to main NlpCrat project, but not to java client project.
> >
> > Regards,
> >
> > Sergey
> >
> > 08.12.2020 05:11, Aaron Radzinski пишет:
> >
> > > NLPCraft-ers,
> > > This is a call for a vote to release Apache NLPCraft - Java Client
> > > (incubating) version 0.7.2. This release includes bug fixes and necessary
> > > updates for NLPCraft ver. 0.7.2 (main project).
> > > NOTE: NLPCraft Java Client is a Java wrapper for NLPCraft REST APIs. It is
> > > contained in its own Git repository but shares the same JIRA project as 
> > > the
> > > main NLPCraft project. Community plans to release Java Client along with
> > > the main project to maintain a simple compatibility matrix.
> > > Release information:
> > >
> > > 1.  Release location:
> > >     
> > > https://dist.apache.org/repos/dist/dev/incubator/nlpcraft/java-client/0.7.2/
> > >
> > > 2.  Git tag:
> > >     https://github.com/apache/incubator-nlpcraft-java-client/tree/v0.7.2
> > >
> > > 3.  JIRA issues fixed in release:
> > >     https://issues.apache.org/jira/projects/NLPCRAFT/versions/12349298
> > >
> > > 4.  KEYS file:
> > >     https://dist.apache.org/repos/dist/release/incubator/nlpcraft/KEYS
> > >
> > >
> > > The vote will be open for at least 72 hours or until a necessary number of
> > > votes are reached.
> > > Please vote accordingly:
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > > Thank you,
> > > Aaron (NLPCraft community).
>
>

Reply via email to