Now the SDL Version in CVS is 1.2.5, on the change page this change is
listed under 1.2.6. This can get rather confusing, I planned on
updating my current stable Win32 copy of the source to 1.2.5 I’d have an
incorrectly labeled DLL (which I guess isn’t a major problem, but it
is an annoyance. If I modify the Resource file myself I believe I have
LGPL issues to deal with, and If I use 1.2.5 1/2 things get rather
confusing. Can’t an update be made to the already released 1.2.5, or
are the Windows developers going to need to go ahead and wait for the
release of 1.2.6 (hopefully by then the 1.2.6 resource file will be
1.2.6) to get a correctly versioned DLL.
Now the SDL Version in CVS is 1.2.5, on the change page this change is
listed under 1.2.6. This can get rather confusing, I planned on
updating my current stable Win32 copy of the source to 1.2.5 I’d have an
incorrectly labeled DLL (which I guess isn’t a major problem, but it
is an annoyance. If I modify the Resource file myself I believe I have
LGPL issues to deal with, and If I use 1.2.5 1/2 things get rather
confusing. Can’t an update be made to the already released 1.2.5, or
are the Windows developers going to need to go ahead and wait for the
release of 1.2.6 (hopefully by then the 1.2.6 resource file will be
1.2.6) to get a correctly versioned DLL.
Don’t worry, I corrected the version in CVS, updated the web page and
I’ll have new binaries tomorrow morning. 
See ya,
-Sam Lantinga, Software Engineer, Blizzard Entertainment