--On Wednesday, June 26, 2024 5:29 PM -0700 Christopher Paul chris.paul@rexconsulting.net wrote:
On 6/26/24 15:52, Quanah Gibson-Mount wrote:
I think you mean, why do I suggest 2.6 over 2.5? It's been out several years, the core functions are solid. 2.5 had many fixes to replication, 2.6 has further fixes. I've run 2.6 in production for over 2 years, making use of some of the newer features (file based logging for example).
Is there any chance that something new will be added to a future version of 2.6 that might cause problems? It would seem that since 2.5 is the official LTS Release according to https://www.openldap.org/software/download/, that the project would not add any new features to 2.5, thus reducing the risk than a new version would cause problems or unexpected changes in behavior. Whereas, since 2.6 is the official "Feature Release", that a new feature might be added to 2.6 that could produce an undesirable outcome in someone's production environment?
New features have to be enabled, so if you don't enable it, how would it affect things? For example, the recent work on the memberOf overlay to work with replication still requires a flag to do the behavior change.
We also of course have a test suite to ensure core functionality is not affected by changes (new features or not).
--Quanah