Hi folks,
i have noticed openldap keeps releasing new versions from time to time. I have not noticed changes in protocol specification. So why does openldap release new versions ? Isn't it mature enough yet ? I am asking cause i am used to djb tools like qmail and djbdns and they don't change since a long time ago.
Please, don't get me wrong. I am no saying one approach is better than another, i am just curious about openldap.
Thanks.
On Aug 05, 2012, at 08.07, Friedrich Locke wrote:
Hi folks,
i have noticed openldap keeps releasing new versions from time to time. I have not noticed changes in protocol specification. So why does openldap release new versions ? Isn't it mature enough yet ? I am asking cause i am used to djb tools like qmail and djbdns and they don't change since a long time ago.
Please, don't get me wrong. I am no saying one approach is better than another, i am just curious about openldap.
um - most software projects release new versions from time to time. i'm not sure what consistency in protocol specifications or "maturity" would have to do with it [e.g. that's unrelated], and the last thing i'd do is use software like qmail or djbdns as the reference for this notion.
for a more specific answer to your question, read the changelogs that ship with each release, and you can find out why new releases occur.
using software that is not under reasonably active development is, generally speaking, more likely to be detrimental than beneficial. there are always corner cases and exceptions, as with all things, but absence of releases because the author[s] believes the software is "perfect" is not one of them.
-b
I am not a openldap developer but i am a lazy FL / oss developer. So i think your question is general. There are so many project that don't change the basic function but are releasing new version. Why ? Well, a possibility is introducing a new build sistem, changing the library api for a better factoring, fixing some bug and , why not, better integration, portability issue . And sometime new feature, dropping past mistake in a incompatible way and so on. for me this is a sufficient reason for doing release.
But it just my not so naive i think opinion .
Best regards and sorry for the top posting.
2012/8/5, Friedrich Locke friedrich.locke@gmail.com:
Hi folks,
i have noticed openldap keeps releasing new versions from time to time. I have not noticed changes in protocol specification. So why does openldap release new versions ? Isn't it mature enough yet ? I am asking cause i am used to djb tools like qmail and djbdns and they don't change since a long time ago.
Please, don't get me wrong. I am no saying one approach is better than another, i am just curious about openldap.
Thanks.
As others already said, ongoing development in an Open Source project is a good thing.
OpenLDAP has been LDAP core standard compliant from the beginning of the project, since it was the Open Source reference implementation.
But there are additions to the standard (see e.g. the RFC list at the bottom of http://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol)
And although OpenLDAP is a really good and well engineered product, there is always possibilities of improvements, e.g. Howard's new mdb data backend that makes the fastest LDAP implementation have even higher performance.
Cheers,
Peter
Am 05.08.2012 14:07, schrieb Friedrich Locke:
Hi folks,
i have noticed openldap keeps releasing new versions from time to time. I have not noticed changes in protocol specification. So why does openldap release new versions ? Isn't it mature enough yet ? I am asking cause i am used to djb tools like qmail and djbdns and they don't change since a long time ago.
Please, don't get me wrong. I am no saying one approach is better than another, i am just curious about openldap.
Thanks.
openldap-technical@openldap.org