[freetds] Preparing the next release
James K. Lowden
jklowden at freetds.org
Sun Dec 16 18:20:41 EST 2007
It's getting to be time for the next release of FreeTDS. Let's collect
If you have a patch you'd like to see included, now's the time to post it.
If you have an issue that hasn't been addressed, now's the time to say
so. If you'd like to deploy the next release, now's the time to test the
latest snapshot. Post your piece or hold your peace.
How much has change since 0.64?
1. 23,710 lines added or deleted.
2. 85 files added
3. fisql (and odbc utilities)
4. autoconf improvements
5. 21 unit tests
6. encrypted connections
7. timeout handling
It's time alright.
If I could focus your attention on a single feature, it would be results
processing e.g. dbnextrow(). A year ago we reworked that aspect of libtds
to allow the client libraries to do what the docs say they do. If you
have C programs linked to 0.64, it's possible they rely on 0.64's
The next version will be 0.82.
I bet you're wondering why not 0.65. Two reasons: 1) see above and 2)
we're nearing the finish line. FreeTDS is a lot closer to 1.0 than 0.65
implies. db-lib in particular is almost feature complete.
Besides, whenever you change 30% of your codebase, you're entitled to more
than a 0.01 bump. I'm sure that's written down somewhere.
OK, so why 0.82? I figure we're asymptotically approaching perfection.
At the precision we seem to favor, we have 5 more releases before 1.0:
$ V=.64; while [ "$V" != "1.00" ]; do echo -n "$V -> "; V=$(printf
"scale=2\n 1 - (1 - $V) / 2\n" | bc); echo $V; done
.64 -> .82
.82 -> .91
.91 -> .96
.96 -> .98
.98 -> .99
.99 -> 1.00
Keep those cards and letters coming, folks!
More information about the FreeTDS