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
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 wrote:
>
> > +1
+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 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,
+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
wrote:
> Hey Zachary! Thanks, for the upvote.
>
> Also if you're looking for projects ping me! I'm going to be adding mor
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 wrote:
> If I recall the original reason for the 0.1.1 release was that it would be
> able to get it out ea
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:
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
Docke