Planned release schedule

The message details the release plan for the next few months of TOra. All dates are approximations and no commitment to the number of beta, alpha or release candidates are final. I will release it when it is ready. I will however try to stick to making one development release every 2 weeks (Also with exceptions for holidays and vacations), the number of releases may vary though. The releases are usually made on monday because then I can do the packaging during the weekend.

TOra 1.3.1 Alpha - 2001-12-26

Delayed from ideal release by 2 days because of Christmas.

TOra 1.3.2 Alpha - 2002-01-15

Delayed from ideal release by 8 days because skiing vacation.

TOra 1.2.2 - 2002-01-21

Maintenance release of stable TOra, if needed.

TOra 1.3.3 Alpha - 2002-01-28

Final alpha release.

TOra 1.3.4 Beta - 2002-02-11

First beta release. Feature complete, documentation missing.

TOra 1.2.3 - 2002-02-18

Maintenance release of stable TOra, if needed.

TOra 1.3.5 Beta - 2002-02-25

Second beta, release candidate 1. Documentation ready.

TOra 1.3.6 Beta - 2002-03-11

Release candidate 2.

TOra 1.4.0 - 2002-03-18

Final 1.4.0 release.

TOra 1.5.0 - 2002-03-25

First alpha release on the road to 1.6 TOra.

TOra 1.4.1 - 2002-04-22

Maintenance release of stable TOra, if needed.

Planned major future features

The following major features are planned to be included in the 1.4 release. I'm not making any commitment as usual.

Modify object in the DB browser - The most popular new feature in the poll. The reason it's taking so long (It was at the top of the 1.2 feature poll as well) is that it is a really big task to implement.

PostgreSQL support - Actually I will implement a QSQL connection provider which will give support to a whole bunch of databases. This will also replace the MySQL support currently provided natively from TOra. The support will be pretty barebone though. Basically the worksheet and browser will be the only supported tools. This is important to possible future inclusion in the KDE project which will give this application a whole new level of use hopefully.

PL/SQL doc - Only because it is a relatively easy task to implement. Also I think it would be a really usefull tool to use to document database application.

Visual reverse engineering & design - This is a big feature and as such last on my list for 1.4 stuff, but it would be a real killer application which can also share a lot of code with the DB browser modify object. This will definately be added, I just don't know if it will be in 1.4 or 1.6.

By no means are these the only features that I will add. But these are the large and important ones that pretty much define when I can move from alpha to the beta (feature complete) releases.

GlobeCom AB