Yes, we would include those in the new release candidate. On Jun 11, 2015 5:22 PM, "Aljoscha Krettek" <aljos...@apache.org> wrote:
> Aren't there still some commits at the top of the release document that > need to be cherry-picked to the release branch? > > On Thu, 11 Jun 2015 at 17:13 Maximilian Michels <m...@apache.org> wrote: > > > The deadlock in the scheduler is now fixed. Based on the changes that > have > > been push to the release-0.9 branch, I'd like to create a new release > > candidate later on. I think we have gotten the most critical issues out > of > > the way. Would that be ok for you? > > > > On Wed, Jun 10, 2015 at 5:56 PM, Fabian Hueske <fhue...@gmail.com> > wrote: > > > > > Yes, that needs to be fixed IMO > > > > > > 2015-06-10 17:51 GMT+02:00 Till Rohrmann <trohrm...@apache.org>: > > > > > > > Yes since it is clearly a deadlock in the scheduler, the current > > version > > > > shouldn't be released. > > > > > > > > On Wed, Jun 10, 2015 at 5:48 PM Ufuk Celebi <u...@apache.org> wrote: > > > > > > > > > > > > > > On 10 Jun 2015, at 16:18, Maximilian Michels <m...@apache.org> > wrote: > > > > > > > > > > > I'm debugging the TaskManagerFailsWithSlotSharingITCase. I've > > located > > > > its > > > > > > cause but still need to find out how to fix it. > > > > > > > > > > Very good find, Max! > > > > > > > > > > Max, Till, and I have looked into this and it is a reproducible > > > deadlock > > > > > in the scheduler during concurrent slot release (in failure cases). > > Max > > > > > will attach the relevant stack trace to the issue. > > > > > > > > > > I think this is a release blocker. Any opinions? > > > > > > > > > > – Ufuk > > > > > > > > > >
