samba - Dec 2004 - Upgrade from 3.0.2 --> 3.0.7

I'm contemplating the upgrade for my production network from (Red Hat
Enterprises') version 3.0.2 to 3.0.7 (which is the latest from Red Hat).

So I start to peruse the changelog and I see this:

"Syntax errors in the OpenLDAP schema file (samba.schema)."

as one of 4 bullet items at the top of the Samba 3.0.7 changelog.  This has
me a bit concerned.  My production environment is based on an LDAP backend
of for Samba and I need to be sure that the upgrade will not toast my setup.

Here are my questions:
1). Can someone give me more detail on the "syntax errors" that were
corrected?
2). Also, what (if any) effect will I see if I use my existing
schema/directory with the 3.0.7?
3). What's the proper procedure to upgrade the directory so that it *can*
use the updated schema?

I've just started investigating the upgrade so forgive me if these questions
have been answered somewhere else.  Thanks in advance for any help.
--
Kevin L. Collins, MCSE
Systems Manager
Nesbitt Engineering, Inc.

> Here are my questions:
> 1). Can someone give me more detail on the "syntax errors" that
were
> corrected?
There were certain problems in the samba.schema file of the 3.0.6 release
that went unnoticed until after the release.  The SAMBA team quickly made
available a good samba.schema file and incorporated it into the next
release (3.0.7).
> 2). Also, what (if any) effect will I see if I use my existing
> schema/directory with the 3.0.7?
As far as I know, you should see no ill effect using your existing
directory.  You should, howver, use your new samba.schema in place of your
3.0.2 version.

> 3). What's the proper procedure to upgrade the directory so that it
*can*
> use the updated schema?
As far as I know, there should be no conversion necessary.  If you were,
however, as paranoid as I am you would first make sure you have a thourough
backup of your current setup in case your had to roll back.
Next, I would export the entire LDAP directory to an LDIF file for
safekeeping.
Then upgrade to 3.0.7 and everything should fly fine.  If SAMBA refuses to
function after the upgrade, first do a testparm, since some options have
changed since 3.0.2.
If SAMBA acts like the info in the directory is no good, clear out the
entire directory.  Verify the samba.schema is the one shipped with 3.0.7. 
Then import those LDIF files again.

I cannot imagine a scenario in which an upgrade would fail after all of
that, but of course.........

Good luck.