reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Boris Shulman <>
Subject Re: [VOTE] Release Apache REEF 0.15.0 (rc2)
Date Tue, 24 May 2016 16:50:24 GMT
I completely agree for YARN, Mesos and HDI. But do we really need to run c#
local tests manually? MAy be we should just push a PR fro the release
branch just to have all the tests results?


On Tue, May 24, 2016 at 9:41 AM, Markus Weimer <> wrote:

> On 2016-05-24 09:27, Boris Shulman wrote:
>> I would prefer to go on with this release and augmenting it as Markus
>> suggested. I can be the release manager for the next one (0.15.1) as well.
>> Should we make 0.15.1 off the 0.15.0 branch and not master?
> Either is fine. But 0.15.1 cannot break APIs, while `master`, which will
> be 0.16.0, can.
> Another thought is why we rely on the manual testing when we have
>> completely automated tests on AppVeyor and Travis? I would prefer to rely
>> more on teh automated testing vs. manual testing on unstable environments.
> Me too. Ideally, there should be no software testing required as part of a
> release vote.
> However, our integration tests do not have a stellar track record when it
> comes to repeat-ability. Part of it is self-inflicted (like the validation
> via log file we do in .NET) and part of it is just the nature of
> distributed systems which are very sensitive to the performance of the
> underlying machines. And test machines have very different performance.
> I view the latter actually as a good thing. Test failures only found on
> our scrappy build servers have more often than not unearthed very
> interesting synchronization bugs. We just haven't ironed out all of them
> yet :)
> Lastly, we don't have automated tests on YARN, Mesos and HDI yet. We need
> to make sure to not break in those environments as part of the release
> cycle, which is manual for now.
> Markus

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message