+1 (binding)

- mvn clean verify for (Scala 2.10, Hadoop 2.3.0), (Scala 2.11, Hadoop
2.4.1), (Scala 2.10, Hadoop 2.6.3), (Scala 2.11, Hadoop 2.7.2)
- Run examples using the FliRRT tool on multi node cluster.

Cheers,
Till

On Wed, Oct 12, 2016 at 5:32 PM, Neelesh Salian <nsal...@cloudera.com>
wrote:

> + 1 (non-binding)
>
> -  For Hadoop 2.x: mvn clean install -DskipTests -Dhadoop.version=2.6.3
> - For Hadoop 1.x: mvn clean install -DskipTests -Dhadoop.profile=1
> - For Scala 2.11: tools/change-scala-version.sh 2.11, mvn clean install
> -DskipTests
>
> Ran Examples for Batch and Streaming after initiating the local and cluster
> setup.
>
> Thank you for working on this.
>
>
> On Wed, Oct 12, 2016 at 6:53 AM, Stephan Ewen <se...@apache.org> wrote:
>
> > +1 (binding)
> >
> >  - Verified that no changed to LICENSE or NOTICE necessary since the last
> > release
> >  - mvn clean verily for Scala 2.11, Hadoop 2.6.3 including YARN tests
> >
> >
> > On Wed, Oct 12, 2016 at 3:22 PM, Fabian Hueske <fhue...@gmail.com>
> wrote:
> >
> > > +1 to release (binding)
> > >
> > > - checked hashes and signatures
> > > - checked diffs against 1.1.2: no dependencies added or modified
> > > - successfully built Flink from source archive
> > >   - mvn clean install (Scala 2.10)
> > >
> > > Cheers, Fabian
> > >
> > > 2016-10-12 14:05 GMT+02:00 Maximilian Michels <m...@apache.org>:
> > >
> > > > +1 (binding)
> > > >
> > > > - scanned commit history for changes
> > > > - ran "mvn clean install -Dhadoop.version=2.6.0 -Pinclude-yarn-tests"
> > > > successfully
> > > > - started cluster via "./bin/start-cluster.sh"
> > > > - run batch and streaming examples via web interface and CLI
> > > > - used web interface for monitoring
> > > > - ran example job with quickstart project and staging repository
> > > > (cleaned .m2 cache for 1.1.3 before doing that)
> > > > - various tests with ContinuousFileMonitoringFunction and verified
> the
> > > > fix from the previous RC1
> > > >
> > > >
> > > > -Max
> > > >
> > > >
> > > > On Tue, Oct 11, 2016 at 4:40 PM, Robert Metzger <rmetz...@apache.org
> >
> > > > wrote:
> > > > > +1 for releasing this as Flink 1.1.3
> > > > >
> > > > > - Checked the staging repository for hadoop2 / hadoop1 mixup;
> > > quickstart
> > > > > version; build a test project against repository
> > > > > - Checked the artifacts:
> > > > >    - src doesn't contain any binaries
> > > > >    - started Flink locally & executed example & checked web
> interface
> > > > >
> > > > >
> > > > >
> > > > > On Mon, Oct 10, 2016 at 6:52 PM, Ufuk Celebi <u...@apache.org>
> wrote:
> > > > >
> > > > >> Dear Flink community,
> > > > >>
> > > > >> Please vote on releasing the following candidate as Apache Flink
> > > version
> > > > >> 1.1.3.
> > > > >>
> > > > >> The commit to be voted on:
> > > > >> 8e8d454 (http://git-wip-us.apache.org/
> > repos/asf/flink/commit/8e8d454)
> > > > >>
> > > > >> Branch:
> > > > >> release-1.1.3-rc2
> > > > >> (https://git1-us-west.apache.org/repos/asf/flink/repo?p=flin
> > > > >> k.git;a=shortlog;h=refs/heads/release-1.1.3-rc2)
> > > > >>
> > > > >> The release artifacts to be voted on can be found at:
> > > > >> http://people.apache.org/~uce/flink-1.1.3-rc2/
> > > > >>
> > > > >> The release artifacts are signed with the key with fingerprint
> > > 9D403309:
> > > > >> http://www.apache.org/dist/flink/KEYS
> > > > >>
> > > > >> The staging repository for this release can be found at:
> > > > >> https://repository.apache.org/content/repositories/orgapache
> > > flink-1106
> > > > >>
> > > > >> -------------------------------------------------------------
> > > > >>
> > > > >> RC2 adds two new commits since RC1. If there are no objections, I
> > > > >> would like to reduce the voting time to (at least) 2 days. The
> vote
> > > > >> passes if a majority of at least three +1 PMC votes are cast.
> > > > >>
> > > > >> The vote ends on Wed, October 12th, 2016.
> > > > >>
> > > > >> [ ] +1 Release this package as Apache Flink 1.1.3
> > > > >> [ ] -1 Do not release this package, because ...
> > > > >>
> > > >
> > >
> >
>
>
>
> --
> Neelesh Srinivas Salian
> Customer Operations Engineer
>

Reply via email to