Re: Re: [PHP4BETA] PHP 4.0.0 Release packaged

> So, to sum up: PHP releases need to go through an effective code freeze > period and from then on only bug fixes are performed until there a release > is produced. All reports should be handled in a first come, first > addressed basis. Reproducible bugs should have the priority. All features > should be properly documented or else you would better not announce them. > > I think that these rushed releases should be rethought. PHP needs all the > credibility as it may get. Rushing it as it is, is not helping. Release early, release often. It is pretty much as simple as that. It keeps the project dynamic, it keeps people interested and it keeps things fun. Only a few of the PHP developers actually do this as their fulltime job. Probably only Zeev and Andi right now. For the rest of us it is more of a hobby, so you are completely right in saying that it isn't done in a professional manner. This is the very definition of large open source projects. But I also don't agree that it is all that unprofessional. We need to strike a balance between keeping it fun and interesting for everyone involved and being conservative. To reach the lavel of code maturity you seem to insist on you need 6-month complete code freeze periods. For people who wish to contribute snippets of code and the occasional new feature a 6-month code freeze is completely discouraging. The current approach has worked pretty well so far. Yes there will be bugs, and yes they will be fixed. -Rasmus