Hi Kudu dev community,

Since Kudu 1.7.0 was released a few important fixes have been found
and backported to Kudu 1.7.x. Therefore, I would like to propose a 1.7.1
release.

The fixes currently include:

   - [consensus] KUDU-2367 fix replica health report (310dbe0
   <https://github.com/apache/kudu/commit/310dbe0>)
   - KUDU-2377: cap GetResourceLimit return value at kint32max (66b8272
   <https://github.com/apache/kudu/commit/66b8272>)
   - KUDU-2379. java: exportAuthenticationCredentials must connect to the
   cluster (608b5a <https://github.com/apache/kudu/commit/608b5a>)
   - KUDU-2364 Add extra check in ksck for tserver ID (45b3f21
   <https://github.com/apache/kudu/commit/45b3f21>)
   - KUDU-2412: Fix python client compilation in el6 environments (4a3a2b
   <https://github.com/apache/kudu/commit/4a3a2b>)
   - KUDU-2378. Fix unaligned loads of int128 from rows (0ceaafe
   <https://github.com/apache/kudu/commit/0ceaafe>)
   - KUDU-2416: Fix PartialRow.setMin and add a unit test (1e49ac8
   <https://github.com/apache/kudu/commit/1e49ac8>)

Are there any other patches that we should be cherry-picking into 1.7.1?
Reminder that point-releases like this should be critical fixes (data loss,
incorrect results, crashes, etc) only.

I'll volunteer to RM this one. I plan to start a vote on RC1 on
Tuesday, May 1st.

Please let me know your thoughts on the above plan.

Thanks,
Grant

-- 
Grant Henke
Software Engineer | Cloudera
[email protected] | twitter.com/gchenke | linkedin.com/in/granthenke

Reply via email to