Looks like the benchmarks have passed for around 30 builds in a row. +1 to including them if they don't fail for spurious reasons between now and cutting the release.
BTW - Do we have stats on the variance we see in the benchmark numbers? Are we getting close to failing occasionally? What is the criteria that will cause them to fail? Is this on the wiki somewhere? -Dan On Tue, Jan 14, 2020 at 3:58 PM Owen Nichols <onich...@pivotal.io> wrote: > @Anthony has twice proposed[1][2] that we start including geode-benchmarks > in our release process. Is this worth considering for the upcoming 1.12.0 > release? > > [1] > https://lists.apache.org/thread.html/c7bd84b6e6f5464ed674ed447fe8922097237932967b4ed1966e79d3%40%3Cdev.geode.apache.org%3E > [2] > https://lists.apache.org/thread.html/c9c73e726742c78a1ff9739379a51f7eeab33a05d99531a38b537670%40%3Cdev.geode.apache.org%3E > > > On Jan 14, 2020, at 3:44 PM, Mark Hanson <mhan...@pivotal.io> wrote: > > > > It is that time again. It is time to cut a new release branch for 1.12 > on February 3rd. > > > >
