You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by Tae-Geon Um <ta...@gmail.com> on 2017/05/23 09:33:45 UTC
Blocking Issues of 0.16 Release in .NET side
Hi all,
Now, we’ve resolved all blocking issues of 0.16 release in Java side!
However, .NET side issues are still blocking 0.16 release [1].
Do you think it is okay to release 0.16 without resolving .NET side issues?
If not, how long do we have to wait for resolving .NET side issues?
Any thoughts?
Thanks,
Taegeon
[1]: https://issues.apache.org/jira/browse/REEF-1462 <https://issues.apache.org/jira/browse/REEF-1462>
Re: Blocking Issues of 0.16 Release in .NET side
Posted by Tae-Geon Um <ta...@gmail.com>.
Oh, sorry I’m confused.
That was TestFailMapperTasksOnInit.TestFailedMapperOnLocalRuntime :) (https://ci.appveyor.com/project/ApacheSoftwareFoundation/reef/build/1592-master <https://ci.appveyor.com/project/ApacheSoftwareFoundation/reef/build/1592-master>)
Thanks!
Taegeon
> On Jun 2, 2017, at 2:41 PM, Julia Wang (QIUHE) <Qi...@microsoft.com.INVALID> wrote:
>
> HI Taegeon,
>
> Yes, it is the same one in REEF-1804. Where did you find this test failure? In the AppVeyor tests from this PR, this test passed.
>
> Thanks,
> Julia
>
>
>
> -----Original Message-----
> From: Mariia Mykhailova [mailto:mamykhai@microsoft.com.INVALID]
> Sent: Thursday, June 1, 2017 9:24 PM
> To: dev@reef.apache.org
> Subject: Re: Blocking Issues of 0.16 Release in .NET side
>
> As REEF-1804 description says, it is exactly this failing test :-)
>
>
> -Mariia
>
> ________________________________
> From: Tae-Geon Um <ta...@gmail.com>
> Sent: Thursday, June 1, 2017 9:08:01 PM
> To: dev@reef.apache.org
> Subject: Re: Blocking Issues of 0.16 Release in .NET side
>
> Thanks Julia for the work!
>
> I've found another error in the AppVeyor build: TestFailMapperEvaluatorsWithFailedResultHandlerOnDispose.TestFailedMapperOnLocalRuntime.
>
> Is this not related to REEF-1804?
>
>
> Thanks,
> Taegeon
>
>> On Jun 2, 2017, at 12:32 PM, Julia Wang (QIUHE) <Qi...@microsoft.com.INVALID> wrote:
>>
>> I have sent PL for the fix in REEF-1804 and updated Jira with my observations. In the AppVeyor build, at least this test doesn't fail anywhere.
>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithu
>> b.com%2Fapache%2Freef%2Fpull%2F1311&data=02%7C01%7Cmamykhai%40microsof
>> t.com%7Cd4d43275ee914a3e807008d4a96cfb11%7C72f988bf86f141af91ab2d7cd01
>> 1db47%7C1%7C0%7C636319732929438925&sdata=ZZN2813SPRXxqviUjM93OYuLDvV%2
>> F8V4FMMp72B6JF38%3D&reserved=0
>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith
>> ub.com%2Fapache%2Freef%2Fpull%2F1311&data=02%7C01%7Cmamykhai%40microso
>> ft.com%7Cd4d43275ee914a3e807008d4a96cfb11%7C72f988bf86f141af91ab2d7cd0
>> 11db47%7C1%7C0%7C636319732929438925&sdata=ZZN2813SPRXxqviUjM93OYuLDvV%
>> 2F8V4FMMp72B6JF38%3D&reserved=0>
>>
>> Julia
>>
>> -----Original Message-----
>> From: Julia Wang (QIUHE)
>> Sent: Wednesday, May 31, 2017 10:32 AM
>> To: dev@reef.apache.org <ma...@reef.apache.org>
>> Subject: RE: Blocking Issues of 0.16 Release in .NET side
>>
>> I am busy on other work. Will find time to look at https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FREEF-1804&data=02%7C01%7Cmamykhai%40microsoft.com%7Cd4d43275ee914a3e807008d4a96cfb11%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636319732929448934&sdata=YW8DrJwiUN15jXGP2qWW4X2tayn1TPE2mmphh68PFok%3D&reserved=0 soon.
>>
>> -----Original Message-----
>> From: Byung-Gon Chun [mailto:bgchun@gmail.com]
>> Sent: Wednesday, May 31, 2017 12:35 AM
>> To: dev@reef.apache.org
>> Subject: Re: Blocking Issues of 0.16 Release in .NET side
>>
>> Do we have any updates on this issue?
>>
>> Thanks!
>> -Gon
>>
>> On Thu, May 25, 2017 at 5:49 AM, Mariia Mykhailova < mamykhai@microsoft.com.invalid> wrote:
>>
>>> These concerns resurface every time we discuss our .NET tests. We
>>> even have a JIRA somewhere to address them, but we've never had the
>>> resources/volunteers to change the way our .NET tests work. I don't
>>> think this is the cause of REEF-1804 itself, as majority of our .NET
>>> tests use this approach for a long time.
>>>
>>> -Mariia
>>>
>>> -----Original Message-----
>>> From: Markus Weimer [mailto:markus@weimo.de]
>>> Sent: Wednesday, May 24, 2017 11:45 AM
>>> To: REEF Developers Mailinglist <de...@reef.apache.org>
>>> Subject: Re: Blocking Issues of 0.16 Release in .NET side
>>>
>>> I had a quick look at [REEF-1804] and left some concerns about the
>>> way we evaluate the tests on the JIRA. -- Markus
>>>
>>
>>
>>
>> --
>> Byung-Gon Chun
>
RE: Blocking Issues of 0.16 Release in .NET side
Posted by "Julia Wang (QIUHE)" <Qi...@microsoft.com.INVALID>.
HI Taegeon,
Yes, it is the same one in REEF-1804. Where did you find this test failure? In the AppVeyor tests from this PR, this test passed.
Thanks,
Julia
-----Original Message-----
From: Mariia Mykhailova [mailto:mamykhai@microsoft.com.INVALID]
Sent: Thursday, June 1, 2017 9:24 PM
To: dev@reef.apache.org
Subject: Re: Blocking Issues of 0.16 Release in .NET side
As REEF-1804 description says, it is exactly this failing test :-)
-Mariia
________________________________
From: Tae-Geon Um <ta...@gmail.com>
Sent: Thursday, June 1, 2017 9:08:01 PM
To: dev@reef.apache.org
Subject: Re: Blocking Issues of 0.16 Release in .NET side
Thanks Julia for the work!
I've found another error in the AppVeyor build: TestFailMapperEvaluatorsWithFailedResultHandlerOnDispose.TestFailedMapperOnLocalRuntime.
Is this not related to REEF-1804?
Thanks,
Taegeon
> On Jun 2, 2017, at 12:32 PM, Julia Wang (QIUHE) <Qi...@microsoft.com.INVALID> wrote:
>
> I have sent PL for the fix in REEF-1804 and updated Jira with my observations. In the AppVeyor build, at least this test doesn't fail anywhere.
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithu
> b.com%2Fapache%2Freef%2Fpull%2F1311&data=02%7C01%7Cmamykhai%40microsof
> t.com%7Cd4d43275ee914a3e807008d4a96cfb11%7C72f988bf86f141af91ab2d7cd01
> 1db47%7C1%7C0%7C636319732929438925&sdata=ZZN2813SPRXxqviUjM93OYuLDvV%2
> F8V4FMMp72B6JF38%3D&reserved=0
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith
> ub.com%2Fapache%2Freef%2Fpull%2F1311&data=02%7C01%7Cmamykhai%40microso
> ft.com%7Cd4d43275ee914a3e807008d4a96cfb11%7C72f988bf86f141af91ab2d7cd0
> 11db47%7C1%7C0%7C636319732929438925&sdata=ZZN2813SPRXxqviUjM93OYuLDvV%
> 2F8V4FMMp72B6JF38%3D&reserved=0>
>
> Julia
>
> -----Original Message-----
> From: Julia Wang (QIUHE)
> Sent: Wednesday, May 31, 2017 10:32 AM
> To: dev@reef.apache.org <ma...@reef.apache.org>
> Subject: RE: Blocking Issues of 0.16 Release in .NET side
>
> I am busy on other work. Will find time to look at https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FREEF-1804&data=02%7C01%7Cmamykhai%40microsoft.com%7Cd4d43275ee914a3e807008d4a96cfb11%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636319732929448934&sdata=YW8DrJwiUN15jXGP2qWW4X2tayn1TPE2mmphh68PFok%3D&reserved=0 soon.
>
> -----Original Message-----
> From: Byung-Gon Chun [mailto:bgchun@gmail.com]
> Sent: Wednesday, May 31, 2017 12:35 AM
> To: dev@reef.apache.org
> Subject: Re: Blocking Issues of 0.16 Release in .NET side
>
> Do we have any updates on this issue?
>
> Thanks!
> -Gon
>
> On Thu, May 25, 2017 at 5:49 AM, Mariia Mykhailova < mamykhai@microsoft.com.invalid> wrote:
>
>> These concerns resurface every time we discuss our .NET tests. We
>> even have a JIRA somewhere to address them, but we've never had the
>> resources/volunteers to change the way our .NET tests work. I don't
>> think this is the cause of REEF-1804 itself, as majority of our .NET
>> tests use this approach for a long time.
>>
>> -Mariia
>>
>> -----Original Message-----
>> From: Markus Weimer [mailto:markus@weimo.de]
>> Sent: Wednesday, May 24, 2017 11:45 AM
>> To: REEF Developers Mailinglist <de...@reef.apache.org>
>> Subject: Re: Blocking Issues of 0.16 Release in .NET side
>>
>> I had a quick look at [REEF-1804] and left some concerns about the
>> way we evaluate the tests on the JIRA. -- Markus
>>
>
>
>
> --
> Byung-Gon Chun
Re: Blocking Issues of 0.16 Release in .NET side
Posted by Mariia Mykhailova <ma...@microsoft.com.INVALID>.
As REEF-1804 description says, it is exactly this failing test :-)
-Mariia
________________________________
From: Tae-Geon Um <ta...@gmail.com>
Sent: Thursday, June 1, 2017 9:08:01 PM
To: dev@reef.apache.org
Subject: Re: Blocking Issues of 0.16 Release in .NET side
Thanks Julia for the work!
I’ve found another error in the AppVeyor build: TestFailMapperEvaluatorsWithFailedResultHandlerOnDispose.TestFailedMapperOnLocalRuntime.
Is this not related to REEF-1804?
Thanks,
Taegeon
> On Jun 2, 2017, at 12:32 PM, Julia Wang (QIUHE) <Qi...@microsoft.com.INVALID> wrote:
>
> I have sent PL for the fix in REEF-1804 and updated Jira with my observations. In the AppVeyor build, at least this test doesn't fail anywhere.
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Freef%2Fpull%2F1311&data=02%7C01%7Cmamykhai%40microsoft.com%7Cd4d43275ee914a3e807008d4a96cfb11%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636319732929438925&sdata=ZZN2813SPRXxqviUjM93OYuLDvV%2F8V4FMMp72B6JF38%3D&reserved=0 <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Freef%2Fpull%2F1311&data=02%7C01%7Cmamykhai%40microsoft.com%7Cd4d43275ee914a3e807008d4a96cfb11%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636319732929438925&sdata=ZZN2813SPRXxqviUjM93OYuLDvV%2F8V4FMMp72B6JF38%3D&reserved=0>
>
> Julia
>
> -----Original Message-----
> From: Julia Wang (QIUHE)
> Sent: Wednesday, May 31, 2017 10:32 AM
> To: dev@reef.apache.org <ma...@reef.apache.org>
> Subject: RE: Blocking Issues of 0.16 Release in .NET side
>
> I am busy on other work. Will find time to look at https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FREEF-1804&data=02%7C01%7Cmamykhai%40microsoft.com%7Cd4d43275ee914a3e807008d4a96cfb11%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636319732929448934&sdata=YW8DrJwiUN15jXGP2qWW4X2tayn1TPE2mmphh68PFok%3D&reserved=0 soon.
>
> -----Original Message-----
> From: Byung-Gon Chun [mailto:bgchun@gmail.com]
> Sent: Wednesday, May 31, 2017 12:35 AM
> To: dev@reef.apache.org
> Subject: Re: Blocking Issues of 0.16 Release in .NET side
>
> Do we have any updates on this issue?
>
> Thanks!
> -Gon
>
> On Thu, May 25, 2017 at 5:49 AM, Mariia Mykhailova < mamykhai@microsoft.com.invalid> wrote:
>
>> These concerns resurface every time we discuss our .NET tests. We even
>> have a JIRA somewhere to address them, but we've never had the
>> resources/volunteers to change the way our .NET tests work. I don't
>> think this is the cause of REEF-1804 itself, as majority of our .NET
>> tests use this approach for a long time.
>>
>> -Mariia
>>
>> -----Original Message-----
>> From: Markus Weimer [mailto:markus@weimo.de]
>> Sent: Wednesday, May 24, 2017 11:45 AM
>> To: REEF Developers Mailinglist <de...@reef.apache.org>
>> Subject: Re: Blocking Issues of 0.16 Release in .NET side
>>
>> I had a quick look at [REEF-1804] and left some concerns about the way
>> we evaluate the tests on the JIRA. -- Markus
>>
>
>
>
> --
> Byung-Gon Chun
Re: Blocking Issues of 0.16 Release in .NET side
Posted by Tae-Geon Um <ta...@gmail.com>.
Thanks Julia for the work!
I’ve found another error in the AppVeyor build: TestFailMapperEvaluatorsWithFailedResultHandlerOnDispose.TestFailedMapperOnLocalRuntime.
Is this not related to REEF-1804?
Thanks,
Taegeon
> On Jun 2, 2017, at 12:32 PM, Julia Wang (QIUHE) <Qi...@microsoft.com.INVALID> wrote:
>
> I have sent PL for the fix in REEF-1804 and updated Jira with my observations. In the AppVeyor build, at least this test doesn't fail anywhere.
>
> https://github.com/apache/reef/pull/1311 <https://github.com/apache/reef/pull/1311>
>
> Julia
>
> -----Original Message-----
> From: Julia Wang (QIUHE)
> Sent: Wednesday, May 31, 2017 10:32 AM
> To: dev@reef.apache.org <ma...@reef.apache.org>
> Subject: RE: Blocking Issues of 0.16 Release in .NET side
>
> I am busy on other work. Will find time to look at https://issues.apache.org/jira/browse/REEF-1804 soon.
>
> -----Original Message-----
> From: Byung-Gon Chun [mailto:bgchun@gmail.com]
> Sent: Wednesday, May 31, 2017 12:35 AM
> To: dev@reef.apache.org
> Subject: Re: Blocking Issues of 0.16 Release in .NET side
>
> Do we have any updates on this issue?
>
> Thanks!
> -Gon
>
> On Thu, May 25, 2017 at 5:49 AM, Mariia Mykhailova < mamykhai@microsoft.com.invalid> wrote:
>
>> These concerns resurface every time we discuss our .NET tests. We even
>> have a JIRA somewhere to address them, but we've never had the
>> resources/volunteers to change the way our .NET tests work. I don't
>> think this is the cause of REEF-1804 itself, as majority of our .NET
>> tests use this approach for a long time.
>>
>> -Mariia
>>
>> -----Original Message-----
>> From: Markus Weimer [mailto:markus@weimo.de]
>> Sent: Wednesday, May 24, 2017 11:45 AM
>> To: REEF Developers Mailinglist <de...@reef.apache.org>
>> Subject: Re: Blocking Issues of 0.16 Release in .NET side
>>
>> I had a quick look at [REEF-1804] and left some concerns about the way
>> we evaluate the tests on the JIRA. -- Markus
>>
>
>
>
> --
> Byung-Gon Chun
RE: Blocking Issues of 0.16 Release in .NET side
Posted by "Julia Wang (QIUHE)" <Qi...@microsoft.com.INVALID>.
I have sent PL for the fix in REEF-1804 and updated Jira with my observations. In the AppVeyor build, at least this test doesn't fail anywhere.
https://github.com/apache/reef/pull/1311
Julia
-----Original Message-----
From: Julia Wang (QIUHE)
Sent: Wednesday, May 31, 2017 10:32 AM
To: dev@reef.apache.org
Subject: RE: Blocking Issues of 0.16 Release in .NET side
I am busy on other work. Will find time to look at https://issues.apache.org/jira/browse/REEF-1804 soon.
-----Original Message-----
From: Byung-Gon Chun [mailto:bgchun@gmail.com]
Sent: Wednesday, May 31, 2017 12:35 AM
To: dev@reef.apache.org
Subject: Re: Blocking Issues of 0.16 Release in .NET side
Do we have any updates on this issue?
Thanks!
-Gon
On Thu, May 25, 2017 at 5:49 AM, Mariia Mykhailova < mamykhai@microsoft.com.invalid> wrote:
> These concerns resurface every time we discuss our .NET tests. We even
> have a JIRA somewhere to address them, but we've never had the
> resources/volunteers to change the way our .NET tests work. I don't
> think this is the cause of REEF-1804 itself, as majority of our .NET
> tests use this approach for a long time.
>
> -Mariia
>
> -----Original Message-----
> From: Markus Weimer [mailto:markus@weimo.de]
> Sent: Wednesday, May 24, 2017 11:45 AM
> To: REEF Developers Mailinglist <de...@reef.apache.org>
> Subject: Re: Blocking Issues of 0.16 Release in .NET side
>
> I had a quick look at [REEF-1804] and left some concerns about the way
> we evaluate the tests on the JIRA. -- Markus
>
--
Byung-Gon Chun
RE: Blocking Issues of 0.16 Release in .NET side
Posted by "Julia Wang (QIUHE)" <Qi...@microsoft.com.INVALID>.
I am busy on other work. Will find time to look at https://issues.apache.org/jira/browse/REEF-1804 soon.
-----Original Message-----
From: Byung-Gon Chun [mailto:bgchun@gmail.com]
Sent: Wednesday, May 31, 2017 12:35 AM
To: dev@reef.apache.org
Subject: Re: Blocking Issues of 0.16 Release in .NET side
Do we have any updates on this issue?
Thanks!
-Gon
On Thu, May 25, 2017 at 5:49 AM, Mariia Mykhailova < mamykhai@microsoft.com.invalid> wrote:
> These concerns resurface every time we discuss our .NET tests. We even
> have a JIRA somewhere to address them, but we've never had the
> resources/volunteers to change the way our .NET tests work. I don't
> think this is the cause of REEF-1804 itself, as majority of our .NET
> tests use this approach for a long time.
>
> -Mariia
>
> -----Original Message-----
> From: Markus Weimer [mailto:markus@weimo.de]
> Sent: Wednesday, May 24, 2017 11:45 AM
> To: REEF Developers Mailinglist <de...@reef.apache.org>
> Subject: Re: Blocking Issues of 0.16 Release in .NET side
>
> I had a quick look at [REEF-1804] and left some concerns about the way
> we evaluate the tests on the JIRA. -- Markus
>
--
Byung-Gon Chun
Re: Blocking Issues of 0.16 Release in .NET side
Posted by Byung-Gon Chun <bg...@gmail.com>.
Do we have any updates on this issue?
Thanks!
-Gon
On Thu, May 25, 2017 at 5:49 AM, Mariia Mykhailova <
mamykhai@microsoft.com.invalid> wrote:
> These concerns resurface every time we discuss our .NET tests. We even
> have a JIRA somewhere to address them, but we've never had the
> resources/volunteers to change the way our .NET tests work. I don't think
> this is the cause of REEF-1804 itself, as majority of our .NET tests use
> this approach for a long time.
>
> -Mariia
>
> -----Original Message-----
> From: Markus Weimer [mailto:markus@weimo.de]
> Sent: Wednesday, May 24, 2017 11:45 AM
> To: REEF Developers Mailinglist <de...@reef.apache.org>
> Subject: Re: Blocking Issues of 0.16 Release in .NET side
>
> I had a quick look at [REEF-1804] and left some concerns about the way we
> evaluate the tests on the JIRA. -- Markus
>
--
Byung-Gon Chun
RE: Blocking Issues of 0.16 Release in .NET side
Posted by Mariia Mykhailova <ma...@microsoft.com.INVALID>.
These concerns resurface every time we discuss our .NET tests. We even have a JIRA somewhere to address them, but we've never had the resources/volunteers to change the way our .NET tests work. I don't think this is the cause of REEF-1804 itself, as majority of our .NET tests use this approach for a long time.
-Mariia
-----Original Message-----
From: Markus Weimer [mailto:markus@weimo.de]
Sent: Wednesday, May 24, 2017 11:45 AM
To: REEF Developers Mailinglist <de...@reef.apache.org>
Subject: Re: Blocking Issues of 0.16 Release in .NET side
I had a quick look at [REEF-1804] and left some concerns about the way we evaluate the tests on the JIRA. -- Markus
Re: Blocking Issues of 0.16 Release in .NET side
Posted by Markus Weimer <ma...@weimo.de>.
I had a quick look at [REEF-1804] and left some concerns about the way
we evaluate the tests on the JIRA. -- Markus
RE: Blocking Issues of 0.16 Release in .NET side
Posted by "Julia Wang (QIUHE)" <Qi...@microsoft.com.INVALID>.
I agree we should not release 0.16 without .Net.
I can look at REEF-1804.
For other test failures, they are transit. I can pass one more time to see if I can find more possible failed reasons. I remember last time, I improved a few places, I did see less frequent test failures on those after that change but before REEF-1804.
Julia
-----Original Message-----
From: Mariia Mykhailova [mailto:mamykhai@microsoft.com.INVALID]
Sent: Tuesday, May 23, 2017 9:58 AM
To: dev@reef.apache.org
Subject: RE: Blocking Issues of 0.16 Release in .NET side
No, it's still not okay to release 0.16 without resolving .NET issues.
The only thing that changed since we've last discussed this is that REEF-1804 has been introduced, due to which the last passing AppVeyor build happened three weeks ago, and all builds since then failed. I don't think this indicates any improvement on stability of .NET side. (I've marked REEF-1804 as a release blocker to make this explicit)
-Mariia
-----Original Message-----
From: Boris Shulman [mailto:shulmanb@gmail.com]
Sent: Tuesday, May 23, 2017 8:05 AM
To: dev@reef.apache.org
Subject: Re: Blocking Issues of 0.16 Release in .NET side
I don't think we can release without .NET side.
Sent from my iPhone
> On May 23, 2017, at 2:33 AM, Tae-Geon Um <ta...@gmail.com> wrote:
>
> Hi all,
>
> Now, we've resolved all blocking issues of 0.16 release in Java side!
> However, .NET side issues are still blocking 0.16 release [1].
>
> Do you think it is okay to release 0.16 without resolving .NET side issues?
> If not, how long do we have to wait for resolving .NET side issues?
>
> Any thoughts?
>
> Thanks,
> Taegeon
>
> [1]: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FREEF-1462&data=02%7C01%7Cmamykhai%40microsoft.com%7C550ab466236a4dd5190708d4a1ed26eb%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636311487314194211&sdata=Qr4JyGBxBeL2c7PfkwfAqpGIwTL9%2Fcss1%2FOOdjNYFKE%3D&reserved=0 <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FREEF-1462&data=02%7C01%7Cmamykhai%40microsoft.com%7C550ab466236a4dd5190708d4a1ed26eb%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636311487314194211&sdata=Qr4JyGBxBeL2c7PfkwfAqpGIwTL9%2Fcss1%2FOOdjNYFKE%3D&reserved=0>
>
>
RE: Blocking Issues of 0.16 Release in .NET side
Posted by Mariia Mykhailova <ma...@microsoft.com.INVALID>.
No, it's still not okay to release 0.16 without resolving .NET issues.
The only thing that changed since we've last discussed this is that REEF-1804 has been introduced, due to which the last passing AppVeyor build happened three weeks ago, and all builds since then failed. I don't think this indicates any improvement on stability of .NET side. (I've marked REEF-1804 as a release blocker to make this explicit)
-Mariia
-----Original Message-----
From: Boris Shulman [mailto:shulmanb@gmail.com]
Sent: Tuesday, May 23, 2017 8:05 AM
To: dev@reef.apache.org
Subject: Re: Blocking Issues of 0.16 Release in .NET side
I don't think we can release without .NET side.
Sent from my iPhone
> On May 23, 2017, at 2:33 AM, Tae-Geon Um <ta...@gmail.com> wrote:
>
> Hi all,
>
> Now, we've resolved all blocking issues of 0.16 release in Java side!
> However, .NET side issues are still blocking 0.16 release [1].
>
> Do you think it is okay to release 0.16 without resolving .NET side issues?
> If not, how long do we have to wait for resolving .NET side issues?
>
> Any thoughts?
>
> Thanks,
> Taegeon
>
> [1]: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FREEF-1462&data=02%7C01%7Cmamykhai%40microsoft.com%7C550ab466236a4dd5190708d4a1ed26eb%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636311487314194211&sdata=Qr4JyGBxBeL2c7PfkwfAqpGIwTL9%2Fcss1%2FOOdjNYFKE%3D&reserved=0 <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FREEF-1462&data=02%7C01%7Cmamykhai%40microsoft.com%7C550ab466236a4dd5190708d4a1ed26eb%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636311487314194211&sdata=Qr4JyGBxBeL2c7PfkwfAqpGIwTL9%2Fcss1%2FOOdjNYFKE%3D&reserved=0>
>
>
Re: Blocking Issues of 0.16 Release in .NET side
Posted by Boris Shulman <sh...@gmail.com>.
I don't think we can release without .NET side.
Sent from my iPhone
> On May 23, 2017, at 2:33 AM, Tae-Geon Um <ta...@gmail.com> wrote:
>
> Hi all,
>
> Now, we’ve resolved all blocking issues of 0.16 release in Java side!
> However, .NET side issues are still blocking 0.16 release [1].
>
> Do you think it is okay to release 0.16 without resolving .NET side issues?
> If not, how long do we have to wait for resolving .NET side issues?
>
> Any thoughts?
>
> Thanks,
> Taegeon
>
> [1]: https://issues.apache.org/jira/browse/REEF-1462 <https://issues.apache.org/jira/browse/REEF-1462>
>
>