Bug 1391459 - [Doc-RFE] Drop support for legacy replication
Summary: [Doc-RFE] Drop support for legacy replication
Keywords:
Status: CLOSED DUPLICATE of bug 1208696
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: Doc-administration-guide
Version: 10.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: DS10.1
: ---
Assignee: Marc Muehlfeld
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-03 11:10 UTC by Marc Muehlfeld
Modified: 2016-11-09 11:32 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-09 11:32:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1208694 0 unspecified CLOSED [Console only] drop support for legacy replication 2021-02-22 00:41:40 UTC

Description Marc Muehlfeld 2016-11-03 11:10:26 UTC 
DS has a feature to be a consumer for a legacy supplier (4.x). This feature was no longer needed and has been removed from the code. Thus it could be dropped from the documentation as well.

See BZ#1208694.


https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/10.1/html/Administration_Guide/Managing_Replication-Replication_with_Earlier_Releases.html
Comment 1 Marc Muehlfeld 2016-11-09 11:30:23 UTC 
I removed the following sections about legacy replication from our guides (10.0, 10.1, and master branch):


Admin Guide:
11.1.8. Replication with 4.x Versions of Directory Server
11.19. Replication with Earlier Releases
+ one glossary entry


Configuration, Command, and File Reference:
3.4.2. Legacy Replication Attributes
4.1.31. Legacy Replication Plug-in
6.4. copiedFrom
6.5. copyingFrom
4.1.31. Legacy Replication Plug-in
+ one glossary entry


Plug-in guide:
One glossary entry
Comment 2 Marc Muehlfeld 2016-11-09 11:32:32 UTC 

*** This bug has been marked as a duplicate of bug 1208696 ***
Note You need to log in before you can comment on or make changes to this bug.