No offense intended, but do you have people test the mod before release? Some of these bugs shouldn't be present if someone tested it. I volunteer for testing 2.5 Yeah, someone should test things before it gets released to the public.
Assemble a squad of 6 or so dedicated beta testers and you'll be good to go.
We thoroughly test every bit of code that the team itself writes explicitly for Floris (for 2.4, things like sea trade, weather-related ranged weapon penalties, the integrated options screen, the new features from PBOD such as the reworked deathcamera system, etc).
In addition to that, we make the sometimes mistaken assumption that the mini-mods/scripts/codes that others release for use have been tested and are working as described (the bank and companion presentations, for instance).
Finally, we do a number of tests to be sure the mod will start and there are no obvious script errors, etc. (This found the sounds.txt issue that some run into and had us ready with a variety of files for individuals to try.) But we can only test so many situations in a timely fashion.
It's a damned if you do, damned if you don't situation. Wait too long with testing and people increasingly complain that there is no release...and we want to work more of the in-process features in, which makes for more testing and more waiting. Do as I have described in an effort to get a delayed version out as soon as we can, and the appearance of a few bugs brings on the complaints and insinuations that we don't bother to test anything.
Some modicum of attempted understanding would be appreciated. This time around, we intend on releasing small bugfixes before the next major version, so as more bugs are reported, we'll gather them into some fixes here.