I feel sorry for your situation, but I think your comments are a bit harsh. A couple of things I have to point out:
- Why was management being shown a "test" site without being warned that there may be some bugs? - Why was management able to trigger a bug that you hadn't noticed as part of your own testing? - If management are expecting you to know about a particular feature, why were you sitting back and just expecting the rest of us to keep track of these aspects? - In the "real world", if a project is coming in to the tune of $35 million, you speak to someone who works for the company (or community) that is making the product and create a relationship that allows for two way communication. I don't see any examples of you coming in and saying that you've found a problem with a particular piece of code and want to work with us to fix it. I think it is a bit unfair for you to simply pick up an "off the shelf" product and expect us to know what your doing with it. Also, with the number of problems being reported that can be tracked back to mistakes being made by the user / coder. I am not always willing to accept that anything that you can't explain can be blamed on the API. I have had some problems with my own work that can be tracked down to a particular server / proxy / browser combination that creates a corruption of code. Since you claim the problem effects MSIE, I have to ask the question of why you are using a browser that gets patched every week for a new hole and accept that as the norm, while bitching about installing a distro that you hadn't tested. Would you refer that we alter the distro and remove the examples section? PHP doesn't include examples as part of their download and they don't have such problems. And before you complain that PHP is a "mature" project, I have to mention the status of the GD library in PHP 4.06. They implemented a new version that was supposed to support TTF files and made a mistake. They are still to fix it and release a new version. And PHP 4.06 has been out for about 6 months now. You comments about "not telling anyone" are out of line. If you are really interested in what changes are being made, join the CVS list. It emails EVERY code change. At the least, you chould go through the CVS details on the site and track down what changes were made. This is exactly what I did with the recent "removeChild / addChild" problem. It takes maybe 20-30 mins tops to track down which lines were changed and who changed them. Then, you can reverse the changes if you so chose in your own version. My early work on the A**oAPI came about due to my joining with people using it and working with them to find solutions to the problems. And I would certainly consider my own work to be less "mature" than that of the official project. It is completely unfair for you to jump out from nowhere and accuse us of causing your current situation. It is quite possible that the DynAPI was the catalyse but the cause may lie with your own mistakes in your administration of your own work. Doug Melvin wrote: >I did not deploy it on the live site. >only on the test site. >The problem is the management has gotten the impression that DynAPI is not >"mature" enough >fo commercial use. > >How the fuck do I convince them that the DynAPI is ready for the bigtime >when anyone in the office can download the 'official' distrubution and find >that it is broken? > >Or how about when the right-click no longer works (button is NEVER == to 2 >or whatever) >they ask me why this is so, and why was this feature implemented, and I >can't even say why, or even when? > >This is the real world guys. >In the real world people check their work before releasing it (with the >exception of Microsoft of course) > > >----- Original Message ----- >From: "Scott Andrew LePera" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Friday, December 07, 2001 4:06 PM >Subject: Re: [Dynapi-Dev] This sucks badly. > >>One wonders: >> >>1) why you bothered to deploy the latest bleeding-edge version knowing >>full well that things could break, as they often do, >> >>2) if you bothered to make backups of your last known working distro, so >>you could revert back, >> >>3) if you are using CVS, Perforce or some other system so you can >>rollback your changes, and >> >>4) why the hell you think any of us should care when you basically call >>the entire list "assholes." >> >>Since I know you're in a frustrated state, I'm going to refrain from >>recommending that you get kicked off the list, and instead wait until >>you calm down and provide some specifics on what broke and where. >> >>scottandrew >> >>Doug Melvin wrote: >> >>>Well guys. >>> >>>Thanks to somebody checking in code that they have NOT tested. >>> >>>IE: version 2.5.6 >>> >>>And with people making fundamental changes without telling anyone >>>(someone implemented a right-click event wich fucked up our entire >>>fucking site) >>> >>>I am most likly going to loose my job. >>> >>>Thanks a lot assholes. >>> -- Michael Pemberton [EMAIL PROTECTED] ICQ: 12107010 _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/
