- 1. Library audit.
- 1.1 Did we lose or gain any public symbols in our libraries since the 4.1.0? Gbuild requires explicit export instead of exporting everything and then possibly controlling visibility with a .map file, so it's very possible.
- 1.2 Did ELF symbol versions on *nix platforms change? The older gbuild modules probably did, as I didn't understand the meaning of .map files back then.
- 1.3 Are the same libraries with the same names available in both 4.1.0 and 4.2.0?
- 2. Base:
- 2.1 Complete the Java SDBC driver framework, used by both the new SDBC-JDBC bridge and the Postgres SDBC driver.
- 2.2 Audit the new SDBC-JDBC bridge in Java against the old C++ one, fix any differences.
- 2.3 Complete the Postgres SDBC driver; still needs views, users, groups, etc.
- 2.4 Complete the integration of the Postgres SDBC driver into the Base UI forms (like MySQL already is).
- 3. Crashreporter
- 3.1 Get it working again.
- 3.2 Bug reported in UI form (instead of submitted to some now obsolete server), which can be copied/pasted or attached to Bugzilla.
- 4. Testing
- 4.1 Run all available tests (unit tests, smoketest, module integration tests, bvt, fvt, etc.) against 4.1.0 and 4.2.0, find and fix any regressions.
Task report