I don't think that the message that OACS supported both databases was missed at all.But the fact that ETP is not easy to maintain for Oracle and PG. That's why the announcement for ETP2 was made, to get interest going on building an ETP easier to maintain. So deeming it not ready for prime time release is probably prudent as it's not as mature as it should be.
I also think some pieces of code that were added or patched to the original ETP code that worked after your port probably sneaked it's way in. Since this mistake seemed to be pretty non-trivial to find, so it probably just got overlooked. Since the OpenMSG folks have set up the testing enviros, hopefully these kinds of things will happen less.
talli
