Re: 1.1-devel differences?

["Kurt D. Zeilenga" <Kurt@openldap.org>]

1.1-devel?

For clarification:
    The HEAD branch is not OpenLDAP 1.1Alpha.  The
    HEAD branch is -devel and is currently being used
    for 2.X development.  Issues concerning -devel
    should be raised on -devel mailing list.

    OpenLDAP 1.1Alpha is in OPENLDAP_REL_ENG_1_1 branch
    and tagged OPENLDAP_REL_ENG_1_1_ALPHA.  1.1Alpha
    should be API compatible with 1.0.  1.1Alpha issues
    should be raised to -bugs mailing list.

I've updated the -devel README to contain the following
note:
    OpenLDAP -devel is for the development of OpenLDAP.  As such,
    it changes often.  These changes include changes in functionality
    and unproved bug fixes.  Many of these changes will cause
    previous working programs to fail.

    Client developers seeking a stable development platform
    should use -stable.

I've also added clarification to download.html.

In -devel, we are currently updating the API to
draft-ietf-ldapext-ldap-c-api-01 as part of our LDAPv3
efforts.  This being done incrementally.  As such,
-devel is neither Umich nor Netscape3 nor ietf-draft.

I posted a message (on -devel) stating how to detect Umich,
Netscape3, ietf draft APIs at compile time.  I will post a
note (on -devel) stating how to specifically detect -devel's
ever changing API.

At 12:28 PM 11/4/98 -0500, Rasmus Lerdorf wrote:
>Probably something that should be noted in a portability readme somewhere.

We will be writing a developer's guide...

>With the previous slapd I could send a query that looked like this:
>
>   $result = ldap_search($ds,"o=Lerdorf, c=CA","(sn=Ler*)");
>
>and it worked fine.  Now, however I have to do:
>
>   $result = ldap_search($ds,"ou=CORE, o=Lerdorf, c=CA","(sn=Ler*)");
>
>What changed that would force me to add the ou here?  

This is likely a scope issue (subtree vs ??).  I'll see
if I can duplicate the problem.

As these issues appear to all -devel related, I suggest we
take followups to -devel mailing list.

Kurt