Good question. I wish I could guarantee that the 5 issues mentioned in
my original email under "INCOMPATIBILITIES" are the last incompatible
changes, but of course it's never done until it's done, and it's
*possible* that we'll find some more things that we'd like to change
before drawing the line in the sand. However you can tell from the
list of incompatibilities that they are definitely edge cases. The
changes in transaction semantics are the most serious IMO, but it's
always possible that someone has accidentally put strings over 500
characters in a StringProperty (or over 500 bytes in an indexed
BlobProperty). Still, no methods, functions or classes were renamed,
and no signatures changed. I hope to continue this trend.
In any case, I can't remind people enough that (at least) these
incompatibilities will hit production when the 1.6.4 SDK goes out
(actually production will see them a few days earlier) so please
review your code, and if possible test with NDB 0.9.9. I also hope
that 1.6.4 will see NDB's "experimental" label removed -- but no
guarantees!