Re: [PHP4BETA] PHP 4.0.0 Release packaged
[email protected] (Stanislav Malyshev)
| Newsgroups | php.version4 |
|---|---|
| Organization | Zend Technologies Ltd (http://www.zend.com/) |
| Message-ID | <[email protected]> |
AP>> This is total garbage, there are many people putting thier jobs AP>> and businesses on the line by using open source. This would be AP>> the smack in the face that would get someone to never want to be AP>> associated with open source ever again nevermind loosing thier job AP>> or having thier business ruined. Face the reality. Commercial software companies *always* release known-buggy software, there's no way to meet deadline otherwise. Also, I do not see why current release of PHP 4 would ruin someone's business. I have hard time imagining that putting "Release" stamp on some version of PHP can have so big impact on someone's life. If $SNAPSHOT_CALLED_PHP_4 is buggy, you couldn't use it be it 4.0 or 4RC3. If it isn't buggy, you can use it if it's 4.0 but most will still much careful be it 4RC3. AP>> Remember, the php CVS repository is completely open to the public, AP>> this isn't the Linux kernel where releases need to be made so that AP>> people can see the changes. You won't tell Fortune-N company to use current CVS snapshot for their pet mega-project. Neither would you say this to mom-and-pop websoftware crafting shop whose all life depends on their scripts working. They should have reference point to lean on. CVS can't be that point, CVS is today here and tomorrow nowhere. There were numerous occasions that CVS even didn't compile. That's what CVS development releases are for - they don't even ought to build. They are for developers and those fearless ones that want to play with live fire. AP>> Software development isn't a popularity contest, you do it right, AP>> or you shouldn't do it at all. Well, not quite so. If trying to do it right means never finishing doing it, you'd better do it 99% right and then release and then continue working on remaning 1%. Or you never release at all. -- Stanislav Malyshev [email protected] +972-3-6139665