[Date Prev][Date Next]
file name and stable tag to 2.3.13 (was: Openldap 2.3.11 cannot autorecover from abnormal shutdown.)
- To: openldap-devel@OpenLDAP.org
- Subject: file name and stable tag to 2.3.13 (was: Openldap 2.3.11 cannot autorecover from abnormal shutdown.)
- From: Michael Ströder <firstname.lastname@example.org>
- Date: Tue, 20 Dec 2005 09:23:05 +0100
- In-reply-to: <C8BDA0F5E17CA978BCDAD68E@cadabra-sw.stanford.edu>
- References: <email@example.com> <C8BDA0F5E17CA978BCDAD68E@cadabra-sw.stanford.edu>
- User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920
Quanah Gibson-Mount wrote:
> --On Tuesday, December 20, 2005 11:20 AM +0800 Yingbo Qiu
> <firstname.lastname@example.org> wrote:
>> If the slapd was killed by SIGKILL(9), bdb database will be
>> autorecovered at startup, I can read recovery message from 'slapd -d
> You may with to upgrade to 2.3.13, where there were fixes to
> autorecovery since 2.3.11.
IMHO http://www.openldap.org/software/download/ is confusing.
I think the stable tag should be moved away from 2.3.11 to 2.3.13 since
2.3.13 seems to be much more stable and people should be discouraged to
I'd also vote for just keeping the release number in the tar.gz file
name of source distribution marked stable. Placing a release date into
the file name (like openldap-stable-20051018.tgz) is not a good
reference to the content of file CHANGES.