lib389 replica class

[William Brown]

Hi Mark / others

Given that one of our community members (ankity) is hitting up against
some issues, and the function they need is in the ReplicaLegacy object,
maybe it's time we bit the bullet and broke the old ReplicaObject in
favour of the new one? It would be worth us sinking some time down into
this improvement, as it's going to help ease people into lib389 in the
future.

[Mark Reynolds]

On 04/25/2017 01:05 AM, William Brown wrote:
> Hi Mark / others
>
> Given that one of our community members (ankity) is hitting up against
> some issues, and the function they need is in the ReplicaLegacy object,
> maybe it's time we bit the bullet and broke the old ReplicaObject in
> favour of the new one? It would be worth us sinking some time down into
> this improvement, as it's going to help ease people into lib389 in the
> future.

I would like to get rid of all the legacy classes.  What does this
impact, just the existing CI tests?
> 389-devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

[William Brown]

On Tue, 2017-04-25 at 07:17 -0400, Mark Reynolds wrote:
> On 04/25/2017 01:05 AM, William Brown wrote:
> > Hi Mark / others
> >
> > Given that one of our community members (ankity) is hitting up against
> > some issues, and the function they need is in the ReplicaLegacy object,
> > maybe it's time we bit the bullet and broke the old ReplicaObject in
> > favour of the new one? It would be worth us sinking some time down into
> > this improvement, as it's going to help ease people into lib389 in the
> > future.
>
> I would like to get rid of all the legacy classes.  What does this
> impact, just the existing CI tests?

Yes, it would probably affect many of these tests, but most of the
damage would be the topology module. Thankfully, it's only one place to
fix, then it's just cleanup.
> > 389-devel mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]