Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1208694

git patch file (389-ds-console master)
0001-Ticket-48139-drop-support-for-legacy-replication.patch

389-ds-console>
Description: Deleted the code for the DS to act as a legacy consumer
of a 4.x supplier server (4xcompatible) as well as its online doc.

Sorry, it turned out "Legacy Consumer Settings" was still there. I'm reworking on it.

git patch file (389-ds-console master) -- revised so that the Legacy Consumer Settings tab is removed, as well.
0001-Ticket-48139-drop-support-for-legacy-replication.2.patch

You are removing a comment that should probably be left alone in ReplicaSettingPanel.java:

{{{
/ If the user tries to define a master or a hub, we need to log the changes.
That's why we see if the change log entry exists or not.
If the change log entry does not exist we display an error message telling
the user that he/she has to define the Change Log first. In this dialog we
describe the steps to follow /
}}}

git patch file (389-ds-console master) -- resurrected the comment (Thanks, Nathan!)
0001-Ticket-48139-drop-support-for-legacy-replication.3.patch

I cloned this ticket for the server: Ticket #48150 - [Server] drop support for legacy replication

Let me use this ticket for Console only.

And I consider the fixed patch got an "ack". :)

Pushed to master:
e9d5e61..8b276a5 master -> master
commit 8b276a5533ff4945e23f2091c9de29c605491b25

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/1470

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.