Re: Next development steps?

> > I think that we use current stable version as start point for
> > development branch. I don't think we could share code between this
> > two branches. It doesn't lead to better (readable) code.
>
> I think that should be assessed on a per-patch basis. If there is a bug
> that can be fixed in the stable branch with low risk of causing other
> problems, then it should be fixed. If it's specific to the new code, or
> high risk, then it should only be fixed in head.

You're right of course. But if everything goes as I expect then
the development version is much different from stable ...
I don't wait all of you agree so I tried small steps ;-)

> > Yes. I'm planning this mainly for me (maybe someone join me/us).
>
> Well, it seems that the Pervasive guys are back again, and we've had
> offers to help with bug hunting :-)

Nice to hear. It's better than I expect.
For Jaime Casanova: bug hunting is needed as Dave wrote. I think over
psqlODBC (regression) test suite in addition. I hope it isn't so hard
(but time consuming).

You complimented me and I have to cut down the time for psqlodbc
development during Xmas becouse I have to reinstall, upgrade and feature
grow the server and all clients workstations till people go back to work
at 3. January 2006. I hope I find one or two hours per two or three days.
I expect I'll be at work for 12 hours (or even more) per day ...

Regards,

Luf