Roman,
"- no caching in auto-commit mode" is probably the most important
(this is related to memory correct?) ... I would rather you forge
ahead and get to the next major release instead of spend cycles back-
fitting for a patch - especially if the new release targeted for
around May...? What I need is a guess (WAG) on a release so I can
plan for integration to a client's software release - once their
software is deployed it won't be updatable for over 6 months
(environmentally isolated environment) so I want to get the best
possible driver beforehand.

So - can we expect May (or late May) for 2.0?

thanks,
Ron


--- In Firebird-Java@yahoogroups.com, "Roman Rokytskyy"
<rrokytskyy@a...> wrote:

> Ron,
>
> > What is the schedule for the next release of the JayBird driver?
>
> Next release will be 2.0 and will include many new features:
>
> - full support for Services API (backup/restore, user management,

etc);

> - support for updatable result sets
> - execution plan in statements
> - no caching in auto-commit mode
> - reworked JCA code
>
> First three issues are solved, last is almost solved (reconnecting

an

> in-limbo transaction for recovery is the only problem there), I am

currently

> doing big refactoring of the transaction management to fix caching

in

> auto-commit mode. Current state of the driver is not acceptable

even for

> alpha release, it's in the middle of refactoring. I think I need

one month

> to finish this task, and if there will be no pending changes from

Gabriel

> Reid and Steven Jardine, then we can start with the release cycle.
>
> > The latest version is still 1.5.5, correct?
>
> Correct.
>
> > Since December there have been multiple enchancments and bugs

fixed (?) -

> > I am particularly interested in bugs related to memory leaks,

etc.

>
> I do not plan to release 1.5.6 version, but if there is demand for

it - I

> will check how hard would it be to backport fixes from HEAD to

Branch_1_5.

> If that is not too complex, I will do this.
>
> Can you please provide a list of bugfixes to port (the best would

a list of

> ChangeLog entries, file is available from CVS)?
>
> Roman