Great I'm calling it. Also, if anyone wants to test or provide feedback on https://github.com/apache/incubator-myriad/pull/64 that would be awesome. It still needs work, but if you have hdfs up it takes about a half hour to get a Myriad up, I'm working on streamlining it a bit. Would also like to get the base docker images hosted on something other than my personal dockerhub. On Thu, Apr 21, 2016 at 12:16 AM, Santosh Marella <smare...@maprtech.com> wrote:
> Agreed. Let's just do a 0.2.0 rather than a 0.1.1. > > Santosh > > On Wed, Apr 20, 2016 at 6:28 PM, Swapnil Daingade <sdaing...@maprtech.com> > wrote: > > > +1 > > > > Another change to the roadmap was to move the security work to 0.3 > release. > > > > Regards > > Swapnil > > > > > > > > On Wed, Apr 20, 2016 at 6:04 PM, Adam Bordelon <a...@mesosphere.io> > wrote: > > > > > +1 to skipping 0.1.1 if 0.2.0 is coming soon enough > > > I don't think we have any production users eagerly awaiting the 0.1.1 > > fixes > > > > > > On Wed, Apr 20, 2016 at 5:52 PM, Darin Johnson < > dbjohnson1...@gmail.com> > > > wrote: > > > > > > > Hey Zachary! Thanks, for the upvote. > > > > > > > > Also if you're looking for projects ping me! I'm going to be adding > > more > > > > tickets in the next few days. > > > > > > > > On Wed, Apr 20, 2016 at 8:38 PM, Zachary Jaffee <z...@case.edu> > wrote: > > > > > > > > > If I recall the original reason for the 0.1.1 release was that it > > would > > > > be > > > > > able to get it out earlier than the 0.2.0 release. Since it looks > > like > > > > they > > > > > will be released at the same time essentially, the reason to > release > > > > 0.1.1 > > > > > over just waiting to release 0.2.0 goes away. > > > > > > > > > > On Wed, Apr 20, 2016 at 5:29 PM, Darin Johnson < > > > dbjohnson1...@gmail.com> > > > > > wrote: > > > > > > > > > > > During the dev sync today we discussed the upcoming 0.1.1 and > 0.2.0 > > > > > > releases. Currently, the only out standing issue for 0.1.1 is > > > > MYRIAD-192 > > > > > > (Cgroups), for Myriad 0.2.0 the outstanding issues are Myriad-36 > > and > > > > > Myriad > > > > > > 192 (Configuration and Docker/Appc support). Currently I have a > > WIP > > > PR > > > > > for > > > > > > Docker Support which I'd like some feedback on (it's should be > > super > > > > easy > > > > > > to test), I'll probably complete Myriad 192 and part of that PR > as > > > > it's a > > > > > > natural fit. I estimate I can get all patches done by early may > > and > > > > > > hopefully get a release or release candidate out by May 11 > > > (ApacheCon). > > > > > > > > > > > > Due to the Alpha nature of Myriad and the significant value of > > Docker > > > > and > > > > > > Configuration support, I think most people would opt for 0.2.0 > over > > > > 0.1.1 > > > > > > and don't feel it's worth the effort to provide both releases at > > this > > > > > > time. I suggest simply doing a 0.2.0 release. Are there any > > > > objections? > > > > > > > > > > > > Darin > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Zach Jaffee > > > > > B.S. Computer Science > > > > > Case Western Reserve University Class of 2017 > > > > > Operations Director | WRUW FM 91.1 Cleveland > > > > > (917) 881-0646 > > > > > zjaffee.com > > > > > linkedin.com/in/zjaffee > > > > > github.com/ZJaffee > > > > > > > > > > > > > > >
