Thanks everyone for trying out rc0 and providing feedback.

There were PRs submitted for minor issues that were identified in rc0. I
have merged most of them locally last night.

I will merge the rest shortly, do some sanity testing and prepare a rc1.

----------------------
Sent from mobile
On Nov 9, 2015 6:17 PM, "Swapnil Daingade" <swapnil.daing...@gmail.com>
wrote:

> Downloaded rc0 tar.gz. Built and deployed on 3 node MapR cluster. Tested NM
> flexup/flexdown with HA enabled and disabled. Tried Framework Shutdown.
> All operations worked as expected.
>
> Will try out rc1 if we plan to cut one. Else +1
>
> Regards
> Swapnil
>
>
> On Mon, Nov 9, 2015 at 5:54 PM, yuliya Feldman <yufeld...@yahoo.com.invalid
> >
> wrote:
>
> > We have found an issue with MYRIAD-162
> > Executor values (cpu, mem) counted twice.  It is not a big issue, since
> it
> > is only adding additional 0.2 CPU and some amount of memory.
> > I have a fix for this - will submit PR shortly.
> > Other then that
> > +1 (non-binding)
> > Checked signatureDownloaded tar.gzBuilt from tar.gzDeployed on one node
> > clusterTested NM/JHS flexup/downRun M/R job successfully
> > Thanks,Yuliya
> >
> >       From: Santosh Marella <smare...@maprtech.com>
> >  To: dev@myriad.incubator.apache.org
> >  Sent: Monday, November 9, 2015 5:05 PM
> >  Subject: Re: [VOTE] Release apache-myriad-0.1.0-incubating (release
> > candidate 0)
> >
> > Changed Myriad version to 0.1.0 in the code and github documentation.
> >  PR: https://github.com/apache/incubator-myriad/pull/37
> >
> > Updated the Wiki documentation with hadoop version changed to 2.7.0 and
> > myriad version changed to 0.1.0.
> >
> > @Adam, et al., any other feedback on rc0 ?
> >
> > Unless more code changes are anticipated, I can cut a rc1 once the
> > outstanding PRs are reviewed.
> >
> >
> >
> > Santosh
> >
> >
> >
> > On Mon, Nov 9, 2015 at 1:29 AM, Adam Bordelon <a...@mesosphere.io>
> wrote:
> >
> > > Do we need to rev the version on the executor jars up to 0.1.0?
> > > Is there anywhere else we need to bump the version?
> > >
> > > $ grep -rin "myriad.*[^ \[\(0-9]0" . |grep -v Apache
> > > ./docker/Dockerfile:34:ADD /libs/myriad-executor-runnable-0.0.1.jar
> > > /usr/local/libexec/mesos/
> > > ./docker/ResourceManager.dockerfile:30:ADD
> > > /libs/myriad-executor-runnable-0.0.1.jar /usr/local/libexec/mesos/
> > > ./docker/build-myriad.sh:40:cp -rf
> > > ../myriad-executor/build/libs/myriad-executor-runnable-0.0.1.jar libs/
> > > ./docs/vagrant.md:100
> > > :/vagrant/myriad-scheduler/build/libs/myriad-executor-0.0.1.jar
> > > ./docs/vagrant.md:107:cp
> > > /vagrant/myriad-executor/build/libs/myriad-executor-0.0.1.jar
> > > $YARN_HOME/share/hadoop/yarn/lib/
> > > ./docs/vagrant.md:150:  path:
> > >
> >
> file://localhost/usr/local/libexec/mesos/myriad-executor-runnable-0.0.1.jar
> > > ./docs/myriad-dev.md:67:cp
> > > myriad-executor/build/libs/myriad-executor-0.0.1.jar
> > > /opt/hadoop-2.7.1/share/hadoop/yarn/lib/
> > > ./docs/myriad-remote-distribution-configuration.md:39:cp
> > > myriad-executor/build/libs/myriad-executor-0.0.1.jar
> > > /opt/hadoop-2.7.1/share/hadoop/yarn/lib/
> > > ./myriad-scheduler/src/main/resources/myriad-config-default.yml:55:
> > path:
> > > file:///usr/local/libexec/mesos/myriad-executor-runnable-0.0.1.jar
> > > ./myriad-scheduler/src/main/resources/myriad-config-default.yml:58:
> > #path:
> > > hdfs://namenode:port/dist/myriad-executor-runnable-0.0.1.jar
> > >
> > >
> >
> ./myriad-scheduler/src/main/java/org/apache/myriad/configuration/MyriadConfiguration.java:55:
> > > * path:
> > >
> >
> file://localhost/usr/local/libexec/mesos/myriad-executor-runnable-0.0.1.jar
> > >
> ./myriad-scheduler/src/test/resources/myriad-config-test-default.yml:31:
> > > path:
> file:///usr/local/libexec/mesos/myriad-executor-runnable-0.0.1.jar
> > >
> ./myriad-scheduler/src/test/resources/myriad-config-test-default.yml:34:
> > > #path: hdfs://namenode:port/dist/myriad-executor-runnable-0.0.1.jar
> > >
> > >
> > > On Mon, Nov 9, 2015 at 1:20 AM, Santosh Marella <smare...@maprtech.com
> >
> > > wrote:
> > >
> > > > I haven't created a git tag for the rc. I will try creating one in
> the
> > > > morning.
> > > >
> > > > ----------------------
> > > > Sent from mobile
> > > > On Nov 9, 2015 1:10 AM, "Adam Bordelon" <a...@mesosphere.io> wrote:
> > > >
> > > > > Awesome! I'll try to build and run this myself this week.
> > > > > Is there a git tag I can sync to for 0.1.0-rc0?
> > > > >
> > > > > On Mon, Nov 9, 2015 at 1:01 AM, Santosh Marella <
> > smare...@maprtech.com
> > > >
> > > > > wrote:
> > > > >
> > > > > > Hi all,
> > > > > >
> > > > > > I have created a build for Apache Myriad 0.1.0-incubating,
> release
> > > > > > candidate 0.
> > > > > >
> > > > > > Thanks to everyone who has contributed to this release.
> > > > > >
> > > > > > Here’s the release notes:
> > > > > > https://cwiki.apache.org/confluence/display/MYRIAD/Release+Notes
> > > > > >
> > > > > > The commit to be voted upon is:
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/apache/incubator-myriad/commit/343a11aceb0fc9b5c84f46bba43b2423643eff6f
> > > > > >
> > > > > > The artifacts to be voted on are located here:
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/myriad/myriad-0.1.0-incubating-rc0/
> > > > > >
> > > > > > Release artifacts are signed with the following key:
> > > > > > https://people.apache.org/keys/committer/smarella.asc
> > > > > >
> > > > > > Please vote on releasing this package as Apache Myriad
> > > > 0.1.0-incubating.
> > > > > >
> > > > > > The vote is open for the next 72 hours and passes if a majority
> of
> > > > > > at least three +1 PPMC votes are cast.
> > > > > >
> > > > > > [ ] +1 Release this package as Apache Myriad 0.1.0-incubating
> > > > > > [ ]  0 I don't feel strongly about it, but I'm okay with the
> > release
> > > > > > [ ] -1 Do not release this package because...
> > > > > >
> > > > > >
> > > > > > Here is my vote:
> > > > > > +1 (binding)
> > > > > >
> > > > > > Thanks,
> > > > > > Santosh
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> >
>

Reply via email to