We are heavily utilising back-sql on our product. Granted it has its issues
but it does so far fulfill our needs. We are currently running on 2.4.58
which we build ourselves for Debian and RHEL/CentOS based systems. We
needed couple of patches to back-sql to make it work for us. I just created
issues (and added my patches) for them. I don't have a slightest idea if
the patches are of any use for you but they make our environments work.
Removing back-sql from future releases would make us stuck with 2.4 release.
https://bugs.openldap.org/show_bug.cgi?id=9629https://bugs.openldap.org/show_bug.cgi?id=9630
--- Aapo Romu
--- Software Architect
--- Eficode Oy
On Mon, 9 Aug 2021 at 00:02, Quanah Gibson-Mount <quanah(a)symas.com> wrote:
>
>
> --On Sunday, August 8, 2021 6:32 PM +0100 Howard Chu <hyc(a)symas.com>
> wrote:
>
> > Quanah Gibson-Mount wrote:
> >> For 2.5, we deprecated:
> >>
> >> back-ndb
> >> back-sql
> >> back-perl
> >>
> >> Should these be removed for 2.6?
> >
> > I still routinely build back-perl in master. Is there any reason to
> > remove it?
>
> Not necessarily, that's why I started the discussion. back-bdb was
> deprecated with 2.3, but was around for all of 2.4 as well. I see no
> reason to keep back-ndb around. back-sql has numerous open issues, but
> I've no real insight into whether it retains any usefulness.
>
> --Quanah
>
>
> --
>
> Quanah Gibson-Mount
> Product Architect
> Symas Corporation
> Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
> <http://www.symas.com>
>
After evaluating our experience with OpenLDAP 2.4 and demands* from e.g. Symas enterprise customers,
we're adopting a new release policy which will be posted on -announce shortly. The main objective
is to resolve the tension between wanting to release new features as soon as they're available, vs
keeping stability over the long term.
*i.e., enterprises want to avoid any version updates unless they're for a specific feature
they commissioned. We considered resurrecting use of the STABLE tag but that really didn't
satisfy, and its use was retired for good reasons.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
