Re: OpenLDAP 2.5 plans and community engagement

Yes, I’m sure all the people who I have seen come to this list running an older, distro-supplied RPM/Deb have read that, ignored it, and posted anyways thinking “surely they can’t be serious”. As an admin I know that all / most of the software in a distro is out-of-date, but there are not enough hours in the day to compile-from-source all the software that is used: that’s why distros were invented in the first place, to save everyone time. Perhaps all of these people started providing these binaries because the project itself didn’t / doesn’t? Maybe all of those other efforts could be refocused to build binaries served from (say) repos.openldap.org. The infrastructure seems to already be present: perhaps it just needs to be centralized / concentrated? That is an argument for timed releases. The OpenBSD project is a good example: they release twice a year. If a feature cannot be made stable in time for one release, they either back it out or do not commit in the first place, and simply try to make it work for the following one. There is actually less pressure to force a feature (that may or may not be ready) in a particular release, because the next one will be along shortly. When releases are ad hoc, there is actually more pressure because people start thinking “if we don’t get it in this release, who knows when the next opportunity will be”.