BTW, do we plan to make sure 1.12 runs on recently released [1] Debian 10?
> Or we can declare it's supported de-facto (if it's so) after releasing
> 1.12?
>
We can add support for Debian 10 if we want to. If it happens to work on
1.12 then we could document that. Otherwise, I suppose the changes
Looks good to me.
BTW, do we plan to make sure 1.12 runs on recently released [1] Debian 10?
Or we can declare it's supported de-facto (if it's so) after releasing 1.12?
[1] https://www.debian.org/News/2020/20200208
Thanks,
Alexey
On Mon, Apr 13, 2020 at 1:57 PM Todd Lipcon
wrote:
>
Sounds good. I've struggled with GCC 4 compatibility workarounds lately as
well, so would be nice to cut out that surface area.
-Todd
On Mon, Apr 13, 2020 at 11:39 AM Bankim Bhavsar
wrote:
> LGTM.
>
> Bankim
>
> On Sun, Apr 12, 2020 at 10:48 AM Grant Henke
> wrote:
>
> > Hello Kudu
LGTM.
Bankim
On Sun, Apr 12, 2020 at 10:48 AM Grant Henke wrote:
> Hello Kudu Developers,
>
> As we approach the 1.12.0 release I think now is a good opportunity to
> evaluate the platform versions
> we support. Doing so before the 1.12.0 release is useful because it will
> allow us to mark
Hello Kudu Developers,
As we approach the 1.12.0 release I think now is a good opportunity to
evaluate the platform versions
we support. Doing so before the 1.12.0 release is useful because it will
allow us to mark any OS we
intend to drop as deprecated. This is similar to how we have handled
