Hello to all the Lindens:
I do understand the problems inherent with churning out an update weekly.
Having said that, and having been in the "business", this is what I'm seeing as an end user.
Minor old bugs reappearing in new versions:
Example: The problems with highlighting and replacing text during Editing of Object and Prims was a bug in the July 21st Version, was "fixed" in the July 28th version and is now back again.
Generally, these types of things happen when development doesn't have control of the code library.
Having worked with several small software firms in their process of "making the leap", I realize that getting control of the code library isn't an easy task, and the problem gets compounded if you have programming staff spread out across multiple locations.
It's also not fun, nor sexy, basically it's a boring frustrating process, because someone always has something checked out to be worked on.
Having said that, you and I both know that eventually you'll have to get control of the code library so that old bugs don't keep coming back to haunt both you and us, the end users.
My suggestion is that you all take a deep breath, put development on hold for a week (or two if necessary), and get the code library straightened up, and more stringent controls put in place to avoid putting new "enhancements" into bad code and then sending it out in the update process.
Believe me, in the long run, it's worth it. Your staff is doing great things, but having to go back and fix stuff a 2nd time or a 3rd time isn't a good use of their time, and it's frustrating to the end users.
Thanks for listening,
Pup