FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> From: Castellano, Nicholas 
> Sent: January 7, 2004 3:47 PM
> > From: Lowden, James K 
> > Sent: Wednesday, January 07, 2004 1:36 PM
> > 
> > These are all important issues.  
> > 
> > If you commit fixes after today, please bump the rc number in 
> > configure.in. It's better to skip an rc than to have 
> > different snapshots both sporting the same number.  
> 
> I have committed these fixes.

Excellent!  Especially for "no promises".  ;-)    

        ++Tru64;

> I didn't bump the rc number, it's probably
> better if that's done centrally once per day by the release manager.

OK, that would be me.  I've already bumped it for today.  Your changes will
appear in rc4. 

> The only remaining issues for me are the three failures 
> mentioned earlier by
> Bill.  I'll leave those to him and Freddy to sort out unless 
> additional
> input is needed (too many cooks and all that...)

I'm going to try FreeTDS on NetBSD/Alpha (64-bit, little endian,
egcs-2.91.66) with TDS 5.0 and 7.0.  I hope to test it with the new gcc the
release, which I still hope to issue this weekend.  

I won't hold up 0.62 for the failures Bill cites.  One he said is "poorly
designed", and the other two aren't show stoppers according to Frediano, who
wrote them.  

I'm satisfied that bcp works with in-memory or character-delimited files,
which is all we're promising, even though I'm sure Bill will fix native
files as soon as he has time.  BCP is slated for a (nother) major rewrite,
this one for the history books, and there's every reason to expect native
files to work when the dust settles on 0.63.  

[memo to file: add -n caveat to freebcp man page.]

At this point, I'm just waiting for negative feedback.  If it's a quiet week
in Lake Woebegon, Sunday will be the big day.  

--jkl
-----------------------------------------
The information contained in this transmission may contain privileged and 
confidential information and is intended only for the use of the person(s) 
named above. If you are not the intended recipient, or an employee or agent 
responsible for delivering this message to the intended recipient, any 
review, dissemination, distribution or duplication of this communication is 
strictly prohibited. If you are not the intended recipient, please contact 
the sender immediately by reply e-mail and destroy all copies of the original 
message. Please note that we do not accept account orders and/or instructions 
by e-mail, and therefore will not be responsible for carrying out such orders 
and/or instructions.