FreeTDS Development Group

[ZIGLIO Frediano <Frediano.Ziglio AT vodafoneomnitel.it>]

> 
> If we have things that worked in 0.53 and no longer work, 
> then I would 
> consider doing a 0.60pl1 specifically to address those 
> issues.  However, 
> if it's things like threadsafety not working on platform X, 
> or whatever, 
> we should just roll forward to 0.61pre1 in a couple of weeks.
> 

All problem raised seem new to me...
Quite different from 0.60pl1 and 0.61pre1...
0.60pl1 is a patched version of 0.60 (include only fixes), while 0.61pre1 is
a prerelease of 0.61 (include new feature and perhaps new bugs.. not so good
for professional uses..)
Perhaps some fixes can be made only by movings tags or creating a new one.

I know that branching need more work but for doing patches version is quite
useful.

> The TDS 4.2 versus Sybase 12.5 issue appears in 0.53 
> apparently, but 12.5 
> wasn't available at the time, so no one noticed it.
> 

Well, just update readme to use 5.0.. not our problem if server hang with
good query...
Or write a workaround... if possible

> So, let's sort out which issues are truely regressions if any 
> and address 
> those in a pl1 release, everything else, include horribly broken new 
> features go into 0.61pre1.
> 
> I'm debating whether a bug that affects lesser used and out of 
> date platforms (DU 4.0f, ahem we got rid of ours about three 
> years ago) is 
> worth the developer time of branching and going through the release 
> process or just expecting those folks to move onto the CVS or 
> snapshot 
> version.  This is not to dis DU, we're obviously going make 
> sure it works 
> moving forward, but is it worth the time?
> 

Was so old ??
I didn't know. However this problem is present even in 5.x version
(parameter order is different from other unices, so.. core if threadsafe
enabled).

> Brian
> 
freddy77

=================================
"STRICTLY PERSONAL AND CONFIDENTIAL

This message may contain confidential and proprietary material for the sole
use of the intended recipient. Any review or distribution by others is
strictly prohibited. If you are not the intended recipient please contact
the sender and delete all copies.
The contents of this message that do not relate to the official business of
our company shall be understood as neither given nor endorsed by it."

=================================