Thanks Adam, I think 194 was a typo I believe I meant 195 (node manager dieing). Currently I haven't noticed the behavior so it will depend on root cause. On Apr 8, 2016 4:51 AM, "Adam Bordelon" <a...@mesosphere.io> wrote:
Thanks for heading this up Darin! Here's a link to the JIRA Issues page for Myriad 0.1.1: https://issues.apache.org/jira/browse/MYRIAD/fixforversion/12335455/?selectedTab=com.atlassian.jira.jira-projects-plugin:version-issues-panel Looking at MYRIAD-194, it seems to be a new feature request, and only bugfixes should go into a patch release like 0.1.1, so I vote against its inclusion. MYRIAD-191 could be worth including, depending on the root-cause. On Wed, Apr 6, 2016 at 11:06 AM, Darin Johnson <dbjohnson1...@gmail.com> wrote: > Hi, > > I'm the release manager for Myriad 0.1.1, which we're hoping to get out in > the next couple weeks. Here's the list of PR's and JIRA's that I think > should go into the release since 0.1.0: > > Complete: > #56 MYRIAD-181 Build failure due to dependency on zookeeper test jar > <https://github.com/apache/incubator-myriad/pull/56> > #57 MYRIAD-153: tasks not finishing when FGS is enabled > #60 MYRIAD-186 Clean up the build > <https://github.com/apache/incubator-myriad/pull/60> > #62 Myriad 188 - NodeManager switch to UNHEALTHY causes NPE > <https://github.com/apache/incubator-myriad/pull/62> > #63 MYRIAD-171, MYRIAD-190 > <https://github.com/apache/incubator-myriad/pull/63>, compatibility issues > with 2.7.1+ and 2.6.2+ > > Todo: > Myriad-192 > > Possibly (Pending determination of issue): > Myriad-194 > Myriad-191 > > This is certainly open for discussion so if you think something should be > added or removed please respond. This is a fix release so no new features > are to be added. However, we plan to release 0.2.0 shortly after so new > features can be added then. > > Darin
