Critical Bug: Department/Staff Drop Downs

[NC Software]

John,

You provided a STABLE that was untested and flawed. It obviously didn't instantly go into a "mess" status, so fix the issues pointed out and re-release another STABLE. Would it hurt to put out a STABLE monthly? People are not required to update, but those of us that need the updates to resolve the heinous usability issues you introduced by failure to test will update. Microsoft is pushing updates to developers much more frequently now, consider following their lead. There is a reason for it, especially when software quality is substandard.

[ecornet]

I don't understand, if you are this unhappy with the product for the last three months (at least) why don't you just stop using it and find another solution?

[John Haugeland]

Originally Posted by NC Software

You provided a STABLE that was untested and flawed.

It wasn't untested, Neal, and all software is flawed. If you look, you can see what we plan to fix for the next several versions; our upcoming release has known bugs too. This is, in fact, the case for essentially all software.

Originally Posted by NC Software

Would it hurt to put out a STABLE monthly?

Actually, I've been pushing for this internally. It's a really big change for a large team, and it's not a change to be made lightly. There is a lot of dissenting opinion on the matter among the engineers.

Originally Posted by NC Software

heinous usability issues you introduced by failure to test

Why do you say things like this? It's difficult to respond politely, to be frank. You don't know anything about our testing process, and of the in excess of one hundred repairs in 3.20.03, only two had to be continued. The primary three purposes of testing are to verify that repairs are accurate, to verify that old fixed problems do not re-emerge, and to verify range terms. We have an excellent record in all three of those respects.

Believe it or not, testing doesn't just vaporize all defects, nor does it expose problems that haven't been reported. It also doesn't stave off new defects, and testing for UI in a web context is virtually impossible.

Just because you don't understand the impact of our testing doesn't mean it doesn't exist. I really wish you'd stop making these accusations. They're not productive, they're not pleasant and they're not correct.

Originally Posted by NC Software

Microsoft is pushing updates to developers much more frequently now

They're using the exact same non-automated key release every six months that they've been doing for the last fifteen years. They haven't even changed the numbering system since it was introduced with MSDN in the Windows 3.1 days.

Originally Posted by NC Software

consider following (Microsoft's) lead.

If you're angry about defect rates and release times, you honestly couldn't have chosen a less appropriate major company to imitate.

I think I'm pretty much done replying to this thread. You had your answer days ago. Nothing useful is being said here.