Hi, I wanted to gently follow up on this thread in case anyone has any thoughts or would like to take a look.
Thanks, Murali On Mon, Sep 16, 2024 at 10:23 AM Muralidhar Basani < muralidhar.bas...@aiven.io> wrote: > Thanks Chia. > > I have updated KIP with this quote, in the migration plan section. > > Thanks, > Murali > > On Sun, Sep 15, 2024 at 3:30 PM Chia-Ping Tsai <chia7...@gmail.com> wrote: > >> >> > Muralidhar Basani <muralidhar.bas...@aiven.io.invalid> 於 2024年9月15日 >> 晚上9:02 寫道： >> > >> > With this, I think, users don't have to make any explicit changes in >> their >> > code, if their provider is reload4j. And if it's a different provider >> (like >> > logback, log4j), they would have to upgrade that to match it with slf4j. >> >> If upgrading the matched provider is the only explicit change and we >> expect users have responsibility to keep consistent version when using >> other providers , could we write it down to the KIP? >> >> That means we will update slf4j without KIP in the future except for >> specific reason. >> >> Best, >> Chia-Ping > >
