OK, awesome :)
I just wanted to make sure there are no objections before opening the
JIRA, since discussions are easier on the mailing list.
On Mon, Dec 23, 2019 at 5:01 PM Ryanne Dolan wrote:
>
> Gwen, no one is hiding anything. Please follow up your JIRAs with PRs and
> I'm sure we can get the
Gwen, no one is hiding anything. Please follow up your JIRAs with PRs and
I'm sure we can get the site updated.
Ryanne
On Mon, Dec 23, 2019, 8:38 AM Gwen Shapira wrote:
> There's nothing preventing us from updating the site-docs now to make them
> match the 2.4 release better (I just opened few
There's nothing preventing us from updating the site-docs now to make them
match the 2.4 release better (I just opened few JIRA for additional docs).
Is there a reason why we want to hide MirrorMaker 2.0 until next release?
For example, is it unstable? Do you expect interfaces or tools to
signific
Hey Gwen, per the KIP, the depreciation plan will take a few releases.
Copied here:
Phase 1 (targeting next Apache Kafka release): All MirrorMaker 2.0 Java
code is added to ./connect/mirror/.
Phase 2 (subsequent release): Legacy MirrorMaker Scala code is deprecated,
but kept in place. Sample MM2
