On Tue, Oct 7, 2014 at 8:41 AM, jan i <j...@apache.org> wrote: > It seems (from the vote thread) you already have solved the problem, but > dont want to wait for a respin, can you please at least explain why the > project is under such a time constraint, that 72 hours is too long to wait > to make good quality. >
You have to make a cut somewhere. There are always a number of very small, low priority bugs and platform issues in any release. Drill is now on a monthly release cycle so triaging a minor bug as something that doesn't stop shipping has very little down-side. On the other hand, delaying by 3+ days is more than a 10% delay in the monthly release. Your characterization of this issue being a "quality" issue is also a bit of an over-statement. The problem was that several dependencies worked differently on Java8 than Java7. The fix involved changing the version of these dependencies. Changing dependency versions is not a small change and requires a full QA cycle since it takes serious thought to decide what impact the version change might have. The best way for that to happen in a reasonable way is to simply put this fix in the next release.