"The programmers are working on things as fast as they can..." When I start working on a new project, I first draw up a list of what should be needed and how to get it. Then I make a time-plan, how long is it going to take to achieve what I'm after? This done, I sit down and start working, methodically, tackling the list items one by one, until no one is left to tackle. My project is ready now, but not tested. Another list is drawn: what kind of tests are required, how to go about it, what could go wrong... The project enters testing phase (usually with outsiders helping)... During testing some things can go wrong... They are noted down and solved one by one until the bottom of the list is reached again... Now the project (the product if you prefer) is ready for release. Some things can still go wrong, but these would require minor fixes only, or, if this isn't the case (and big problems arise) it would only mean that somewhere along the line someone (me) didn't do his job right. It happened during the marketplace migration and we thought this would serve as a lesson for the next move. It didn't apparently. It's happening again... Would it happen once more in the next migration? The thought makes me shiver. Bottom line: It is far better prevent instead of trying to find cures afterward. If the famous "programmers" in charge of the move can't do their job right, fire them and hire new ones, capable ones. As I'm expected to present a faultless product at the time it hits the market, so I expect those in charge of the framework design of this community to fulfill the same (required) standards. Rules are made to apply to all, comrades. --Panos

"That's another fine mess you got me in to!" -- Oliver Hardy