reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tae-Geon Um <taegeo...@gmail.com>
Subject Re: Disable tests with transient failures
Date Fri, 21 Jul 2017 02:18:43 GMT
That’s great. I also +1 for doing the release with known transient failures :) 

I will share the release plan in a separate thread.

Thanks!
Taegeon 

> On Jul 21, 2017, at 9:31 AM, Byung-Gon Chun <bgchun@gmail.com> wrote:
> 
> Taegeon, it looks like we have a consensus. :)
> 
> Could you proceed to the next step of the release process?
> It would be nice to set a deadline to fix the transient failure case(s).
> After that, we should make a release with known transient issues.
> It would be super helpful if you share your plan as a release manager.
> 
> I asked about upgrading to hadoop 2.7.0 for a new release. It looks like no
> one objects. If you have a concern, please share your concern. This's the
> last call.
> 
> Thanks!
> -Gon
> 
> On Wed, Jul 19, 2017 at 11:21 PM, Markus Weimer <markus@weimo.de> wrote:
> 
>> On Tue, Jul 18, 2017 at 10:56 PM, Mariia Mykhailova
>> <mamykhai@microsoft.com.invalid> wrote:
>>> Would you really prefer to do a release without tests than a release
>> with some known transient issues tracked by CI and JIRA issues?
>> 
>> We have decided not to release with transient issues many times over
>> on this list. Compared to not releasing, I prefer releasing with fewer
>> tests and a clear and open message about that.
>> 
>> 
>>> +1 for doing the release with known transient issues - so that your
>> desire to do a release doesn’t push you to bad engineering decisions,
>> 
>> Wohoo! Let's work towards that, then!
>> 
>> 
>> Markus
>> 
> 
> 
> 
> -- 
> Byung-Gon Chun


Mime
View raw message