I expect 3.4 to be pretty unstable. What we'll probably want to do is
to start investigating just how we can tap into things like the new database API, named queries, etc to ease our porting problems in the future. We'll have systemic things to worry about as aD is making more and more use of SQLJ, which means we need Dan's nsjava AOLserver module working portably and robustly enough so any 'ole fool (like me)
can install it and have it work reliably.
Etc etc.
So I'd expect us to start working on porting issues as 3.4 rolls out, but not to attempt a full port but rather concentrate on 4.0. For instance, we need to decide what to do about bind variables. The latest style guide for aD has them buried in the API in a way that we can kludge for PG to our hearts content, but not all DB calls in the ACS will be able to make use of that style. That style's just evolved in the last week or so - this moving-target aspect will undoubtably live on after 3.4 is released, before things get glued down for 4.0.
